Overview
Deploy Openfuse on your own infrastructure. Full control over your circuit breaker platform with Docker Compose, Kubernetes, or any container orchestrator.
Openfuse is designed to run anywhere — your laptop, a single VM, or a full Kubernetes cluster. Self-hosting gives you complete control over your data, network topology, and deployment lifecycle.
Architecture
A self-hosted Openfuse deployment consists of four services and a PostgreSQL database:
| Component | Image | Role |
|---|---|---|
| API | ghcr.io/openfuseio/openfuse-api | Backend server. Runs migrations on startup, serves the REST API. |
| Keycloak | ghcr.io/openfuseio/openfuse-keycloak | Authentication (SSO). Manages users, OAuth, multi-tenant realms. |
| UI | ghcr.io/openfuseio/openfuse-ui | Web dashboard. Static SPA served by Nginx. |
| Config Importer | ghcr.io/openfuseio/openfuse-config-importer | One-time task. Imports Keycloak realm configuration, then exits. |
All images are published to GitHub Container Registry and support linux/amd64 and linux/arm64.
Startup order
The Docker Compose files handle startup ordering automatically:
The UI is a static SPA with no service dependencies — it starts immediately. The Config Importer is a one-time task that configures Keycloak and exits; it doesn't block the API. In the Docker Compose setup, Caddy waits for the API, Keycloak, and UI to be healthy before it starts routing traffic.
Subdomain routing
Openfuse uses subdomains to isolate tenants. Given ROOT_DOMAIN=example.com:
| URL pattern | Routes to |
|---|---|
*.api.example.com | API — each company gets its own subdomain (e.g., acme.api.example.com) |
sso.example.com | Keycloak — authentication and login pages |
example.com, app.example.com, *.example.com | UI — dashboard and company-specific views |
This is why self-hosted deployments require wildcard DNS records.
Choose your path
Try locally
Run the full platform on your laptop with one command. No domain or DNS required — uses lvh.me for local subdomain routing. Takes about 5 minutes.
Deploy to cloud
Spin up Openfuse on a VM for team evaluation or from a CI pipeline. Non-interactive installer with automatic secret generation.
Docker Compose
Full production setup with managed databases, wildcard TLS, SMTP, and backups. Everything you need to run Openfuse reliably.
Already running? Check the configuration reference or learn how to upgrade.
Running Kubernetes, ECS, or Cloud Run? See Kubernetes, AWS ECS, Cloud Run, or Azure Container Apps.