Packages and licence
Packages and the licence are transferred through a private delivery channel. The documentation platform provides procedures and their commands.
Delivery contents
| Deliverable | Purpose |
|---|---|
| Backend package | Linux .tar.gz or Windows .zip archive, Platform API, rag-ingestor, rag-embed and scheduler workers, optional AI Gateway command and SeaweedFS binary |
| Frontend service package | Same release as Backend, web interface and session management |
| YAML templates | smartagt-backend-core.yaml and smartagt-bff-core.yaml, matching these packages |
| Versions and SHA256 checksums | Pair Backend and Frontend service |
Evaluation licence .lic |
Activate the installation for the agreed organization and period |
| SmartAGT contact | Obtain a missing deliverable or report an installation issue |
Use the archive names listed in your delivery manifest. Commands refer to the archive as <Backend package> or <Frontend package>: give its path on the server. The Linux archive contains a root directory, smartagt-backend-core/ or smartagt-bff-core/; the Windows archive places run.exe directly at its root. weed sits next to the Backend launcher.
Prepare PostgreSQL and pgvector. These dependencies are not part of the SmartAGT deliverables.
Required resources
| Resource | Reference |
|---|---|
| VM, administration permissions and network | Resources and systems |
| DNS, enterprise certificates or evaluation CA | Install your certificates |
| Provider account and authorized models | Getting started |
| Passwords and a place to retain keys | Configuration and secrets |
The terminal collects secrets without displaying them.