What people actually say about Rootly
32 mentions across 2 sources · 88% positive · researched Jul 3, 2026
Hacker News, Lemmy
What users praise
- • Deep Slack integration for incident declaration and management.
- • AI timeline generation is consistently accurate and saves time.
- • Transparent pricing often half the cost of PagerDuty.
What frustrates them
- • Over-reliance on AI for fixes is risky and discouraged by community.
- • Long-term reliability at scale not yet proven in public data.
- • Limited integration with non-Slack communication tools.
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Rootly review.
What comes up again and again about Rootly
Recurring themes across everything we collected, with where each one showed up.
Slack-first incident management reduces context switching and accelerates response times.
praised · seen on Hacker News, Lemmy
AI features (timeline, root cause) are impressive but not yet trusted for autonomous fixes.
mixed · seen on Hacker News, Lemmy
Cost advantage over PagerDuty makes Rootly a compelling alternative.
praised · seen on Hacker News
Growing enterprise adoption signals reliability and scalability.
praised · seen on Hacker News
Community values open-source contributions like On-Call Health.
praised · seen on Hacker News
Human-in-the-loop remains critical despite AI improvements.
criticised · seen on Hacker News
How hard is Rootly to learn?
Users describe it as beginner · typically 30 minutes to get going
Where people get stuck
- • Setting up Slack integration initially requires admin permissions
- • Customizing incident types and workflows may take a few hours
Who Rootly actually suits
Works well for
- • Engineering teams heavily using Slack for daily ops
- • Teams looking to replace PagerDuty or incident.io with a cheaper alternative
- • SRE teams wanting unified on-call, response, and post-mortem tooling
Not the right fit for
- • Teams that avoid Slack or prefer email/Teams for incident management
- • Teams wanting fully autonomous AI incident resolution without human review
- • Small teams with very low incident volume who may not need the extensive features
What people are discussing right now
Discussion volume is medium and trending up
- AI SRE capabilities and limitations
- Comparison with PagerDuty and incident.io
- On-Call Health open source tool
- Slack-native incident workflows
What people really think about Rootly
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your Rootly report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about Rootly — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on Rootly?
Your scan is ready in under a minute · ₹20 / $1.
Compare Rootly head-to-head
See how it stacks up against the tools people weigh it against.
Top alternatives to Rootly
Researching options? Explore the closest alternatives.
Spider Cloud
AI web scraping API that turns any site into markdown or JSON for AI agents, pay-as-you-go or flat-rate.
Temporal AI
Durable execution platform that keeps AI agents working through failures with automatic retries and state capture.
Presto Voice
Managed drive-thru voice AI for QSR chains, boosting revenue and staff efficiency.
Check sentiment on these too
Run a live scan on the alternatives before you decide.
Rootly — questions buyers ask
What do people complain about most with Rootly?
The complaints that recur most often are over-reliance on AI for fixes is risky and discouraged by community, long-term reliability at scale not yet proven in public data and limited integration with non-Slack communication tools. Drawn from 32 mentions across 2 sources.
What do users like about Rootly?
Users consistently praise deep Slack integration for incident declaration and management, AI timeline generation is consistently accurate and saves time and transparent pricing often half the cost of PagerDuty.
Is Rootly hard to learn?
Users describe it as beginner; most people are up and running in 30 minutes; the usual sticking points are setting up Slack integration initially requires admin permissions and customizing incident types and workflows may take a few hours.
Who should not use Rootly?
Based on what users report, it is a poor fit for teams that avoid Slack or prefer email/Teams for incident management, teams wanting fully autonomous AI incident resolution without human review and small teams with very low incident volume who may not need the extensive features.
What are people saying about Rootly right now?
Discussion volume is medium and trending up. Current topics: AI SRE capabilities and limitations, comparison with PagerDuty and incident.io and On-Call Health open source tool.
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.