Rootly launched to address one of the biggest problems enterprises face: resolving incidents like critical outages quickly and painlessly.
The company also announced that it closed $3.2 million in seed funding from XYZ Venture Capital, 8VC and Y Combinator. Individual investors, including Bart Mediratta, former CTO of Dropbox; Jason Warner, CTO of GitHub; John Lilly, former partner at Greylock Partners; and Max Mullen, co-founder of Instacart, also participated. Funds will be used to expand the Rootly team and accelerate product development as the company continues to add innovative features and extend its product suite.
Rootly’s incident management platform and Slackbot are designed to help companies resolve incidents faster by automating manual admin tasks and providing insight to prevent them in the future. This has become increasingly important in 2021. Companies such as Slack, Robinhood and most recently Fastly have experienced headline-grabbing outages, demonstrating that no company is immune to chaotic, manual and expensive incidents.
“The problems companies experience have been exacerbated over the past 18 months as teams have gone remote. Not only have incidents become harder to resolve, but engineers are trying to fix issues in less than optimal conditions. For example, they can no longer gather in physical war rooms that mask over poor tooling,” said Quentin Rousseau, Co-founder and CEO of Rootly. “On top of this, system complexity has grown as companies shift towards cloud-native, microservices and depend further on third party services. It is unlikely for one person to possess all of the tribal knowledge required to fix the problem, and anyone who does probably is not going to be available to help in the moment of need. Rootly offers a better way so developers can focus on what they do best, putting out the fire.”
With Rootly, an alert is generated from PagerDuty or customer support and an incident is declared. The Rootly platform then allows team members to respond, communicate and quickly resolve the incident directly from Slack. Once the problem is fixed, Rootly provides retrospectives and actionable insights to keep similar incidents from happening in the future.
“If you use PagerDuty and don’t also have Rootly, you are leaving thousands of developer productivity hours on the table,” said Ross Fubini, managing partner at XYZ Venture Capital. “This team understands the problem at a very practical level; they know where all the pain points are. Rootly’s elegant solution eliminates the need for any company to try to build something similar in-house.”
The Rootly team has been able to successfully tackle the incident recovery problem thanks to the founders’ uniquely suited backgrounds. Quentin was an early Site Reliability Engineer at Instacart who built much of the foundations for Instacart’s system, which went from handling thousands of orders a week to millions, reliably. Co-founder and COO JJ Tang applied his own set of best practices after leading on the product side of Instacart as the company experienced exponential growth over the course of the pandemic. Together, they developed an automated solution capable of seamlessly scaling with the world’s fastest growing companies.
Some of Rootly’s most popular features include:
- Incident Slackbot: Create, manage and resolve incidents directly in Slack. Easily collaborate, looping in the right teams and automate manual admin tasks such as creating incident channels, setting up a Zoom bridge and looping in the right teams.
- Automated Runbooks: From automatically pulling in Datadog metrics and recent GitHub commits to reminding you to update status pages every 30 minutes, runbooks can help debug incidents faster and create a consistent response process every time.
- Retrospective and Metrics: Learn from incidents with the fastest retrospective you'll ever write with an auto generated timeline, no more copy-pasting out of Slack. Rootly provides invaluable reliability insights with all the metrics enterprises care about in one place. Accurate and comprehensive reports help pinpoint exactly where an organization should focus its reliability efforts.
- Integrations: Rootly boosts 20+ one-click integrations, including PagerDuty, Opsgenie, GitHub, Jira, Asana, New Relic, ServiceNow and Kubernetes, to cover everything you need with the tools you already love.
“Incident management is a fundamental problem for engineers. We hear horror stories almost daily, and we’ve experienced these issues and the chaos that ensues firsthand,” said Tang. “Rootly was built to transform the industry. We’ve taken the best practices and tools, those used by companies with million dollar budgets, and made them accessible to any organization through a turnkey solution. This will change the game, saving companies millions in revenue and lost developer productivity.”
Rootly can be implemented in under five minutes.
The Latest
In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
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 ...