Pricing
Three flat prices for the hosted service. Pro includes 3 people, $5 a month for each one after. The open source core is free on your own server. Every plan has every check type, incidents, maintenance windows, the badge and feeds, the API and the MCP endpoints.
Hosted plans
Free needs no card, and running it yourself is free with no limits. The paid plans bill monthly through Polar and can be cancelled from the billing page at any time.
Free
$0a month
- Status pages
- 1
- Monitors (HTTP, TCP, DNS, ping, certificate, domain, heartbeat)
- 1
- Monitors per page
- 1
- People on the team
- 1
- Check interval
- 5 minutes
- History
- 7 days
- Raw checks kept
- 7 days
- Slack, Discord, Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and webhook alerts
- Email, Slack, Discord, Teams and webhook subscribers
- Checks from every location in turn, response time from the ones you pick
- Incident updates and post-mortems drafted from the checks
- Components that follow a vendor's status page
- Monthly uptime report by email
- Password-protected pages
- Private pages
- Address
- Assigned
- Your own domain
- Pages without "Powered by StatOSS"
Hobby
$4a month
- Status pages
- 1
- Monitors (HTTP, TCP, DNS, ping, certificate, domain, heartbeat)
- 10
- Monitors per page
- 10
- People on the team
- 1
- Check interval
- 1 minute
- History
- 90 days
- Raw checks kept
- 14 days
- Slack, Discord, Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and webhook alerts
- Email, Slack, Discord, Teams and webhook subscribers
- Checks from every location in turn, response time from the ones you pick
- Incident updates and post-mortems drafted from the checks
- Components that follow a vendor's status page
- Monthly uptime report by email
- Password-protected pages
- Private pages
- Address
- Your choice
- Your own domain
- Pages without "Powered by StatOSS"
Pro
$15a month
- Status pages
- 10
- Monitors (HTTP, TCP, DNS, ping, certificate, domain, heartbeat)
- 100
- Monitors per page
- 50
- People on the team
- 3, then $5 a month each
- Check interval
- 1 minute
- History
- 1 year
- Raw checks kept
- 14 days
- Slack, Discord, Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and webhook alerts
- Email, Slack, Discord, Teams and webhook subscribers
- 1,000 per page. Blocks of 1,000: $5 a month. Overage: 1¢ per subscriber a month.
- Checks from every location in turn, response time from the ones you pick
- Incident updates and post-mortems drafted from the checks
- Components that follow a vendor's status page
- Monthly uptime report by email
- Password-protected pages
- Private pages
- Address
- Your choice
- Your own domain
- Pages without "Powered by StatOSS"
On every plan
- Down, slow and recovery emails
- Incidents with post-mortems, templates and maintenance windows
- A second location confirms every failure
- Uptime target and error budget on the page
- Your logo and colours
- Status badge, JSON, RSS and Atom
- API and MCP endpoints
- Import from other tools, export as CSV
Self-hosted
$0on your own server
The standalone version is the open source core of StatOSS: HTTP checks, the same strip and page, incidents, maintenance windows, and alerts to email, Slack, Discord and a signed webhook, in one container configured with a YAML file. It is MIT licensed, and the only limit on pages and monitors is the machine it runs on.
The hosted plans add the dashboard, six more check types, a second location that confirms every failure, and the API and MCP endpoints.
Get the source on GitHubgit clone https://github.com/kroqdotdev/statoss-standalonecd statoss-standalonemkdir datacp config.example.yaml data/config.yaml# Edit data/config.yaml; the example explains every field.sudo chown -R 1000:1000 datadocker compose up -d --buildQuestions
- Is there a free plan?
- Yes, and it does not expire. Free holds 1 status page and 1 monitor of any type, checked every 5 minutes, with 7 days of history and down, slow and recovery emails. No card is asked for.
- How many monitors does Pro hold?
- 100, across up to 10 status pages, 50 per page. Hobby holds 10. Components do not count.
- What does history mean?
- What the page shows: 7 days on Free, 90 days on Hobby, a year on Pro. Raw checks are kept 7 days on Free and 14 days on Hobby and Pro; the failed-runs lists and the API's raw results read from those.
- How many subscribers can a page have?
- 1,000 per status page on Pro. Blocks of 1,000 more cost $5 a month per page. Overage, enabled per page, bills 1¢ per subscriber a month past the allowance.
- Password-protected or private?
- Password-protected: one shared password. Private: only the people and email domains you allow, each signing in with a link sent to their address. Both on Pro.
- What does a monitor count as?
- One thing being checked: a URL, a port, a DNS record, a host to ping, a certificate, a domain, or a heartbeat. Components, the parts of a product with no check, never count.
- Is pricing per seat?
- Past 3 people on Pro, yes: $5 a month each, billed with the subscription at the month's highest count. Free and Hobby are for one person.
- Can I move between plans?
- Yes, from the billing page. Moving between Hobby and Pro is prorated on the spot. Cancelling takes effect at the end of the period you have paid for, and pages and monitors past the new plan's limits are paused, not deleted.
- Where do the checks run from?
- From Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Hobby and Pro can add 7 more, from $4 a month. On Free the checks run from Aarhus, and a second place in Europe confirms every failure and every slow response before it counts. On Hobby and Pro the regions take turns, a failure is checked from every region at once, and the page says where something is down.
- What do more locations cost?
- London, Paris, San Jose, Toronto and São Paulo are $4 a month each; Johannesburg and Tokyo are $8. Pro includes $4 of them. A fixed IP on a place you added is $4 a month, shared by the accounts that added it. They are billed with the Hobby or Pro subscription, and an ended one runs to the end of the period.
- What is the self-hosted version?
- The open source core of StatOSS, MIT licensed, in one container configured with a YAML file: HTTP checks, the same strip and page, incidents, maintenance windows, and alerts to email, Slack, Discord and a signed webhook. Unlimited pages and monitors. The self-hosting guide walks through it, and the source is on GitHub.
- How is billing handled?
- Through Polar, the merchant of record. Polar takes the card, charges VAT and issues the invoices.