Skip to main content

Sentry Acquires Specto

Sentry acquired Specto, a mobile profiling tool that gives developers data and analytics around their app performance.

The addition of Specto adds deeper context in mobile application monitoring that will bring additional value for Sentry customers.

Amidst an explosion of applications, every development team is under pressure to deliver near-perfect product experiences to retain users and grow their businesses. This is especially true for mobile teams, although these developers have historically been neglected, having few “mobile-first” solutions for application monitoring. But mobile is no longer a standalone platform for most companies, as evidenced by a 200% increase in mobile projects across Sentry’s user base. Having a cohesive platform for error monitoring, performance monitoring, release health, and robust analytics for all languages and platforms enables massive efficiency and gains in application health.

Sentry CEO Milin Desai said the Specto acquisition is part of Sentry’s commitment to bring continuous profiling to a larger audience and code observability to a new level.

“When we added Performance Monitoring to our core platform last year, developers not only saw the power of a singular workflow to see, solve and learn from slowdowns and crashes together, but the cohesion and speed that engineering teams can experience error monitoring, performance monitoring, release health, and robust analytics in one place,” Desai said. “We believe the depth that profiling brings to developers aligns closely with our vision to empower developers to own their application health.”

The acquisition is part of Sentry’s commitment to bring deeper insights and monitoring for mobile applications. Earlier this year the company announced Release Health, which surfaces issues in user experience and pinpoints exactly where a release began to degrade. Armed with data — such as user adoption, application usage, and session data, and insight into the impact of crashes and bugs as they relate to user experience — mobile teams are empowered to deliver reliable, performant apps, and superior application experiences, which is a critical factor in building trust and loyalty with customers.

As part of the acquisition, Specto’s talented and experienced team, including co-founders and former Facebook mobile engineers Jernej Strasner and Indragie Karunaratne, will join the Sentry team. The Specto team brings not only deep profiling experience, but also a first-class commitment to developers, and not just machines.

“Like Sentry, Specto is an engineering-driven company. We’re solving an engineering problem for engineers,” said Strasner.

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

Sentry Acquires Specto

Sentry acquired Specto, a mobile profiling tool that gives developers data and analytics around their app performance.

The addition of Specto adds deeper context in mobile application monitoring that will bring additional value for Sentry customers.

Amidst an explosion of applications, every development team is under pressure to deliver near-perfect product experiences to retain users and grow their businesses. This is especially true for mobile teams, although these developers have historically been neglected, having few “mobile-first” solutions for application monitoring. But mobile is no longer a standalone platform for most companies, as evidenced by a 200% increase in mobile projects across Sentry’s user base. Having a cohesive platform for error monitoring, performance monitoring, release health, and robust analytics for all languages and platforms enables massive efficiency and gains in application health.

Sentry CEO Milin Desai said the Specto acquisition is part of Sentry’s commitment to bring continuous profiling to a larger audience and code observability to a new level.

“When we added Performance Monitoring to our core platform last year, developers not only saw the power of a singular workflow to see, solve and learn from slowdowns and crashes together, but the cohesion and speed that engineering teams can experience error monitoring, performance monitoring, release health, and robust analytics in one place,” Desai said. “We believe the depth that profiling brings to developers aligns closely with our vision to empower developers to own their application health.”

The acquisition is part of Sentry’s commitment to bring deeper insights and monitoring for mobile applications. Earlier this year the company announced Release Health, which surfaces issues in user experience and pinpoints exactly where a release began to degrade. Armed with data — such as user adoption, application usage, and session data, and insight into the impact of crashes and bugs as they relate to user experience — mobile teams are empowered to deliver reliable, performant apps, and superior application experiences, which is a critical factor in building trust and loyalty with customers.

As part of the acquisition, Specto’s talented and experienced team, including co-founders and former Facebook mobile engineers Jernej Strasner and Indragie Karunaratne, will join the Sentry team. The Specto team brings not only deep profiling experience, but also a first-class commitment to developers, and not just machines.

“Like Sentry, Specto is an engineering-driven company. We’re solving an engineering problem for engineers,” said Strasner.

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...