Skip to content

Network

SmartAGT exposes four interfaces: three serve your users and applications, the fourth links the Frontend to the API. This page shows where they sit in each topology and which flows to allow in your firewalls.

Exposed interfaces

Interface Port Clients Default exposure Certificate
Frontend HTTPS 9000 User workstations, or reverse proxy All server interfaces (0.0.0.0) Self-signed by default, or your own
Public API HTTPS 8000 Applications; Frontend service during enrollment Loopback; server address for applications or a remote Frontend service Self-signed by default, or your own
Gateway HTTPS 8001 Authorized AI clients, if AI Gateway is deployed All server interfaces (0.0.0.0) Self-signed by default, or your own
Internal link mTLS 8010 Frontend service only Loopback; between servers, open to Frontend services only SmartAGT, renewed automatically

These interfaces stay on your private network: Network exposure.

The Public API is configured under smartagt.http.public, the Gateway under smartagt.gateway.server. Certificates and responsibilities are detailed in Security.

Topologies

Choosing a topology is explained in Prepare a project.

Single serverOne VM hosts every component, each linked to its clients
SmartAGT VM
Backend
BrowserUser workstations
Applications
AI clients
FrontendInterface and sessions
APIAgents and business logic
GatewayModel access
WorkersIngestion, indexing and deferred tasks
PostgreSQLData, sessions and vectors
SeaweedFSFiles
ModelsPrivate or SaaS
FrontendHTTPS :9000 Public APIHTTPS :8000 GatewayHTTPS :8001 Internal linkmTLS :8010 TLS :5432 TLS :5432 mTLS :8888 HTTPS

Default accessApplication and AI accessInternal and outbound flows

Databases and storage remain local. User workstations reach the Frontend service directly or through a reverse proxy. Remote models are outbound destinations.

ClusterOne block per node, shared PostgreSQL and S3
Backend
BrowserUser workstations
Applications
AI clients
Load balancerWeb entry point
Frontend VMsInterface and sessions
Load balancerTCP passthrough (L4)
Platform VMsPublic API, internal link and Gateway
Worker VMsIngestion and indexing
PostgreSQLShared service
S3Shared private bucket
ModelsPrivate or SaaS
HTTPS :443 FrontendHTTPS :9000 Public APIHTTPS :8000 GatewayHTTPS :8001 Internal linkmTLS :8010 TLS :5432 TLS :5432 HTTPS HTTPS

Default accessApplication and AI accessNode-to-node and outbound flows

Hosts use internal DNS names. Browsers go through a load balancer placed in front of the Frontend nodes. Backend nodes reach PostgreSQL and the shared S3 storage directly. The Frontend service reaches the API through the internal link 8010, directly or through a load balancer. On this link, the load balancer performs plain TCP passthrough (layer 4) and does not terminate TLS: an intermediary that terminates it breaks mutual authentication. The firewall only allows the clients planned in the topology.

KubernetesPostgreSQL and S3 remain services outside the containers
Application containers
Backend
BrowserUser workstations
Applications
AI clients
Ingress or proxyWeb entry point
FrontendInternal service
PlatformPublic API, internal link and Gateway
WorkersIngestion and indexing
PostgreSQLExternal service
S3External private bucket
ModelsHTTPS services
HTTPS :443 FrontendHTTPS :9000 Public APIHTTPS :8000 GatewayHTTPS :8001 Internal linkmTLS :8010 TLS :5432 TLS :5432 HTTPS HTTPS

Default accessApplication and AI accessService-to-service and outbound flows

The proxy or ingress publishes the web entry point. PostgreSQL and S3 have their own access rules; only the relevant roles can reach them. Certificates are also verified between containers.

Flow matrix

All application connections are encrypted with TLS, including connections within one VM. The certificate and service name are verified on internal links managed by SmartAGT. Encryption to PostgreSQL is enabled with PostgreSQL SSL; it is expected in production. On exposed interfaces, verification is complete once your certificates are installed with Install your certificates. The ports below match the procedures; adapt rules to the addresses and ports actually selected.

