Skip to content
pulseback
Coming soonJoin the waitlist for launch day

Monitoring, on-call and status pages. Finally one calm product.

Pulseback checks your services from multiple regions, wakes the right engineer, points at the deploy that probably caused it, and keeps your customers posted — without per-seat pricing.

Free for 5 monitors when we open. Unlimited viewers on every plan.

SEV-2 INC-482 · Production

API latency increased

Open for 00:04:12
p95 response time120ms → 2.4s
▲ deploy api@a3f9c12
  • Failures confirmed from 3 regions — us-east, eu-west, ap-south
  • Deployed 4 min before degradation · a3f9c12 “Move sessions to Redis cluster”
  • Primary on-call Priya N. paged by push
  • Escalates to Marcus O. in 5 min if unacknowledged
Open incident

Replace StatusCake, PagerDuty, or both

Replace StatusCake

Bring your monitors, keep your history.

Import checks in one step, get 30-second intervals, modern dashboards and status pages included.

Moving from StatusCake
Replace PagerDuty

Rotations without the enterprise maze.

Import schedules and escalation policies. Pay for responders, never for the people who just need to watch.

Moving from PagerDuty
Replace both

One bill. One alert path. One timeline.

The check that fails is the incident that pages is the update your customers see. No glue code in between.

From the first failed check to the postmortem, in one place.

Most teams stitch four tools together and lose context at every seam. Pulseback owns the whole loop.

  1. 01 Detect Multi-region checks confirm before anyone is woken.
  2. 02 Understand Recent deploys and related alerts, attached automatically.
  3. 03 Notify Push that breaks through Focus, email, Slack — escalated until someone answers.
  4. 04 Respond One incident view with owners, notes and evidence.
  5. 05 Resolve Recovery detected, status page updated, team told.
  6. 06 Learn A drafted postmortem from the timeline you already have.
Uptime monitoring

Every way your service can quietly fail, checked every 30 seconds.

Checks run from several regions and are confirmed before they alert, so one flaky network hop never pages your team at 3am.

  • HTTP & API
  • Keyword
  • TCP
  • Ping
  • DNS
  • SSL expiry
  • Domain expiry
  • Cron & heartbeat
Explore uptime monitoring
checkout.acme.dev
99.982% · 90 days
90 days agoToday
us-east
118ms
eu-west
142ms
ap-south
231ms
Platform rotationAmerica/Chicago
Role MonTueWedThuFriSatSun
Primary Priya N. Marcus O.
Secondary Marcus O. Override: Lee Priya N.
  1. 0 min Page primary · push
  2. 5 min Page secondary · push + email
  3. 15 min Notify #incidents and engineering lead
On-call & escalation

The right person, woken once, with the whole story.

Rotations, overrides and time-zone-aware handoffs you can read at a glance. Alerts are grouped and deduplicated, and escalation keeps going until someone acknowledges.

  • Swap a shift from your phone in two taps
  • Repeat pages until acknowledged, recovery sent automatically
  • Full delivery log for every page, call and text
Explore on-call & escalation
Status pages

Tell customers before they tell you.

Status pages stay in sync with your monitors, on your own domain and brand. Post an update from the incident itself — subscribers get it by email.

Explore status pages
Acme statusstatus.acme.dev
Elevated API response times Identified — a fix is rolling out. Next update in 15 minutes.
Dashboard Operational
Public API Degraded
Webhooks Operational
Reliability before features

Your pager keeps working, even when we don’t.

Alert delivery and escalation run on infrastructure separate from the dashboard. If our app goes down, your 3am page still happens.

  • Independent alert path Escalations are scheduled durably and keep firing through a control-plane outage.
  • Every channel, with fallback Push, email, Slack and webhooks — retried until delivered, with email as the fallback.
  • Exactly-once paging Idempotent processing means one outage is one page, not forty.
  • A full audit trail See who was paged, how, and when they answered — for every alert.
Built for developers

Monitoring as code, from day one.

A REST API and Terraform provider for everything you can click. Organize by project and environment, and review monitor changes like any other pull request.

Read the API docs
# monitors.tf
resource "pulseback_monitor" "checkout" {
  url      = "https://checkout.acme.dev/health"
  interval = 30
  regions  = ["us-east", "eu-west", "ap-south"]
  confirm  = 2
  escalation_policy = pulseback_policy.platform.id
}

Priced on what you monitor, not who’s watching.

Unlimited viewers and collaborators on every plan. Need more monitors, responders or messages? Move up a plan, or talk to us about custom limits.

  • Free

    $0

    • 5 monitors · 1 responder
    • 5-minute checks
    • Email & push alerts
    • 1 status page
    Join the waitlist
  • Starter

    $19 /mo

    • 25 monitors · 2 responders
    • 60-second checks
    • AI incident summaries
    • Custom-domain status page
    Join the waitlist
  • Team

    Most teams

    $49 /mo

    • 100 monitors · 5 responders
    • 30-second checks
    • Rotations & escalations
    • Slack · 3 status pages
    Join the waitlist
  • Business

    $129 /mo

    • 500 monitors · 15 responders
    • Advanced workflows
    • SSO & analytics
    • 10 status pages
    Join the waitlist
  • Enterprise

    Custom

    • Custom limits
    • Contractual SLAs
    • Advanced security
    • Priority support
    Talk to us

Compare every plan

Get paged when Pulseback launches.

Pulseback is almost ready. Join the waitlist and we’ll email you the day it opens, Free plan and all.

We’ll use your email to tell you when Pulseback opens. Privacy