Rootly | LinkedIn (original) (raw)

Software Development

San Francisco, CA 5,154 followers

AI-powered on-call and incident response. Trusted by leading companies like NVIDIA, Squarespace, Canva, Figma, and more.

View all 45 employees

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

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

Employees at Rootly

Updates

What better way to celebrate Friday than with two brand new episodes of Humans of Reliability?! 🥳 This week, we're talking to Tony Holmes, Affirm's Head of Site Reliability Engineering, and Stefan Kolesnikowicz, Principal SRE at Achievers. These two bring deep expertise in the SRE craft and a passion for mentorship and sharing what they've learned with folks newer to the SRE discipline. Watch the interviews now! ➡️ https://lnkd.in/gByTQ2xq
💡Google SREs are writing incident summaries 51% faster thanks to AI. Learn how you can use AI throughout your incident response process to reduce your MTTR and take repetitive tasks off your responders' hands. 👉 https://hubs.ly/Q02Rh2Lk0
Move from alert to incident creation seamlessly, no matter your observability stack, using Alert Sources in Rootly. Our Alert Sources page makes it incredibly easy to view, create, and test alerts from a huge selection of sources including Sentry, Grafana, Datadog, Prometheus Alertmanager, and more from a beautifully simple user interface. We've just added three new native Alert Sources for cloud providers: Azure Monitor, AWS CloudWatch, and Google Cloud. Learn more about how to hit the ground running when things go wrong in our latest changelog post:https://lnkd.in/gkPPe8WH
Rootly | 🚨 New Alert Sources: Azure, CloudWatch, and Google Cloud rootly.com
The only thing we might love even more than our customers are our customers' pets 😍

VP of Engineering at Auror
4d
Thanks JJ Tang. This one is waiting so patiently for her Rootly swag treat.
VP of Platform Engineering at Garner Health, Chris Ferraro, shared how causing a global outage at Microsoft was one of the most formative moments of his engineering career. "I think it's probably the most formative event in my life when it comes to being able to manage through chaos and adversity, and being able to really be there for engineers when things go wrong—because they will. But it taught me how we can all come together in those moments and make the situation better, not worse. It was probably the only moment in my career I ever thought “shoot, should I just walk out the door right now?” but looking back, I'm glad it happened, and it’s certainly made me the man I am today. I'm very thankful for the moment." See our full conversation with Chris (plus new episodes dropping tomorrow!) on Humans of Reliability: https://lnkd.in/gByTQ2xq
We're bringing back our ultra-popular reliability leaders events, and we're bringing our friends LaunchDarkly, Gremlin, and SafeBase along with us! Throughout October, we're holding exclusive invitation-only events for the best of the best leaders in Reliability, Security, and Platform Engineering. This is a unique opportunity to meet industry leaders, share insights, and learn how leading companies are approaching reliability engineering in the modern age. To get on the guest list, check out our Luma Events Calendar (linked below) and request an invite for your city. Don't see your city yet? We're always adding more events, so subscribe to our calendar to be notified of where we're headed next
📞😌 "You've reached 1-800-INCIDENT, please describe the problem you're experiencing and we'll investigate right away!" Wish you had an easy way for your important customers or frontline teams to report emerging incidents directly to on-call responders? Live Call Routing has you covered. Think of it like an incident hotline - dial the number, report the incident, responders get paged immediately. See how easy it is to set up Live Call Routing in Rootly: https://lnkd.in/gNF5BiKz
Rootly | ☎️ Live Call Routing rootly.com
Get a copy of the SaaS Incident Communications Guide, written by our Reliability & Incident Response Advocate Ashley Sawatsky – former Incident Communications lead at Shopify. Free to download at https://lnkd.in/gapi32jW

developer relations @ rootly (ex - shopify, disney)
1w
I made you something 🎁 🥺👉👈 I've strategized incident comms for a ton of hairy situations, including full-scale production outages, security breaches, politically charged events, COVID-19 response, and a bunch in between. Maybe I'm a glutton for punishment, but communicating with people en masse when sh*t hits the fan is where I feel at home. While things are always changing (the tech world loves to keep us on our toes), I hold some strong opinions on what works and what doesn't when it comes to incident communication. I think we've all been failed at one point or another by poor communication during an incident or disruptive event. From canned corporate comms that make you feel less like a human and more like a data point, to downright confusing messaging that leaves you with more questions than answers. It's time to stop the buck-passing and word fluff and learn to own our mistakes as humans and professionals. I've put together an 𝐈𝐧𝐜𝐢𝐝𝐞𝐧𝐭 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 𝐆𝐮𝐢𝐝𝐞, primarily for SaaS companies, that gives you a blueprint to communicating effectively across multiple channels and audiences. No generic templates, just pragmatic advice that's actually applicable in real-world incidents. And you can have it for free! I hope it helps you navigate the challenges that come with incident comms. If you use it, I'd love to hear from you! Head to https://lnkd.in/gRReS5tj and grab yourself a copy.
[Free Resource] Incident Comms Guide rootly.com

Join now to see what you are missing

Join now

Rootly | LinkedIn (original) (raw)

Software Development

San Francisco, CA 5,154 followers

AI-powered on-call and incident response. Trusted by leading companies like NVIDIA, Squarespace, Canva, Figma, and more.

About us

Products

Rootly

Incident Management Software

Locations

Employees at Rootly

Updates

Join now to see what you are missing

Similar pages

Browse jobs