Hosted Pricing Just Got Cheaper
In short: this is a pricing update where prices went down (by at lot) and the structure got more gradual. The main changes are:
- Free tier tripled: 5K → 15K events
- First paid tier: 50K → 75K events (same price)
- High-volume tiers added: no more €15 → €500 jump, instead there are now tiers at 300K,
Go-live was February 22, 2026.
What Got Cheaper
The structure is flatter and more gradual, especially for teams that expect to grow. Here’s the full table:
Old pricing - Free: 5K events, 1 user - Teams: €15/mo for 50K events - Enterprise: €500+/mo New pricing - Free: 15K events (5K retained), 1 user - 75K: $16/mo - 600K: $50/mo - 3M: $158/mo - 15M: $568/mo - 50M: $1,288/mo
If you are currently on the €15 “Teams” plan, you get to keep that price. For that same price you will now get 50% more events. There are no surprise migrations or forced upgrades hiding behind this update.
The updated pricing page has more details (and allows for actual signup).
Pricing Compared to Sentry
We’ve long claimed that Bugsink can be around 80% cheaper at scale compared to Sentry. That was originally about self-hosting with support. With these hosted tiers, that claim also needs to hold up for managed deployments. It does.
At 50M events per month, Sentry’s Team pricing lands at $6,441. Bugsink is $1,288. That works out to about $0.13 per 1,000 events for Sentry versus roughly $0.026 per 1,000 events for Bugsink, an 80% difference.
At lower volumes the gap is smaller but still clear. Around 75K events per month, Sentry lands roughly in the $36–44 range (based on their published Team pricing), while Bugsink is €16. The difference is about 50% at that point, and the gap widens as you grow.
The free tier offers 15K error events versus Sentry’s 5K, i.e. even for free, you get 200% more events. (For the pedantic: claiming X% cheaper is undefined when the price is zero, but the point is that you get more for free.)
Why the Change?
The old structure had a wide gap between roughly €15 and €500+. That gap created awkward decision points. Teams would hesitate to enable more instrumentation, worry about crossing invisible lines, or delay moving to hosted because the next step felt disproportionate. It also gave the impression that hosted was only for teams with very large volumes, which isn’t the case.
This update closes that gap and makes growth feel incremental instead of dramatic. You can move from tens of thousands of events to millions without entering a different pricing universe overnight. The tiers now reflect how usage actually grows in practice.
There is a simple principle here: when in doubt, offer more. Lower cost pressure changes behavior. Teams track more errors, argue less about volume, and use the tool more freely, which ultimately leads to better debugging and better software.
Why This Works
This change comes from looking at how teams actually grow. The previous gap between €15 and €500+ didn’t match real usage patterns, where volume increases gradually rather than in sudden jumps. The pricing now reflects that progression more closely and removes artificial cliffs.
It’s also sustainable because the engineering supports it. Bugsink’s ingestion and storage model are designed to run lean, even at higher volumes, which is described in more detail in Scalable and Reliable. The hosted tiers follow from what the system can handle efficiently in practice. Pricing here is a consequence of the architecture, not a temporary promotion.
Closing Thoughts
Hosted Bugsink is now structured to scale from small projects to serious volume without cliffs or surprises. The tiers reflect how teams actually grow and what the system can handle efficiently in practice.
If you looked at hosted before and decided it wasn’t the right fit, this might be a good moment to take another look.
It’s March 3 as I’m writing this, so yes, this post is late. Fortunately, announcing price reductions is easier to get away with than announcing increases.