A Sentry alternative. Same SDK. Your agent in the loop.
Keep your Sentry SDK and point error reporting at an Okapi DSN. Give your coding agent access to issues and related logs through MCP. Run Okapi yourself today. Flat-priced cloud hosting is coming soon.
Repoint your DSN for new errors
Create an Okapi project and copy its DSN from the project's setup screen. Replace the DSN in your existing Sentry SDK initialization, then send a test error.
import * as Sentry from "@sentry/browser";
Sentry.init({
dsn: "https://YOUR_PUBLIC_KEY@okapi.example.com/1",
});
Sentry.captureException(new Error("Hello from Okapi"));This is a self-hosted DSN; yours uses your instance's host. Okapi Cloud DSNs will use ingest.useokapi.app. Replace the whole example DSN with the one copied from your project. Keep your existing error-capture code. The DSN change routes new errors; it does not move your Sentry history. Configure source-map uploads for browser JavaScript separately using the Okapi guide.
Let your agent work with the error
Okapi's MCP tools let an authorized agent read stack traces and breadcrumbs, find logs correlated by trace ID, and triage issues. Agent tokens or OAuth approvals limit which projects it can see and which actions it can take. MCP is included on every self-hosted plan today, and in the planned cloud tiers.
See the agent workflowKnow what you are switching
Okapi focuses on errors, logs, and agent-assisted triage. It is not a replacement for every Sentry product.
| If you use Sentry for… | Okapi today |
|---|---|
| Error reporting | Keep the Sentry SDK and use your Okapi project's DSN. Source maps work for browser JavaScript; native crash dumps and mobile debug symbols are not processed. |
| Logs alongside errors | Send logs with the Sentry SDK's logs API; Okapi stores them, and the MCP issue context returns the logs that share an error's trace ID. |
| Performance and distributed tracing UI | Not available in the current release. Trace-ID log correlation is not a performance tracing UI. |
| Session replay | Not supported. |
| Cron monitoring | Not supported. |
| Profiling | Not supported. |
Okapi stores error events and logs. It accepts, then discards, everything else your SDK sends — transactions, replays, profiles, check-ins, sessions and attachments — so turn those integrations off when you switch. If you rely on those features, Okapi does not replace them today.
Sentry references: event categories, cron monitoring, and tracing.
One product. Self-host today, cloud coming soon.
Self-host
Run Okapi with Docker Compose: one Go binary with an embedded dashboard, plus PostgreSQL. The 14-day trial starts on first run, without a license key; after it, issue and log details lock until you license, and ingest keeps running.
Cloud — coming soon
Hosted Okapi is coming soon. You can self-host today, or view the planned cloud tiers.