Self-host OpenDash
Run OpenDash on your own infrastructure. The same two images serve a laptop, a single VM and a scaled deployment, with PostgreSQL as the only stateful dependency.
OpenDash is built to run where your data already lives. Self-hosting gives you the full product: the same images, the same answer gate, and no telemetry sent anywhere. Your warehouse keeps the analytical data; OpenDash keeps only what it needs to run (conversations, definitions, results and jobs) in its own Postgres.
Status: beta
OpenDash is in beta. We’re continuing to improve the product with user feedback.
Read the release notes before every upgrade, and keep backups of Postgres and your encryption key.
Deployment shapes
| Shape | Compute | Postgres | Best for |
|---|---|---|---|
| Single node | docker compose: web and worker, all worker pools in one process | bundled postgres (pgvector image) | evaluating, small teams |
| Scaled | several web replicas, workers split by WORKER_POOLS | external managed Postgres | larger installs |
Start with a single node. Moving to the scaled shape later is a configuration change, not a migration: point the database URLs at a managed Postgres, add web replicas and split the workers.
Architecture
Your infrastructure
web and worker, around one PostgreSQL. Your warehouse keeps the analytical data.webserves the UI, the API, sign-in and webhooks. It never runs migrations and never connects to your databases.workerruns the analyst, the query gateway, routines, syncs and deliveries. It is the only process that reaches your databases, the model providers, Slack and email. Connected services (MCP servers) are reached from both.- PostgreSQL holds everything stateful: data under row-level security, the job queue, full-text and vector search, and change notifications. There is no Redis, queue or object store to run.
The architecture page explains why it is shaped this way.
What you need
- A machine with Docker and Compose v2, or a container platform.
- PostgreSQL 16, 17 or 18 with
vector,pg_trgmandbtree_gin, if you don't use the bundled one. - A domain with HTTPS. Production sign-in refuses plain HTTP; the bundled Caddy profile can get a certificate for you.
- A second HTTPS domain pointed at the same server, for dashboards (
OPENDASH_FRAMES_URL). See Configuration. - An email provider (Resend or any SMTP server). Sign-up, sign-in and password reset send email, and the web app won't start without it in production.
- A model provider key for the analyst: Anthropic, OpenAI, Google or the Vercel AI Gateway. Workspaces can also bring their own.