Skip to content

Network

This page shows where to place SmartAGT, which flows it receives and sends, and which ports to open.

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, 2FA 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 host operates SmartAGT for you.
  • Outbound flows: calls to models, the web and connectors remain possible, as described in Network.

Inbound flows

All SmartAGT connections are encrypted with TLS, including within one server. Open each port, inbound on the firewall, to the listed machines only.

Flow Protocol Port Default listener Open to
Web interface HTTPS 9000 All addresses User workstations or reverse proxy
Public API HTTPS 8000 Loopback Applications, if the API is exposed
AI Gateway HTTPS 8001 All addresses Connected tools
Internal link mTLS 8010 Loopback Frontend servers, in a distributed installation
  • Listening address: smartagt.http.server.host for the Frontend, smartagt.gateway.server.host for AI Gateway. With a reverse proxy on the same server, restrict them to the loopback: Proxy on the same server.
  • Reverse proxy: it receives users on its own port, usually 443, and only it reaches port 9000.
  • AI Gateway: a connected tool must also be listed in the console Network list.

User workstations and connected tools go through the reverse proxy and the load balancers, never directly to a node.

Flow Protocol Port Nodes Open to
Web interface HTTPS 9000 Frontend Reverse proxy
Public API HTTPS 8000 Platform Frontend nodes and API load balancer
AI Gateway HTTPS 8001 gateway role Gateway load balancer
Internal link mTLS 8010 Platform Internal link load balancer

Frontend nodes reach the Public API for their attachment. The API load balancer is only needed if applications call it.

The built-in storage stays local to the server. The first attachment desk, temporary and limited to the loopback, answers over HTTP with signed responses, then closes. To have workstations and applications recognize the server: Certificates.

Outbound flows

SmartAGT only opens encrypted outbound connections. HTTPS flows go through the outbound proxy set in the console.

Infrastructure

Flow Protocol Port
PostgreSQL PostgreSQL/TLS 5432
S3 storage, if used HTTPS 443

Operating flows

Downloads only, over HTTPS 443: no installation data is sent.

Flow Destination Frequency
Model referential Publisher referential Configurable
Exchange rates www.ecb.europa.eu
www.bankofcanada.ca
data.norges-bank.no
16:00 and 22:00 UTC
Open-weight models huggingface.co, hf.co When a local model is installed

Without access, SmartAGT keeps the last known referential and rates. Model weights can be placed by hand. The license is verified locally, without any flow.

MSP platform

An upcoming version routes the referential, exchange rates and license check through the publisher MSP platform only.

Connected services

Only for configured services. Standard ports, to adapt to your services.

Flow Protocol Port
Model providers HTTPS 443
SSO HTTPS 443
Entra ID directory HTTPS 443
LDAP directory LDAPS or STARTTLS 636 or 389
Email SMTP with TLS or STARTTLS 465 or 587
API connectors HTTPS 443
SQL connectors Engine TLS 5432, 3306 or 1433
File shares Encrypted and signed SMB 3 445
Web search HTTPS 443

Detailed destinations: Network.