🔥 Just launched: Auto-Watch Incidents and Required Fields by Incident Type 👀 Auto-Watch keeps you in the loop on incidents that matter most to you. 📝 Required Fields by Incident Type ensures every milestone captures the right context, every time. 👉firehydrant.com/blog/milesto…

✨Introducing Custom Roles & Permissions🔐 Set exactly who can touch what: runbooks, alerts, incidents, service catalog, APIs, and more. All the peace of mind, without putting anything between the fire and the people holding the firehose. 👉Learn more: firehydrant.com/blog/firehyd…

✨Introducing Schedule Rotations in Signals! ✨ On-call schedules can get messy, real fast. Multiple time zones. Shadow rotations. Business vs. after hours. 🤯 Now, it's simple. 👉Learn more: firehydrant.com/blog/introdu…

🤯 Systems are more complex. Incidents are more frequent. And reliability has never mattered more. Looking to build more resilient, scalable systems (with or without a formal SRE team)? This guide's for you. 👉Get it free: firehydrant.com/resource/sre…

🤖 Introducing FireHydrant’s MCP Server, now in beta! AI assistants like Claude or Cursor can tap directly into your FireHydrant data, letting you can manage incidents, alerts, and retros using natural language. 🎉👉Check out the User Guide: firehydrant.com/blog/firehyd…

🚨 91% reduction in mean time to mitigation Scaling rapidly, @backblaze replaced their legacy on-call solution with FireHydrant's all-in-one platform. The result? Streamlined coordination, smarter on-call, and a serious upgrade in ops efficiency 🎉 👉firehydrant.com/customer-sto…

@auditboard ditched their legacy on-call solution for FireHydrant’s all-in-one incident management platform. 🎉 The results? Incident response and on-call now rank among the lowest pain points across their engineering org. 👉Read more: firehydrant.com/customer-sto…

FireHydrant’s new onboarding flow is here — and it’s fast (and delightful). Like, under-5-minutes fast. We've cut set up time by over 90% — so you can easily connect your tools, create your Status Page, and get a head start on Slack. 👉Learn more: firehydrant.com/blog/get-set…

@qlik left legacy on-call tools behind — and redefined how engineering teams manage alerts and incidents. 💥 5–10 minutes saved per incident 👩‍💻 Developers taking ownership of incident response 🔁 One platform for alerts and response 👉Read the story: firehydrant.com/customer-sto…

‼️⏰ Not all alerts deserve a 3 AM wake-up call. With Priority-Based Escalation Policies, you can make sure urgent alerts get top priority while lower-priority ones follow a calmer path 🌴 👉Learn more: firehydrant.com/blog/priorit…

🚀 Introducing The Fire Academy: Your Go-To for FireHydrant Training 🎓 ✅ Interactive courses, videos, and knowledge checks ✅ Tailored training from incident management to Signals to integrations ✅ No extra logins 👉Learn more: firehydrant.com/blog/welcome…