Self-host vs. cloud
Same binary, same dashboard, same DSN format, same MCP server — the difference is who runs Postgres and how you're billed.
At a glance
| Self-host | Cloud | |
|---|---|---|
| Where it runs | Your infrastructure | useokapi.app |
| Data location | Your Postgres, never leaves your network unless you ship it out | Shared multi-tenant Postgres, isolated per organization by row-level security |
| Billing axis | Seats only — everything else unlimited | Daily-sliced event/log quotas, seats, projects, retention (per tier) |
| MCP server | Included, every tier | Included, every tier |
| Multi-organization chrome | Off (OKAPI_MULTI_ORGANIZATION unset) — one organization per instance |
On — self-serve signup, organization switcher |
| License/coverage model | 14-day trial, then license or locked-viewing | No lock state — subscription active or not |
| Ops burden | You patch, back up, and scale Postgres | None |
| Update cadence | You choose when to upgrade (subject to the migration gate — see Licensing) | Always current |
Pricing
Cloud (monthly; annual billing gets 2 months free). Bands are enforced as a daily slice with soft overage to 150% — see Quotas & usage.
| Tier | Price | Seats | Events/mo | Logs/mo | Retention | Projects |
|---|---|---|---|---|---|---|
| Hobby | $15/mo | 1 | 100k | 500k | 30 days | 5 |
| Pro | $35/mo | up to 10 | 1M | 5M | 60 days | 15 |
| Portfolio | $75/mo | unlimited | 5M | 25M | 180 days | unlimited |
Self-host (annual, per instance; seats are the only axis — everything else is unlimited on every tier).
| Tier | Price | Seats |
|---|---|---|
| Solo | $79/yr | 1 |
| Team | $249/yr | up to 10 |
| Business | $599/yr | unlimited (priority support) |
Every self-host tier is the full product — there is no feature gating by plan, ever. Canceling a self-host subscription doesn't take anything away either: you keep the version you have, forever (see Licensing).
When to pick self-host
- You need data to stay inside your own network or cloud account (compliance, contractual, or just preference).
- You're comfortable running Postgres and doing your own backups.
- You want a one-time-feeling annual cost with a hard floor — worst case, you stop renewing and keep running the version you have.
When to pick cloud
- You don't want to operate Postgres or think about upgrades.
- You want multi-organization support (agencies, multiple client workspaces under one login).
- You'd rather pay monthly and scale usage up or down without provisioning anything yourself.
Either way, moving your existing Sentry SDK setup over is a DSN change — see SDK setup to get started, or Quickstart for the fastest self-host path.