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, their default settings and which flows to allow in your firewalls.
Topologies
Choosing a topology is explained in Prepare a project.
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.
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.
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.
Exposed interfaces
These interfaces must stay on your private network, with no Internet exposure: see Network exposure.
| Interface | Port | Clients | Default | Certificate |
|---|---|---|---|---|
| Frontend | HTTPS 9000 |
User workstations Reverse proxy |
0.0.0.0 |
Self-signed, replaceable |
| Public API | HTTPS 8000 |
Third-party applications Automation Frontend service |
127.0.0.1 |
Self-signed, replaceable |
| Gateway | HTTPS 8001 |
AI clients | 0.0.0.0 |
Self-signed, replaceable |
| Internal link | mTLS 8010 |
Frontend service | 127.0.0.1 |
SmartAGT internal |
All these interfaces are customised in their component's YAML:
- Internal link:
smartagt.http.internalblock, withurlandlocal_enrollment_port. - Frontend:
smartagt.http.serverblock. - Public API:
smartagt.http.publicblock. - Gateway, if AI Gateway is deployed:
smartagt.gateway.serverblock.
For these last three interfaces, the following settings can be customised: host, port, certfile, keyfile and trusted_proxies. host sets the listening interface: 0.0.0.0 for all server interfaces, or the IP address of a specific one.
More information: Configuration, Inbound flows and Security.
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, running nodes 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 |
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. The built-in engine also searches images on www.bing.com |
| API connectors | API and relevant processes | Business HTTPS APIs authorized for the project |
| SQL connectors | API and relevant processes | Databases authorized for the project, engine TLS: PostgreSQL 5432, MySQL 3306, SQL Server 1433 |
| File share connectors | API and relevant processes | Shares authorized for the project, encrypted and signed SMB 3 445 |
| Local models | Preparation workstation or authorized process | HTTPS to huggingface.co and the hf.co subdomains, weight CDN included, only when the weights are not placed manually |
| 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 and web search images from their HTTPS origin, including *.mm.bing.net for the built-in engine. 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.