saysOK vs Atlassian Statuspage
Statuspage is Atlassian's status page product: you tell it what is happening, or feed it data from other tools. saysOK runs the checks itself, so the page changes when your product does, and it costs less for the same page.
- Hobby plan
- $29
- 5 team members, 250 subscribers
- included
- Pro, flat
- $19
- 5 seats, 5,000 subscribers
- included
- 50 monitors checking it
- included
Side by side
saysOK's column is what its plans include today. Statuspage's is what its pricing page said on Oct 16, 2026; check there for current figures.
| What is compared | saysOK | Statuspage |
|---|---|---|
| Price | ||
| Price for a public page | $19 or $79 a monthPro or Team, flat per workspace | $29, $99, $399 or $1,499 a monthHobby, Startup, Business or Enterprise |
| Team members | 5 or 10 seatsPro or Team; $4 a month per extra seat on Team | 5, 10, 25 or 50Hobby, Startup, Business or Enterprise |
| Free plan | 10 monitors5 min interval, 1 status page | 100 subscribers25 components, two team members; email, Slack and Microsoft Teams notifications |
| Status page | ||
| Subscribers per page | 5,000 or 25,000Pro or Team | 250, 1,000, 5,000 or 25,000Hobby, Startup, Business or Enterprise |
| Your own domain | Pro or Team | From Hobby |
| Password-protected or private page | IncludedA page can be public, behind a password, or private | From $79 a monthPrivate pages, priced separately |
| SMS to subscribers | Included | From Startup$99 a month |
| Monitoring | ||
| Checks your product itself | YesHTTP, keyword, TCP, ping, DNS and SSL checks; components follow their monitors | Not describedIts pages describe updates by your team and data imported from tools such as Pingdom, New Relic and Datadog |
| On-call and escalation | Included | Not described |
What your page would cost
Set how many people subscribe and how many people on your team update the page. Both are for a page on your own domain. Statuspage's figures are its listed monthly prices from Oct 16, 2026; tax is left out of both.
Statuspage Hobby, $29 a month; saysOK Pro, $19 a month.
What happens at 02:14 with saysOK.
One night at a made-up product, step by step: what saysOK does on its own, what your team sees, and what your customers read.
- Your teamThe check from Frankfurt gets HTTP 503From api.acme.example/health. One region only, so nobody is paged yet.02:14:00
- Your teamVirginia sees it too: incident openedSEV-1. Maya, primary on call, gets a push notification and the Slack message at once.02:14:07Your status page“We are investigating an issue affecting API.”Nobody typed it: the page and its subscribers are updated from the incident.
- Your teamMaya acknowledgesFrom the Slack message. The secondary on call is never woken.02:16:30
- Your teamChecks pass from every region: resolvedThe incident resolves itself, and the Slack message says so.02:29:50Your status page“This incident has been resolved.”API is operational again, and subscribers are told.
- Your teamThe post-mortem is writtenStarted from the incident's timeline.09:30:00Your status pageThe post-mortem goes on the pageUnder the incident, for customers to read.
- Down for
- 15 min 50 s
- Customers told
- at 02:14
- Status updates typed
- none
Which one fits
Neither is right for everyone. This is how we would choose.
Choose Statuspage if
- You already run monitoring elsewhere and only want a page your team updates by hand.
- You need a status page with more than 25,000 subscribers, or audience-specific pages for different customers.
- Your company standardises on Atlassian, and the page should sit next to its other Atlassian tools.
Choose saysOK if
- You want the page to change on its own when a check fails, not when someone remembers to update it.
- You want monitoring, on-call and the status page in one product and one bill.
- A page on your own domain with up to 5,000 subscribers, for $19 a month.
What saysOK includes
Part of the product, not sold as an add-on.
On-call, with a next person if nobody answers
A schedule says who is primary and who is secondary each day. An alert rule pages them in steps: when an alert is not acknowledged in time, the next person is paged.
- at once Slack · #alerts
- +5 min Primary on-call, if not acknowledged
- +10 min Secondary on-call, if still not acknowledged
Every incident keeps its record
A timeline of what was detected, who acknowledged and when it was resolved, with a severity from SEV-1 to SEV-4. Write the post-mortem from it and publish it to your status page.
- 02:14:07Detected: Acme shop is down
- 02:14:08Maya paged by phone call
- 02:15:31Acknowledged by Maya
- 02:31:10Resolved: checks passing again
Cron jobs and backups, next to the uptime checks
A heartbeat monitor expects a ping from each scheduled job and alerts when one does not arrive, so a backup that silently stopped is found the same day.
# crontab: report in when the backup has run
0 3 * * * backup.sh && curl -fsS https://saysok.com/api/heartbeats/YOUR_TOKEN/pingAn API, and a way in for AI assistants
Monitors, incidents and heartbeats are reachable over a public REST API. The MCP endpoint lets assistants such as Claude Code and Cursor work with them too.
curl https://api.saysok.com/v1/monitors \ -H "Authorization: Bearer YOUR_API_KEY"
claude mcp add --transport http saysok https://api.saysok.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
Try it on your own sites.
The free plan covers 10 monitors and one status page. Move to Pro or Team when you need faster checks or seats for a team.