Host Team OS
Deploy the hosted Team OS API and Postgres.
Host Team OS when a team needs shared login, permissions, memory, review, and file sync.
The hosted API is called memory-api in the Agentic OS repository. The name is
historical. In Team OS, it is the client-facing API service.
What to deploy
Deploy two services:
| Service | Purpose | Reachable by workspaces? |
|---|---|---|
| Postgres with pgvector | Stores Company roles, Teams, access requests, members, clients, grants, memory, and audit events. | No |
Team OS API (memory-api) | Serves login, Company and Team management, permissions, memory, sync, review, and health endpoints. | Yes, through public HTTPS or an approved private path. |
Expose only the API through the chosen workspace access path. Never expose Postgres. Keep it inside a private network or behind a firewall.
Hosted deployment model
This documentation currently supports the Team OS beta image. Use the exact
tag ghcr.io/simonc602/team-os-server:beta. Do not use latest or omit the
tag. The current beta image supports Linux amd64 and arm64 hosts.
For a hosted deployment, use separate services:
- Postgres with the
pgvector/pgvector:pg16image. - Team OS API from
ghcr.io/simonc602/team-os-server:beta.
This model is best when the database needs its own backup and restore plan.
Setup path
- Set environment variables.
- Configure secrets and workspace backup.
- Choose a deploy path: Docker Compose, Coolify, Railway, or VPS.
- Complete startup and first owner setup.
- Configure backups and restore.
- Run first verification.
Next: Environment variables