"Legacy players in the space have only focused on step one of the entire incident management process — which is simply getting paged. Too many companies were paying a lot of money for this rudimentary ability. So now you get this feature with Rootly On-Call, but it's combined with our holistic platform that is collecting data throughout the entire lifecycle, through incident resolution." - JJ Tang for International Business Times Thank you to IBT Media for this piece highlighting Rootly is ushering in a modern era of incident management tooling 🚀 https://lnkd.in/dusDy3Vy
Rootly
Software Development
San Francisco, CA 3,779 followers
AI-powered on-call and incident response. Trusted by leading companies like NVIDIA, Squarespace, Canva, Figma, and more.
About us
AI-powered on-call and incident response. Beautiful, modern, and Slack-native incident management—from your first alert to retrospective. Trusted by 100s of leading companies including NVIDIA, Squarespace, Canva, Grammarly, Elastic, Tripadvisor, and Figma. See why they rate us 5 stars on G2: https://www.g2.com/products/rootly-manage-incidents-on-slack/reviews
- Website
-
https://rootly.com/
External link for Rootly
- Industry
- Software Development
- Company size
- 51-200 employees
- Headquarters
- San Francisco, CA
- Type
- Privately Held
- Specialties
- Incident Response, Incident Management, SRE, DevOps, SaaS, B2B, Outage Management, Incident Resolution, Site Reliability Engineering, and Crisis Response
Products
Rootly
Incident Management Software
Some things you can automate with Rootly: 🧪 Creating dedicated incident channels, Zoom rooms, and Jira tickets 🧑🏾🤝🧑🏾 Looping in the right teams/responders and assign roles (e.g. Commander) ⏰ Setting reminders and tasks (e.g. updating Statuspage every 30min) 🎤 Communication with stakeholders (e.g. Statuspage, Slack, Email) 📌 Automated postmortem timeline generation and action item tracking 📟 Create and manage on-call schedules and escalation policies 🚨 Page responders directly from Slack 📊 Tracking and visualizing metrics such as MTTR and incident causes 📝 Write postmortems in tools you use like Confluence, Google Docs, and more ...and much more! Will Rootly work with my existing process? Yes! 🔮 Workflow builder lets you customize Rootly (e.g. page Infra and email leadership when incident > SEV1) 🎛️ 70+ integrations across PagerDuty, Opsgenie, Jira, GitHub, Datadog, Zendesk, and API for custom requests
Locations
-
Primary
San Francisco, CA 94102, US
Employees at Rootly
Updates
-
Thank you Tech Times for featuring us alongside leading DevOps companies like Kentik and GitLab as one of their AI-driven companies to watch! "The ethos behind Rootly's approach to AI is to keep the human at the center. Humans need to be free to do the creative work of solving complex problems about their unique systems, while leaving the AI to deal with the toil of writing up summaries and managing schedules. And because Rootly has more data and context than a legacy paging system, it can automatically build context-aware dashboards that prove extremely useful for individuals and teams triaging an incident." https://lnkd.in/dv4ybPxU
4 AI-Driven Companies to Watch in DevOps
techtimes.com
-
Collecting key incident data with Rootly just got even easier thanks to Dynamic Forms 🪄 Your forms can now automatically update based on certain conditions, like the incident type. This allows you to keep your forms short and quick while still tailoring them to collect the specific information you need in different incident scenarios. The best part? Like everything in Rootly, they're wildly easy to set up. Check out this week's post in our (freshly redesigned 💅) changelog for more information and a 2 minute demo! https://lnkd.in/gYT3ZF48
Rootly | 🪄 Dynamic Forms
rootly.com
-
Ever had to scroll through too many fields when declaring an incident? You may be experiencing ‘Incident overhead.’ In our latest article, we explain why this can be a problem and share tips on how to streamline the process. Check it out to learn more! #sre #reliability https://lnkd.in/dbJWg_sM
Rootly | What is ‘Incident Overhead’ and why does It matter?
rootly.com
-
Our partnership with Outreach has been instrumental in our rapid growth! Thanks JP Cheung for driving this relationship and powering up our team!
"...sometimes going with the top brand is worth it." Well, shucks, Rootly 🥰 Rootly was growing fast and their existing sales platform wasn't working for them, so they made a bold move: they stepped away from their current sales software and upgraded to Outreach. They weren't disappointed. Through the combination of world-class tech and the human support of Outreach's reps, their results speak for themselves: ☎️ 41% increase prospects contacted 📅 69% increase meetings scheduled 📬 130% increase emails delivered 🟦 640% increase in LinkedIn prospects contacted Now, they're even "[sleeping] better." Sweet dreams, Rootly. We're rooting for you! Read the full case study: https://lnkd.in/eCzKmNRX
Rootly supercharges their communications
outreach.io
-
We're thrilled to announce that we have been awarded Intellyx's 2024 Digital Innovator Award! This honor is given to less than 1% of the vendors pitching to Intellyx, making it incredibly exciting for us. Intellyx is a renowned analyst and advisory firm that assists business executives and IT leaders in navigating the complexities of digital transformation. Thank you, Intellyx, for this recognition!
-
When it comes to critical tools like your alerting setup, having easy-to-manage yet highly granular permission controls is key. This ensures everyone in your organization can access what they need to without introducing unnecessary risk. We've taken the same approach to granular role-based access control (RBAC) in the Rootly platform and extended it to Rootly On-Call, making it super simple to manage user access across individual features, either in the platform or via your SSO provider. See this week's changelog post for details on RBAC for On-Call and other product updates! https://lnkd.in/gpujVrVT
🔐 Granular Role-Based Access Control Settings for On-Call
rootly.com
-
Rootly reposted this
Who else checked out Google Cloud's postmortem comms from the UniSuper incident? I found the whole situation really interesting from a comms point of view so I wrote up a post with my thoughts on some of the strategic decisions they made in their incident communication, both during and after the fact. Would love to know your thoughts! Do you agree or disagree with any parts of my assessment? Head to the Rootly blog to read the post! https://lnkd.in/g6z7YWc4
Rootly | What we can learn from Google’s UniSuper incident comms
rootly.com
-
"Looks like it’s from 2025" 🛸 👽 We're building the on-call solution of the future, but don't just take our word for it. Here's what our customer Igor Zankovits at Rush Street Interactive had to say when he first saw the Rootly mobile app 😎 Ready to bring your alerting into 2024 (and beyond 🚀)? Book a free demo today at rootly.com/demo.
-
"We actually started building Rootly as an internal tool at Instacart. One of the senior executives asked me 'Isn’t it odd that we're building critical infrastructure tooling ourselves, and we're a grocery delivery company?' I started looking into what we could buy instead, and it turned out at the time there was nothing really out there that solved this problem. And so, my debrief to him ended up being 'Hey, I’m actually gonna go start this company myself, and your best SRE is going to come with me.' And that’s how the company started." JJ Tang, Rootly Co-founder and CEO recently appeared on the Code Story Podcast, sharing the origin story of Rootly and how the company and product have evolved. Check it out! https://lnkd.in/g8EEk5rb
E25: JJ Tang, Rootly
https://codestory.co