Launching oops in early access: everything is free for now. Here is what paid plans will include later.
oops catches the errors your apps throw — from a browser SDK, a server-side ingest API or an MCP tool — groups them into issues and tells you how many users each one affects. It is in early access: every account gets the full product at no cost. This post explains what will eventually sit behind paid plans, and what stays free.
oops is the fifth app in the 3m4 family, after the URL shortener, the feature-flag service, the user-feedback inbox and the analytics tracker. It answers one question: what is breaking in my apps, for whom, and since which release? Each project gets a public key; drop one script tag in your site and uncaught errors start flowing into an inbox of issues grouped by fingerprint, with stack traces, breadcrumbs, affected users, environments and releases. No browser? Post to the ingest API from your backend, a CLI or an AI agent.
It is deliberately careful with data: secret-looking keys in tags, extra, breadcrumbs and user objects are replaced by [Filtered], query strings and fragments are dropped from URLs, raw user agents are discarded once browser, OS and device have been read, and IP addresses are hashed unless a project opts in to keep them. The SDK sets no cookie and stores nothing in the browser.
The hosted version at oops.3m4.net is in early access. During early access every account gets the full product: unlimited projects, unlimited events, full data retention, the management API and the MCP server. No card, no trial clock.
What stays free
- Self-hosting. The whole stack is MIT licensed and always will be; a self-hosted instance has no limits beyond the ones you configure.
- A free hosted tier with a few projects, a monthly budget of error events and a sensible retention window.
- The browser SDK, the ingest API, grouping, affected-user counts, releases and environments, breadcrumbs, resolve / ignore, the events log.
- Basic API access with role-scoped API keys, and the MCP server for AI agents.
What will move under paid plans
The things that cost money to run at scale, or that mostly matter to teams and businesses:
- Higher counts: more projects and more API keys.
- Bigger monthly event budgets. Past the budget the ingest API keeps answering 202 (your app never gets a second error back), but the extra events are counted and not stored, and the dashboard tells you.
- Longer data retention (a year of raw events instead of 30 or 90 days).
- Longer audit-log retention (a year or more instead of a rolling week).
- Team seats, roles and priority support.
- Enterprise: SSO, SLA and custom limits.
What happens when plans arrive
The SDK and the ingest API never answer with an error. Whatever plan you end up on, every public key you shipped keeps working.
We will announce the change here and by email before any limit applies to an existing account, with enough notice to export your data or pick a plan.
The planned tiers are already listed on the pricing page so there are no surprises. Prices and limits there are our current intent, not a contract, and may still change before launch.
Questions or opinions?
Early access exists to collect them — and yes, oops uses oops: this very site reports its own errors through its own SDK. Tell us which of the items above you would pay for, and which you would not; it directly shapes the final plans.