Bring your monitors, keep your history.
Import your checks in one step and get 30-second intervals, modern dashboards and status pages, with on-call and incident response in the same product.
Imports your checks, their settings and their last 90 days of uptime history, so your status page bars don’t start from zero.
Everything you set up has a place to go.
| In StatusCake | In Pulseback |
|---|---|
| Uptime tests | Monitors: HTTP, keyword, TCP, ping (TCP connect), DNS Checked from several regions, every 30 seconds on Team and up. |
| SSL monitoring | SSL monitors: validity and expiry, degraded days before it runs out |
| Domain monitoring | Domain monitors: registration expiry over RDAP |
| Contact groups | Escalation policies and each person’s notification rules Plus on-call schedules, so alerts reach whoever is on call now. |
| Status pages | Status pages, linked to monitors and updated from incidents |
| Alert integrations | Push, email, Slack and signed webhooks |
An afternoon, not a project.
- 01 Start a workspace Sign up free. No credit card, and the Free plan is enough to try the import.
- 02 Import your checks In Monitors → Import, paste a StatusCake API key or upload a CSV export.
- 03 Review what moved Pulseback lists what it created and what it skipped, with a reason for each.
- 04 Decide who gets paged Pick regions and an escalation policy, then send yourself a test page from your account.
- 05 Run side by side Keep both running for a week if you like. When you trust it, turn the old alerts off.
The check that fails is the incident that pages.
Monitoring is where Pulseback starts, not where it stops. The same product wakes the right person and keeps your customers posted.
-
On-call built in
Rotations, overrides, swaps and escalation that repeats until someone acknowledges.
-
The likely cause
Deploys from GitHub or a webhook are matched to failures, so the incident opens with a suspect.
-
Confirmed alerts
A monitor is down only when several regions agree and a re-check fails too.
-
Heartbeats and cron
Watch backups, queues and scheduled jobs with a ping URL and a deadline.
-
Status pages in sync
Components follow their monitors; post updates from the incident.
-
Viewers are free
Pay for monitors and responders. Everyone else watches for nothing.
Moving from StatusCake
Do I have to change anything on my servers?
No. Pulseback checks the same URLs, hosts and ports from the outside. If you allowlist monitoring traffic, allow Cloudflare’s network, which our checks run on.
What does the import bring across?
Your checks (names, targets and settings that have a Pulseback equivalent) and, with an API key, their last 90 days of uptime history. Anything that doesn’t map to a Pulseback check type is listed as skipped with the reason, so nothing disappears silently.
Can I import without an API key?
Yes. Upload a CSV export instead. The importer reports what it created and what it skipped either way.
Is ping a real ICMP ping?
No. Our checks run on Cloudflare’s network, where ICMP isn’t available, so a ping monitor measures the TCP connect round-trip to a port you choose (443 by default). For most hosts that’s the number you actually care about.
What happens to my status page?
Create one in Pulseback and link its components to your monitors. On Starter and up, point your status subdomain’s CNAME at status.pulseback.io when you’re ready to switch.
StatusCake is a trademark of its owner. Pulseback isn’t affiliated with or endorsed by StatusCake. This page describes how Pulseback works and how to move over; check StatusCake’s own documentation for its current features and pricing.
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.
Join the waitlist