Roadmap

Heartbeat monitoring you can use today.

• Heartbeat monitors — Fixed time of day or rolling interval, plus a grace window.
• Email alerts — One email when a monitor goes Down. Another when it recovers.
• Dashboard & activity — Status at a glance, heartbeat history, and pause when you need it.
• Copy-paste snippets — cURL, GitHub Action, Node, and Python on every monitor. No agent required.
• Slack alerts — Down and recovery in Slack on every plan. Connect a workspace on Account.
• Discord alerts — Down and recovery in Discord on every plan. Connect a channel on Account.
• Telegram alerts — Down and recovery in a Telegram chat or group on every plan. Connect the Gonewatch bot on Account, then enable it per monitor.
• GitHub Issues — Open a ticket when a monitor goes Down, comment while it stays Down, and close it on recovery. Connect one repo on Account. Basic and Pro.
• Linear tickets — Open a Linear issue when a monitor goes Down, comment while it stays Down, and mark it Done on recovery. Connect one team on Account. Basic and Pro.
• Alert reminders — Re-notify on Basic and Pro if a monitor stays Down, so a single alert is not the only chance to see it.
• Heartbeat payload visuals — Optional JSON on a ping becomes last values, charts, and expandable history. Developer docs cover the API and limits.
• Google or email sign-in — Free plan, no credit card.

Share status publicly, then keep alerts from going silent.

• Public status pages — Branded pages showing monitor health for customers or stakeholders.
• Email fallback when a destination dies — If Slack, Discord, Telegram, GitHub, or Linear fails authorization on an alert, send that same Down, reminder, or recovery to email so a destination-only monitor is not silent.

Fewer false alarms, then team collaboration.

• Maintenance windows — Suppress alerts during planned deploys or known downtime.
• Performance history — Late arrivals and success patterns over time, beyond a single ping.
• Team workspaces & roles — Invite collaborators with viewer or admin permissions.

Deeper routing and controls as your stack grows.

• Microsoft Teams alerts — Down and recovery in Teams for workspaces that already live in Microsoft 365.
• Jira tickets — Open a Jira issue when a monitor goes Down, so a missed job is tracked where the work already lives.
• Outbound webhooks & custom alert routing
• PagerDuty, Opsgenie, and SMS channels
• Official SDKs — Typed client libraries if copy-paste snippets are no longer enough.
• Audit log and scoped API keys
• Organization policies & SSO