Okapi
About

I got tired of paying for bad days.

I built Okapi after one too many $400 spike-months — a small, independent error tracker that's flat, self-hostable, and agent-first. The honest answer I wanted for myself.

JR
Justas Raudonius
Founder of Okapi · building it in the open
@justraud

Every metered error tracker makes the same bet: that you won't notice the overage until the invoice lands. One runaway loop, one bad deploy, and a tool that costs $35 at baseline bills you five figures for a single afternoon. I'd lived that — and I didn't want to build a product that profits from your worst day.

So Okapi is flat. It's one Go binary and a Postgres database you can run yourself, with a native MCP server so your coding agent does the triage. Every plan is the full product. Your limits never shrink. And if you ever want out, you self-host and keep the version you have — forever.

What I believe.

01
Pricing should be boring
Flat plans, no overage bills, no feature gating. The price you pick is the price you keep.
02
Agents are first-class
The MCP server isn't a bolt-on. It's how modern debugging works, so it ships on every plan.
03
Your data is yours
Self-host so product data stays on your infrastructure, with limited license and update checks documented in full — or use our cloud.

Start catching errors before your users do.

A 14-day trial. One binary to self-host. MCP on every plan — and a price that never moves.

14-day trial · Sentry-SDK compatible · Self-host or cloud