2 min read · 355 words
Deployment Overview
Today, exactly one artifact is deployed: this documentation site (Vercel). The backend and frontend are local-development services with a documented path to production — not a pretense of one.
Current state
| Piece | Today | Production path |
|---|---|---|
| Docs site | ✅ deployed — Vercel builds MkDocs from main | Docs Site |
| Backend | local uvicorn on :8001, SQLite + Chroma on disk | Backend |
| Frontend | local next dev on :3000 | Frontend |
| Database | file on disk, no backups | Postgres + managed backups (roadmap) |
| Containers / CI/CD | ❌ none — no Dockerfile, no pipelines exist in the repo | roadmap |
The platform has no authentication and no rate limiting — see Security. Deploy only into a private network / behind an authenticating proxy until hardening lands.
Deployment topology (target shape)
Rendering diagram…
The frontend is Vercel-native (it's Next.js); the backend needs any host that gives you a Python process plus a persistent disk — both stores are files, so ephemeral filesystems (classic serverless) lose all data on restart. That single constraint drives most hosting choices; details in Backend.
Environment variables in production
The full reference is Configuration. Production summary:
| Where | Variables |
|---|---|
| Backend host | OPENAI_API_KEY (secret store!), optional OPENAI_MODEL, OPENAI_EMBEDDING_MODEL |
| Frontend host | AGENTOPS_API_BASE_URL, AGENTOPS_DASHBOARD_API_URL, AGENTOPS_AGENTS_API_URL → all pointing at the backend host |
| Docs | none |
Section pages
[Backend Deployment](backend.md)Process model, persistence requirements, a production checklist, and host-agnostic guidance.Backend Deployment
[Frontend Deployment](frontend.md)Building and hosting the Next.js app, environment wiring, and the proxy consideration.Frontend Deployment
[Docs Site](docs-site.md)The live Vercel + MkDocs setup — build command, config files, and how deploys trigger.Docs Site