Deploy OpenFault on Dokploy in one click

You can deploy OpenFault on Dokploy from its template gallery. The template starts one container (ghcr.io/openfault/openfault:0.1.0) on port 8080, stores everything in a volume at /data, gives it a domain, and sets the public URL from that domain. You then open the domain, finish the setup wizard, and paste the new DSN into the Sentry SDK you already use.

OpenFault is a free, MIT-licensed, self-hosted error tracker that accepts events from Sentry SDKs. It is one container with SQLite inside: no Redis, Kafka, Postgres or ClickHouse. In the repo’s 10k-event burst test on an Apple M5 (2026-11-06), it sat at about 10 MB of memory idle and peaked at about 28 MB, accepting 3,000 events and rate-limiting 7,000. That is small enough to share a Dokploy server with your apps.

The template was merged into Dokploy/templates as a community contribution. It was tested with docker compose locally, not inside a Dokploy instance. OpenFault itself is in active development and not production ready. Run it next to your current error tracker first.

What the template sets up

The template’s compose file is short:

services:
  openfault:
    image: ghcr.io/openfault/openfault:0.1.0
    restart: unless-stopped
    environment:
      - OPENFAULT_BASE_URL=https://${OPENFAULT_HOST}
      - OPENFAULT_TRUST_PROXY=1
      - OPENFAULT_SETUP_TOKEN=${OPENFAULT_SETUP_TOKEN}
    volumes:
      - openfault-data:/data

volumes:
  openfault-data: {}

Its template.toml fills in two values when you deploy:

• OPENFAULT_HOST is a domain Dokploy generates for the service, routed to port 8080.
• OPENFAULT_SETUP_TOKEN is a random 32-character password.

What each variable does, from the install guide:

• OPENFAULT_BASE_URL is the public URL used in DSNs and in links in emails, pushes and webhooks. An https:// value also marks session cookies Secure.
• OPENFAULT_TRUST_PROXY=1 makes OpenFault use the first X-Forwarded-For address for login and pairing rate limits. That is right here, because Dokploy’s proxy sits in front.
• OPENFAULT_SETUP_TOKEN pre-sets the one-time setup token. It stops working once the first user exists.

Deploy it

1. In your Dokploy project, open the templates gallery and pick OpenFault.
2. Deploy it. Dokploy fills in the domain and the setup token.
3. Wait for the container to report healthy. The image has a built-in health check that calls /healthz.

Attach your own domain

The generated domain is fine for a first look. For real use, give it a hostname you control, such as errors.example.com:

1. Open the service’s Domains tab and add your domain, pointing at port 8080 with HTTPS on.
2. Change OPENFAULT_HOST in the service’s environment to the same hostname, without https://.
3. Redeploy. Dokploy’s docs say template and compose services pick up domain changes only after a redeploy.

Use HTTPS. The base URL starts with https://, so session cookies are marked Secure, and browsers do not send those over plain HTTP. Dokploy’s docs also note that its free traefik.me domains are HTTP only unless you add a certificate.

Finish setup

Open your domain. The setup wizard asks for the organization name, your name, email and password (10+ characters), and the first project’s name and platform. Email and push settings are optional and can wait. You land on the project’s SDK setup page with its DSN.

The template does not create this account for you. Do it right after the deploy, so the first account is yours. If you would rather script it, the setup token from Dokploy’s environment works with the REST API or the MCP tool setup_instance.

What to do after deploy

1. Check the base URL. The DSN should show your domain, like https://<key>@errors.example.com/1. If it shows the generated domain or localhost, fix OPENFAULT_HOST (which sets OPENFAULT_BASE_URL) and redeploy.
2. Swap the DSN. Keep your Sentry SDK and change only the DSN. Rails, Next.js, Node and Python are the tested SDKs. Per-SDK snippets are in Send your first event.
3. Send a test error. Sentry.captureException(new Error("hello from OpenFault")) should show up as a new issue within a second or two.
4. Set up backups. Everything is in the openfault-data volume. OpenFault has built-in S3-compatible backups to R2, S3 or MinIO.
5. Get the iOS app (optional). The free OpenFault iOS app pairs with your server by QR code and gives you push alerts with Resolve and Mute.

The template pins version 0.1.0. To upgrade later, change the image tag and redeploy. Migrations run on boot.

Coming from Sentry? The full walkthrough is How to switch from Sentry to OpenFault.

Common questions

Is there an official OpenFault template for Dokploy?

Yes. It was merged into the Dokploy templates repository in November 2026 as a community template. It was tested with docker compose, not yet inside a Dokploy instance, so check the steps above after you deploy.

Does the template create the admin account?

No. The template starts the container. You create the owner account in the setup wizard the first time you open your domain.

Where does OpenFault keep its data on Dokploy?

In a named Docker volume, openfault-data, mounted at /data. The SQLite database and the generated secret live there. Back it up with OpenFault’s built-in S3 backups.

Is OpenFault production ready?

No. The server is in active development. Run it next to your current error tracker before you switch that one off.