- REST API
https://app.pulseback.io/api/workspaces/:wid/… - Events API
POST https://app.pulseback.io/api/v1/events - Heartbeats
https://app.pulseback.io/hb/<token>
Get started
Monitoring
- Monitors & check types The nine check types, the settings every monitor shares, how multi-region confirmation decides when something is down, and importing from StatusCake.
- Heartbeats & cron Watch backups, queues and scheduled jobs. Your job pings a URL when it runs; Pulseback pages when a ping is late or reports a failure.
Alerts in
- Events API Open, acknowledge and resolve incidents from your own tools with one POST. The payload is compatible with PagerDuty Events API v2.
- Email integration Turn any email into an incident with an address of its own, and acknowledge or resolve alerts by replying to them.
- Deploy tracking Send deploys from GitHub or any CI so incidents open with the change that probably caused them.
Respond
- On-call & escalation Schedules, overrides and swaps, escalation policies, personal notification rules, and how incidents move from triggered to resolved.
- Workflows (routing rules) Ordered event rules that route alerts by source, payload, tags or time of day — set severity, pick the escalation policy, open quietly or suppress noise.
- Status pages & custom domains Publish a status page that follows your monitors, post updates from incidents, schedule maintenance and serve it from your own domain.
Automate
- REST API & API keys Everything you can click, over HTTPS with a workspace API key. Authentication, conventions, errors and the endpoint groups.
- Terraform provider Manage monitors, on-call schedules, escalation policies, status pages, maintenance windows and integrations as code, reviewed like any other pull request.