Networking and security
Who can reach and join your instance, how OpenDash talks to your databases, and the settings that matter behind a proxy.
A self-hosted OpenDash holds credentials to your databases and spends your model budget, so the defaults are closed. This page covers what you decide as the operator. For how the code isolates tenants and checks numbers, see Security and telemetry.
Who can join
New instances are invite-only (OPENDASH_INVITE_ONLY=1). The address in OPENDASH_BOOTSTRAP_ADMIN_EMAIL can sign up once, while nobody has, and invites everyone else. A new instance nobody has joined refuses to start without it.
Setting OPENDASH_INVITE_ONLY=0 lets anyone who can reach the address sign up, create workspaces on your model keys, and connect sources that reach your network. Only do that on a private instance.
HTTPS
Production sign-in accepts only an HTTPS BETTER_AUTH_URL and HTTPS trusted origins. Either:
- put your own TLS proxy (a load balancer, nginx, Traefik) in front of
web, or - use the bundled Caddy profile:
docker compose --profile caddy up -dwithOPENDASH_DOMAINset. Caddy gets a Let's Encrypt certificate (its own forlocalhost).
Behind a proxy
Per-IP rate limits need the real client address.
- Caddy profile: nothing to set. Caddy overwrites
X-Forwarded-For. - Your own proxy: set
OPENDASH_TRUSTED_PROXIESto its addresses or CIDR ranges. Without it, a multi-entryX-Forwarded-Forisn't trusted and those requests share one strict bucket. If your proxy uses another header, list it inOPENDASH_CLIENT_IP_HEADERS.
Never expose web directly without a proxy. A client could send its own X-Forwarded-For and dodge rate limits.
Reaching your databases
- Only workers connect to your databases and warehouses. The web app never does.
- Every query runs read-only, in a read-only session with a server-side time limit, as the user you connected. Create a read-only user for each source; the connection check tells you if the user can change data.
- Private addresses. The community edition allows them, since that's where most self-hosted databases live. If you host OpenDash for other people, set
OPENDASH_EDITION=cloudonweband workers so workers refuse private addresses, and list their fixed outbound IPs inOPENDASH_EGRESS_IPSfor people to allowlist. - TLS to sources defaults to
verify-fullfor PostgreSQL and MySQL. See Connect a source. - Trust. Results, samples and checks are bounded for an honest server. A server built to ignore its own limits can still send more than expected, so connect only databases you trust to behave.
Secrets
OPENDASH_KEKencrypts every stored connection password and model key. Keep it out of the database backups and back it up separately, offline. Losing it means re-entering every secret.BETTER_AUTH_SECRETsigns sessions and email links.- Secrets live in your environment or
.env. They are never logged, never put in prompts, and never returned to the browser.
Outbound and inbound calls
- Outbound calls from tools and webhooks go through an SSRF guard.
- Inbound webhooks are verified by signature.
- Telemetry: none by default. Traces go only to an OpenTelemetry collector you configure, and never carry prompts, SQL or answers.
PostgreSQL
OpenDash keeps all of its state in one PostgreSQL. What version and extensions it needs, which connection goes where, and notes for Neon, Supabase, Amazon RDS and ClickHouse Managed Postgres.
Monitoring and backups
What to log, watch and back up once OpenDash is running, and how to scale it out.