Loading page
Loading page
Monitoring · Sentry alternative
Track app errors with your existing Sentry SDK, in one small container with an MCP server for coding agents.
OpenFault is an error tracker that speaks the Sentry protocol. Your app keeps its Sentry SDK. You point the DSN at OpenFault, and crashes, releases and breadcrumbs start to show up as issues.
It is built to be small. Everything runs in one container with SQLite inside, and the project says it uses under 100 MB of RAM. It is also built for coding agents: an MCP server gives tools like Claude Code and Cursor the same view of issues that the web UI uses.
It fits solo developers and small teams who want error tracking without a monthly event quota. It also fits people who already let a coding agent fix bugs and want the agent to read errors directly.
Hosted error trackers bill by event volume, and error data can include user details and stack traces. A self-hosted OpenFault keeps that data on your own service and has no event quota.
Be careful with the trade-off. The README says OpenFault is in early development and not ready for production. Keep your old tracker running while you try it. You also handle updates, which are pull and restart, and backups of the SQLite file.
Containers: ghcr.io/openfault/openfault:0.1.0
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose OpenFault, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the OpenFault setup screen.