Like your team, Sentry moves fast. We eat our own dog food, drink our own champagne, take our vitamins, and monitor for errors. We’re obsessive about building the most important features and enabling the best possible experience to serve every developer everywhere.
One of the great benefits of having tens of thousands of Sentry users sending billions of data points every month is that we’re able to see a massive variety of events and patterns, including those that are a reflection of usage and workflows, not just code errors and crash reports.
So, in the spirit of making Sentry as easy to adopt and scale as possible for all types of users, we’re rolling out new outcomes-oriented pricing plans. Wait, what the heck?
Counting Events is the Biggest Barrier to Success
Yeah, that’s right: outcomes. The more attention we’ve paid to customer use cases, the more we’ve come to understand that counting events is the biggest barrier to success. Ultimately, the only number of events that aligns to every objective for error monitoring is MORE. Flexibility is among the most important features Sentry offers, and packaging to enable greater flexibility at lower total cost is the only way to ensure every Sentry user can drive the outcomes they care about, from faster issue resolution to proactive triage to root cause targeting to reducing technical debt.
In order to help drive the goal of outcomes, the new plans are designed to give you greater observability and let you track more errors without worrying as much about the cost of each event. The decisions you make about monitoring, as well as how you align product development priorities, relies on seeing things that you didn’t previously know were important. So, if better resolution workflows are a priority, there’s a plan with the features you need to support them. If easier event allocation and management is important, the new pricing plans make it easy to prioritize that, too.
What that actually means: Sentry users have told us (and we’ve seen) that they run out of events before diving into key use cases or adopting the workflows that help prevent, not just detect, errors. You love that it’s open-source and that it’s simple to get started, but guessing how many events you’ll need for the next month or year can actually compound the problem you set out to solve in the first place. Setting the bar for events too low sucks, especially when you really start to achieve developer efficiencies and want to scale.
Discovering More Reasons to Monitor & Setting More Interesting Goals
Better error monitoring makes your entire team more effective and able to focus on improving your product so that more users use it more. That means not only needing more events as you scale, but also discovering more reasons to monitor and setting more interesting goals. If you’re worried about hitting your events cap, and if each additional event carries a marginal cost, that uncertainty forces you to take your eye off the ball.
With outcomes-oriented pricing, you’re allotted more events than your first, second, third, fourth, and fifth use cases will likely require without any of the extra expense. As your monitoring starts to depend on more breadth and structure, Sentry levels-up on event bandwidth along with the features you need, like our export API, data forwarding, and per-project rate limiting. Plus, with annual discounts under contracts (versus having to pay in advance), it’s way easier to adopt a plan that suits your development roadmap, not blocked by typical up-front billing hurdles.
So, please welcome bigger, better error monitoring into your dev stack with Sentry. Still open source and easy to use, but now with plans assured to give you more events and features so your team can focus on building awesome products and gaining more insight, not counting bugs.