Rootly Blog

rootly.com · Company blog · on HN since 2021

Rootly, an incident management and on-call company, publishes posts on SRE practice, incident response, and hiring.

What HN saysMost HN mentions come from Rootly staff and users: job postings, a customer testimonial, and a founder noting their tool automates postmortem write-ups.
18HN people shared it
8linked it in comments
39stories submitted
105story points
3 months agolast shared
2021people per year2026

Most-shared posts

  1. 1
  2. 2
    Homepage
    3 people · first shared 2022
  3. 3
  4. 4
    Rootly New Blog Series: RescueOps
    2 people · 11 points · first shared 2024 · 1 comments on HN
  5. 5
    SRE vs. Platform Engineering – Differences Explained
    2 people · 4 points · first shared 2022 · discussion on HN
  6. 6
    What Doom taught us about AI-assisted incident response
    2 people · 2 points · first shared 2026 · discussion on HN
  7. 7
    Careers
    2 people · first shared 2025
  8. 8
    Pagerduty vs rootly on call
    2 people · first shared 2025
  9. 9
  10. 10
    AI SRE Needs More Than AI: It Needs Operational Context
    1 people · 10 points · first shared 2025 · 1 comments on HN
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
    The Pros and Cons of Embedded SREs
    1 people · 3 points · first shared 2022 · discussion on HN

What HN people wrote when they linked it

aglazer · 2022-09-13
This looks great and cool to see more innovation in the space. We've been using Rootly https://rootly.com and love it.
jjtang1 · 2022-09-12
Roblox one is one of my favourite: https://blog.roblox.com/2022/01/roblox-return-to-service-10-28-10-31-2… FWIW - my company https://rootly.com/ builds a tool that helps automate postmortem write ups (e.g. timeline creation, etc).
sylvainkalache · 2026-08-03
Rootly | https://rootly.com/| design, engineering, GTM, sales | SF Bay, Toronto, APAC Rootly is an AI-native on-call and incident response. Modern Slack and MS Teams native incident management—from your first alert to retrospective. Trusted by 100s of leading companies including NVIDIA, Squarespace, Canva, Grammarly, Elastic, Tripadvisor, and Figma. Hiring across design, engineering, GTM, and sales https://rootly.com/careers#open-roles
rootlyhq · 2025-11-04
Rootly | AI-native on-call & incident response (Slack/Teams) | Remote (US/Canada/Europe) We help engineering teams resolve incidents faster—from first alert to retrospective—used by 1000+ customers like NVIDIA, Glean, Mistral, Figma, LinkedIn, Dropbox, Replit, Grammarly, Cisco and many more. Hiring * Senior Software Engineer (Backend/Rails) * Senior Site Reliability Engineer * Security Engineer * QA Engineer * Senior Solutions Engineer * Staff Product Designer * Product Marketing Manager * Enterprise Account Executive * Developer Relations & Community Manager * Product Engineer Co-op Why Rootly: A passionate team building modern incident tooling that teams actually love; real adoption at scale; lots of ownership and impact. See roles + details: https://rootly.com/careers
cadamsdotcom · 2025-03-06
Seconding this and offering an honest testimonial as a huge fan of JJ and Rootly’s team. I championed and led the introduction of Rootly’s incident management product at two tech companies and counting. Rootly scales well - the Slack bot replaced chains of comms we used to have humans to handle. It’s reliable. And the attention to detail in their product feels like a love letter to SRE. Rootly has the product chops to make a top notch incident management product. The domain modeling they’ve done for Rootly Oncall is solid - it feels like a superset of PagerDuty and Opsgenie. Anyone moving off Opsgenie would benefit from a close look at it. https://rootly.com/landing/pagerduty-vs-rootly-on-call
kwent · 2022-06-07
Great question. Incident.io is likely our closest competitor and are doing amazing work over there. They have a strong team and smart founders that have been in the trenches before. From a product perspective they are my favourite of our competitors if I had to pick one myself to use. Our differences are largely driven by the customer segment we serve and the needs of SMB vs. enterprise. We've found by going upmarket to enterprises such as Canva, Shell, Bolt, it is quite difficult to develop an opinionated platform based on only industry best practices as each organizations approach to incidents (regardless if it's the same tooling) vary greatly in their process. You'll find Rootly to be a lot more pluggable, customizable, and can turn any knob the make the product work for you if needed. The reason for this is because we find change is hard, even small process tweaks in process. We want to reduce as much of that as possible when a new tool is brought in. We've been around longer so naturally our product maturity is further along. Such as Workflows (https://rootly.com/changelog/2021-11-30-workflows-2-0), integrations (30+), Terraform/Pulumi provider, and security (https://rootly.com/security). Again, they do a great job. Just different needs and requirements for startups vs. enterprise. If helpful, customers have written reviews for us on our respective G2 pages: https://www.g2.com/products/rootly-manage-incidents-on-slack/reviews
jedberg · 2025-03-07
Hey there, this page: https://rootly.com/humans-of-reliability Is weirdly broken (at least for me) on Safari on desktop. Every mouse movement or key click causes all the tiles to enlarge. It's fine on Chrome and Firefox.
darkwater · 2025-03-06
Reading the comparison with PD [1] and having been a Pagerduty customer...even if it's promo material for a competitor, it resonates a LOT with my experience with PD (and boy, I do have experience with it). The web UI and the limitations around overrides, paging groups, escalation policies etc are all real and makes me wonder: how is it possible that a behemoth in the space like PD is stagnating like that? I understand, big enterprises as clients which are notoriously slow, being the incumbent and being a big corporation yourself, but still, I don't get it. [1] https://rootly.com/landing/pagerduty-vs-rootly-on-call

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close