Sentry announced new capabilities for Seer, its AI-powered debugging agent, extending debugging support to local development and code review, and introducing a simplified, flat pricing model with unlimited usage.
“Wherever code breaks, Seer helps you fix it faster,” said Sentry CEO Milin Desai. “It’s the next step in Sentry’s evolution; a fundamentally smarter way to understand what’s happening with your code from development to production, and how to fix it.”
Seer is built on Sentry’s production telemetry, including errors, traces, logs, and metrics. That runtime context allows Seer to diagnose failures that cannot be reliably identified through static code analysis alone, particularly in distributed systems where issues often cross service and infrastructure boundaries.
“After more than a decade of helping developers find and tackle bugs, Sentry has an unrivaled understanding of what breaks in production and why,” Desai said. “With that context, we can move beyond flagging issues after the fact to explaining them in real time, automatically identifying the root cause for developers and their coding agents, and even anticipating problems before code goes live.”
Seer combines source code with live application behavior to identify these problems, including:
- Failures that propagate across services or network boundaries
- Latency spikes caused by contention or resource saturation
- Errors that occur only under production traffic patterns
By analyzing how software actually behaves, Seer focuses on determining why a failure occurred, not just where it surfaced.
“Failures in modern systems often cannot be debugged by simply reading the code,” Indragie Karunaratne, director of engineering at Sentry said. “Seer is designed for that reality. It looks at how services behave together at runtime, which makes it possible to identify root causes that static analysis and code review alone can’t catch.”
With this release, Sentry is expanding Seer’s role beyond production debugging to support developers earlier in their workflow.
Seer connects to local coding agents through the Sentry MCP server. As developers reproduce bugs locally, application telemetry is sent to Sentry, where Seer can analyze raw events and perform root cause analysis. That context can be used by coding agents to generate fixes before code is committed.
Seer can analyze pull requests to identify defects likely to cause production failures. The system is designed to focus on high-impact issues rather than stylistic feedback, helping teams catch real bugs before code is merged.
When bugs reach production, Seer automatically identifies the most actionable issues and performs root cause analysis in the background. When sufficient context exists, it can generate suggested code changes or delegate fixes to supported coding agents.
Sentry is also developing an experimental capability that allows developers to ask Seer open-ended questions about their telemetry. This feature is intended for investigations that begin with symptoms rather than a clearly identified bug, such as unexplained performance regressions or anomalous trends. The capability is currently available in early preview for select customers.
“Seer represents our broader vision: Sentry as the intelligence and reasoning layer for modern software development, and as a platform teams use to see, explain, and fix what matters,” Desai said.
The Latest
For years, infrastructure teams have treated compute as a relatively stable input. Capacity was provisioned, costs were forecasted, and performance expectations were set based on the assumption that identical resources behaved identically. That mental model is starting to break down. AI infrastructure is no longer behaving like static cloud capacity. It is increasingly behaving like a market ...
Resilience can no longer be defined by how quickly an organization recovers from an incident or disruption. The effectiveness of any resilience strategy is dependent on its ability to anticipate change, operate under continuous stress, and adapt confidently amid uncertainty ...
Mobile users are less tolerant of app instability than ever before. According to a new report from Luciq, No Margin for Error: What Mobile Users Expect and What Mobile Leaders Must Deliver in 2026, even minor performance issues now result in immediate abandonment, lost purchases, and long-term brand impact ...
Artificial intelligence (AI) has become the dominant force shaping enterprise data strategies. Boards expect progress. Executives expect returns. And data leaders are under pressure to prove that their organizations are "AI-ready" ...
Agentic AI is a major buzzword for 2026. Many tech companies are making bold promises about this technology, but many aren't grounded in reality, at least not yet. This coming year will likely be shaped by reality checks for IT teams, and progress will only come from a focus on strong foundations and disciplined execution ...
AI systems are still prone to hallucinations and misjudgments ... To build the trust needed for adoption, AI must be paired with human-in-the-loop (HITL) oversight, or checkpoints where humans verify, guide, and decide what actions are taken. The balance between autonomy and accountability is what will allow AI to deliver on its promise without sacrificing human trust ...
More data center leaders are reducing their reliance on utility grids by investing in onsite power for rapidly scaling data centers, according to the Data Center Power Report from Bloom Energy ...
In MEAN TIME TO INSIGHT Episode 21, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses AI-driven NetOps ...
Enterprise IT has become increasingly complex and fragmented. Organizations are juggling dozens — sometimes hundreds — of different tools for endpoint management, security, app delivery, and employee experience. Each one needs its own license, its own maintenance, and its own integration. The result is a patchwork of overlapping tools, data stuck in silos, security vulnerabilities, and IT teams are spending more time managing software than actually getting work done ...
2025 was the year everybody finally saw the cracks in the foundation. If you were running production workloads, you probably lived through at least one outage you could not explain to your executives without pulling up a diagram and a whiteboard ...