Source Destination Protocol / port Purpose
Browser Direct Frontend service HTTPS 9000 PoC interface and sessions
Browser Reverse proxy, if used HTTPS 443 Project public origin
Reverse proxy Frontend service HTTPS 9000 Interface and streaming
Frontend service API · internal link mTLS 8010 All application traffic, including relayed public routes
Frontend service Public API HTTPS 8000 Enrollment with a deployment secret, return after a long absence and readmission
Application Public API HTTPS 8000 SmartAGT API calls
API, workers, Gateway PostgreSQL PostgreSQL/TLS 5432 Platform data and vector indexes
Frontend service PostgreSQL PostgreSQL/TLS 5432 Frontend service database
API and relevant processes Chat models HTTPS, 443 by default Remote inference
API and rag-embed worker Embedding models HTTPS, 443 by default Document indexing and search

Workers wait for the database schema before starting, without any HTTP call to the API.

Storage Source Destination Protocol / port
Built-in (SeaweedFS), on one VM API and workers Local storage managed by SmartAGT HTTPS mTLS 8888, local to the server
Built-in (SeaweedFS), on one VM Built-in storage PostgreSQL PostgreSQL/TLS 5432
S3 API and workers Bucket endpoint HTTPS, 443 by default

On one VM, built-in storage exchanges remain local and use TLS with mutual authentication, under a SmartAGT internal authority: none of your certificates is involved. The S3 bucket remains private and access is restricted to application credentials. For multiple nodes, storage flows are set when the project is scoped.

Source Destination Protocol / port Purpose
Authorized AI client or browser Gateway, direct or through its proxy HTTPS 8001 or 443 JSON/SSE API and console probe
Gateway proxy Gateway process HTTPS 8001 Requests and streaming
Gateway Platform PostgreSQL PostgreSQL/TLS 5432 Permissions, keys, admission and heartbeat
Gateway Authorized providers HTTPS Model execution

AI Gateway shares the Platform database and KEK. It requires no HTTP connection to the Frontend service or Platform API. Both the firewall and the allowed address list in the Gateway console apply.

Service Source Destination to allow
OIDC / Entra ID SSO Browser and API Identity provider HTTPS origins; exact HTTPS callback URL
Entra ID directory API and scheduler login.microsoftonline.com, graph.microsoft.com, HTTPS 443
LDAP API LDAPS 636 or mandatory STARTTLS on 389
Email API and scheduler SMTP relay with implicit TLS 465 or mandatory STARTTLS 587
Web search API Selected engine HTTPS origins and, when page reading is enabled, authorized websites
Connectors API and relevant processes Business HTTPS APIs authorized for the project
Local models Preparation workstation or authorized process HTTPS weight repository, only when files are not prepositioned
Publisher catalog API HTTPS repository supplied with the delivery; offline signed import available
Dependencies Preparation workstation / installation host Authorized HTTPS system and package repositories

The browser may load source images from their HTTPS origin. Provider domains depend on the configured access: record the delivered endpoints, particularly for private and regional services.

In the PoC, user workstations reach the Frontend service on 9000. Open the Public API 8000 and the Gateway 8001 in the firewall only when applications or AI clients must reach them. The internal link 8010, PostgreSQL and storage remain local to the server. For a project, allow the client nodes identified in your architecture, without exposing databases or storage to user workstations. Open 8010 between servers only from Frontend services.

Outbound network

  • Proxy: configure the outbound proxy and external service CAs under Platform > Outbound network (see Configuration). PostgreSQL, built-in storage, LDAP and SMTP do not use an HTTP proxy. License validation is local and does not require general Internet access.
  • DNS: name resolution goes through internal infrastructure services.
  • Time: NTP synchronization goes through the same services.