Rustrak, a self-hosted error tracker for your existing Sentry SDKs Rustrak released a self-hosted error tracker that speaks the standard Sentry protocol, letting existing Sentry SDKs in any language point at it by changing one DSN string, with no new agent or code rewrite. The single-process server defaults to SQLite and, on a 4-core box, accepts a burst of 20,000 events at about 5k events per second while peaking under 60 MB of memory, using two-phase ingestion that writes envelopes to disk and returns 200 before a spawned task does the database work. Rustrak also ingests logs, transactions, release health and AI-agent traces, grouping events by deterministic fingerprint and offering a PostgreSQL compose option for scale. Rustrak is a self-hosted error tracker that also takes logs, transactions, release health and AI-agent traces. It speaks the Sentry protocol rather than a lookalike of it, so the SDK you already have points at Rustrak by changing one string. No new agent to install, no vendor library to swap, no code to rewrite. It runs as a single process with SQLite by default, which means the whole install is one compose file and nothing to provision. Error tracking usually comes two ways: a SaaS bill that scales with your worst day, or a self-hosted stack that wants its own machine. Rustrak is the third option: the same protocol, on hardware you already have. Two design decisions do most of that work. The dashboard is static files the server hands out , so one small process answers both the API and the UI, and an image built without the dashboard is a complete product on its own. And ingestion is two-phase . The endpoint parses the envelope, writes it to disk and returns 200 ; a spawned task then does the database work. Accepting an event never waits on the database, which is what stops a traffic spike from becoming a timeout inside your app. On a 4-core box with SQLite, a burst of 20,000 events is accepted at about 5k events per second with the server peaking under 60 MB of memory. No per-event pricing, no sampling you did not ask for, and no seat you have to justify to anyone. SQLite is the default, so this is the whole install. There is no database to provision and no broker to run. This is the repository's docker-compose.yml : services: server: image: rustrak/rustrak-server:latest ports: "8080:8080" volumes: rustrak data:/data environment: - SESSION SECRET KEY=${SESSION SECRET KEY} - CREATE SUPERUSER=${CREATE SUPERUSER} restart: unless-stopped volumes: rustrak data: export SESSION SECRET KEY=$ openssl rand -hex 32 export CREATE SUPERUSER=admin@example.com:changeme123 docker compose up -d Open http://localhost:8080 http://localhost:8080 and sign in with those credentials. One container answers both the dashboard and the API, so there is no second port and no address to tell one half about the other. Want the dashboard on a different host from your data? rustrak/rustrak-ui is the same dashboard behind nginx; see the production guide https://rustrak.dev/configuration/production dashboard-on-its-own-host . Running at scale? docker-compose.postgres.yml runs the :postgres image next to a PostgreSQL service. The installation guide https://rustrak.dev/getting-started/installation has both setups and the production notes. Rustrak accepts the standard Sentry envelope, so migrating is a configuration change rather than a project. Create a project, copy its DSN, and change one line. Your SDK never learns it is talking to something else. python Python import sentry sdk sentry sdk.init dsn="http://