Deploy a PoC
This path installs SmartAGT on a Linux or Windows VM, with PostgreSQL 18, pgvector and built-in file storage. Conversation, embedding, OCR and image models are accessed remotely.
Default accessApplication and AI accessInternal and outbound flowsSmartAGTVM · Linux or Windows
User sessions
Embedding
managed by
SmartAGT
mTLS :8010
HTTPS :8000
HTTPS :8001
HTTPS :443
TLS* :5432
mTLS :8888
TLS* :5432
Sessions
- Host
- x64 VM
- Processor
- 4 vCPUs
- Memory
- 16 GB RAM
- System
- Linux or WindowsUbuntu 22.04+, Debian 12+, Windows Server 2022+
- Disk
- 100 GB SSD
- Database
- PostgreSQL 18pgvector extension installed; on Windows, built with the Visual Studio C++ tools
Only flows entering or leaving the server are shown here. Interactions between processes on the server are detailed in the complete flow matrix.
| Source | Destination | Protocol / port | Purpose |
|---|---|---|---|
| User workstations | Server · Frontend service | HTTPS 9000 |
Web interface |
| Applications | Server · Public API | HTTPS 8000 |
SmartAGT API calls |
| AI clients | Server · Gateway | HTTPS 8001 |
Model access through Gateway |
| SmartAGT server | Internet | HTTPS 443 |
Remote models, web and connectors |
Listening ports can be customized.
The Public API stays on loopback: expose it only when applications must reach it. The Gateway listens on all interfaces: open port 8001 in the firewall when AI clients on other hosts must reach it. The internal link between the Frontend and the API, on 8010, stays local to the server and SmartAGT manages it: nothing to configure.
Each component spreads its files over four locations: its package, its configuration, its data and its logs. An update replaces only the package.
Linux
/app
├── smartagt-backend-core/ Backend package, replaced on update
├── smartagt-bff-core/ Frontend package, replaced on update
└── config/
├── backend/ Backend YAML and certificates
└── bff/ Frontend YAML and certificates
/etc/smartagt/ environments and secrets
/var/lib/smartagt/
├── backend/ Backend data
└── bff/ Frontend data
/var/log/smartagt/
├── backend/ Backend logs
└── bff/ Frontend logs
Windows
C:\app
├── smartagt-backend-core\ Backend package, replaced on update
├── smartagt-bff-core\ Frontend package, replaced on update
├── config\
│ ├── backend\ Backend YAML, environment and certificates
│ └── bff\ Frontend YAML, environment and certificates
├── data\
│ ├── backend\ Backend data
│ └── bff\ Frontend data
└── logs\
├── backend\ Backend logs
└── bff\ Frontend logs
The data and log directories are declared in each component's YAML, with data_dir and log_dir. Configuration lists every path.
This PoC is intended to evaluate all platform features with a group of up to 100 users in a functional evaluation. Load testing, running large models locally and intensive processing require adapted sizing.
* TLS to PostgreSQL can be enabled, if you wish, with the PostgreSQL SSL procedure.
Required deliverables
- Backend package: base component for Platform, Gateway and workers.
- Frontend package: base component for the interface.
- Evaluation license.
Your environment must meet the system and network prerequisites detailed above.
Prepare the environment
Complete these two prerequisites before installing SmartAGT.
| Step | Operation | Result |
|---|---|---|
| 1 | Prepare PostgreSQL | Compliant instance, pgvector installed. |
| 2 | Prepare the databases | Databases, roles and extensions ready. |
Install SmartAGT
The environment is ready. Install the packages, then follow the installation wizard.
| Step | Operation | Result |
|---|---|---|
| 1 | Install the Backend | API and workers running. |
| 2 | Install the Frontend | HTTPS sign-in, internal link active. |
| 3 | Activate the installation | Password changed, license active. |
| 4 | Getting started | Setup completed with the wizard. |
Getting started
Change the initial password, then follow the installation wizard with Getting started.
Screens, agents and day-to-day administration are described in the documentation inside SmartAGT.
Update the PoC
To update the project, follow the Update procedure.