Skip to content
Back to the blog

Introducing - StatiBeat:2.0

Detect what needs attention. Bring the right people into the response. Give customers a clear update.

StatiBeat began with StatusPage. StatiBeat 2.0 brings Monitoring and Pager alongside it, connecting the work of spotting a problem, responding to it and explaining its impact.

An incident rarely stays in one tool. A check detects a failure; someone needs to take ownership; customers need an update if the service they use is affected. Our 2.0 preview brings those steps together around Services while keeping each product's job clear.

01 / Detect

Monitoring: see the signal and the evidence

Beats check the endpoints and journeys that matter to your service. Run a check, inspect its result and history, and decide what should happen when health changes. Beat Groups organize related checks; supported private agents can check systems that should stay private. You can also bring in signals from other systems. Explicit connections determine whether a signal leads to Pager, StatusPage or another configured destination.

Explore Monitoring →

02 / Respond

Pager: make the response accountable

Services ring Pagers. People hold Pagers. A Pager keeps its people, shifts, rotations and temporary cover together, so teams can see who is covering each escalation level and when. The same Pager can support multiple Services without copying its schedule.

Organization Response Targets define acknowledgement expectations and escalation timing. Each Service chooses its Pager and Response Target; the Pager supplies the coverage and responders. This lets a regional first level and a continuous second level run independently. Alert activity then shows acknowledgement, escalation, resolution and delivery attempts in context. Delivery methods depend on the relevant configuration and verified destinations.

Explore Pager →

03 / Communicate

StatusPage: explain the impact

StatusPage turns response work into communication customers can understand. Build pages around products, services and regions; publish incident and maintenance updates; and give different audiences focused views, subscriber updates and feeds. Branding, domains and viewer access are available where supported by the plan and page setup. Private response details stay separate from what you publish.

Explore StatusPage →

One organization, with room to grow

Monitoring, Pager and StatusPage sit within one organization, with shared Services linking signals, response and communication. People get access to the work they need. Supported APIs, Terraform, Slack and AI-assisted workflows can help teams extend the process, with the access and features included in your plan.

What's next

Your workspace shows which products and features you can use today. If your organization has not moved to 2.0 yet, keep using your current setup.

Once your organization is on StatiBeat 2.0, you'll be able to enable or disable Monitoring, Pager and StatusPage independently. Choose the products and features you want or need.

Pricing

Updated .

Each approved plan includes Monitoring, Pager and StatusPage under one organization subscription. You won't need a separate subscription for each product.

Compare monthly and annual plans on our pricing page. The beta plans apply when your organization moves to 2.0. Your workspace shows what you can use today. Questions? Talk to us.

Explore the productsAbout the 2.0 previewSign in to your organization
Introducing StatiBeat 2.0Three products. One organization subscription.