Skip to content

Security

Connections in a SmartAGT installation are encrypted with TLS, including within one server. This page shows where to place SmartAGT, who manages each certificate, what you are responsible for and which secrets to keep.

Network exposure

SmartAGT is designed to run on a private network.

Internet exposure

SmartAGT is neither designed nor intended to be exposed directly to the Internet. Direct exposure is your sole responsibility.

  • Additional protections: HTTPS and a reverse proxy strengthen access without replacing the private network. A reverse proxy reachable from the Internet is still direct exposure.
  • Remote users: they join the private network through a VPN or agent-based Zero Trust access.
  • Hosted installation: the same rule applies if a hosting provider or reseller operates SmartAGT for you.
  • Outbound flows: calls to models, the web and connectors remain possible, as described in Network.

Encrypted flows

Flow Protocol Certificate managed by
Browser or reverse proxy to the Frontend HTTPS 9000 You, or SmartAGT with a self-signed certificate by default
Browser to the reverse proxy, if used HTTPS 443 You
Applications to the Public API HTTPS 8000 You, or SmartAGT with a self-signed certificate by default
AI clients to AI Gateway, if enabled HTTPS 8001 You, or SmartAGT with a self-signed certificate by default
Frontend to the API, internal link mTLS 8010 SmartAGT
API, workers, AI Gateway and Frontend to PostgreSQL PostgreSQL/TLS 5432 You
API and workers to built-in SeaweedFS storage HTTPS and gRPC over mTLS SmartAGT
API and workers to S3, if used HTTPS, 443 by default Service host
API, workers and AI Gateway to remote models HTTPS, 443 by default Provider
Access to connected services: SSO, directory, LDAP, email, connectors, web search HTTPS, LDAPS or STARTTLS, SMTP with implicit TLS or STARTTLS Service host

The only exception is the local enrollment endpoint used for first enrollment: temporary and restricted to loopback, it answers over HTTP with signed responses, then closes.

A self-signed certificate encrypts exchanges, but it does not let clients authenticate the server: the browser displays a warning. To remove it, install your own certificates with the Install your certificates procedure. Clients calling these interfaces must then trust the authority that issued them. Ports to open are detailed in Network.

Responsibilities

Item You SmartAGT (product)
Frontend 9000, Public API 8000 and AI Gateway 8001 certificates Optional: replace them with your own (Install your certificates) Self-signed certificate by default
PostgreSQL TLS Your responsibility No action
Frontend and API internal link 8010, built-in storage No action Authorities, certificates, automatic renewal and rotation
KEKs, passwords and provider keys Keep them in a vault Encrypting data under the KEKs and using the other secrets to authenticate
Firewall and network exposure Your responsibility: Network exposure, Secure the installation No action

Secrets to keep

Keep these secrets in a vault.

Secret Purpose
Backend KEK Protect encryption keys used by Platform and its workers
Frontend KEK Protect Frontend keys
PostgreSQL passwords Authenticate each component's role on its databases
Provider keys Authenticate model and connected service calls
admin account password set during activation Administer SmartAGT; the one-time password from init is replaced at first login

Backend processes share the Backend KEK; the Frontend has its own. These keys must be kept across restarts: replacing a package must preserve access to databases, files and encryption keys.