Status pages · replacement recipe

Go from Statuspage to Uptime Kuma

The job: Independent status page and basic checks (Incident posts, Service components, Uptime checks, Email alerts). Pick where you are today and where you want to land; the move below follows your pick.

From · what you pay for now
Statuspage
Statuspage Startup · $99/mo
Year one+$308modeled
To · your pickBest fit
Uptime Kuma
Self-hosted · $15/mo + 0.5 h upkeep a month
Change where you land

The money

$99/mo today $15/mo

Statuspage Startup

Year one, net+$308
Pays back in6.8 months

Modeled from public list prices, with your time at $50 an hour. Show the math

Does it do the job? 4 of 4 covered

  • Incident posts
  • Service components
  • Uptime checks
  • Email alerts

The work

Setup
About 6 h + $100
Upkeep
0.5 h a month
Watch out
No SMS, enterprise integration parity or contractual SLA. Hosting must be independent.

Make the move in four steps

  1. Export from Statuspage

    Your page's subscribers (email, SMS and webhook). Format: CSV or JSON

    Export steps

  2. Set up Uptime Kuma

    10 service components; basic checks and email incident notices

    Details

  3. Switch links and integrations

    Point links, embeds and integrations at Uptime Kuma, then send a test through every one.

  4. Cancel Statuspage

    Turn off renewal before your renewal date, once the new setup works. Access runs until: The end of the billing period, or immediately if the billing page offered Click here.

    How to cancel Statuspage
Open Uptime KumaHow to cancel Statuspage
Modeled, not measured. Savings use public prices and planning assumptions: the bill you stop paying, minus the new tool, your upkeep time and your setup time at $50/hour, over the first 12 months. Paths marked Tested by Stackcut were run end to end by us on our own products. They're our tests, not customer results. Check the must-haves in each recipe before you switch.

The whole recipe: 5 ways out, best first

What you use

  • Incident posts
  • Service components
  • Uptime checks
  • Email alerts

Not covered

  • SMS parity
  • Contractual SLA
  • Enterprise notification routing
  • Global monitoring parity

Check before switching

  • Independent hosting
  • Email delivery budget
  • Backup restore tested
  • No unsupported guarantee required

Agents: get_recipe("basic-status") on the Stackcut MCP server.

5 ways out, best first

Open sourcebasic status stackSaves $308 in year one
$99/mo today → $15/mo + 0.5 h upkeep · setup 6 h + $100 · then $708/yr · payback 6.8 mo
10 service components; basic checks and email incident notices
Covers 100% of the core features
License: MIT project; operational independence must be designed, not inferred from a license.
How we got this
You pay now: Statuspage Startupflat price$99/mo
New cost: basic status stack$15/mo
Your upkeep time0.5 h/mo × $50/h$25/mo
Difference each month$99 − $15 − $25+$59/mo
Over 12 months+$59 × 12+$708
Setup, once6 h × $50/h + $100 one-time−$400
Year one+$708 − $400+$308
  • Not counting your time (12 h in year one): saves $908 in year one.

Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team

Sources: atlassian.comgithub.com
Switch vendorOpenStatusSavings not modeled yet
Covers 100% of the core features
License: Inspect current repository license and hosted-plan differences.
Sources: github.com
Open sourceOpenStatusSavings not modeled yet
Covers 100% of the core features
License: Inspect current repository license and hosted-plan differences.
Sources: github.com
Agent skillUptime Kuma MCP serverPriced by usage
Free to install; needs A self-hosted Uptime Kuma 2.x server (open source; a small server you run) (Self-hosted: Free)
Setting up and checking uptime monitors by asking your agent, on a self-hosted Uptime Kuma: create HTTP/ping monitors, add email or Slack alert channels, schedule maintenance and ask what is down, instead of a hosted monitoring plan.
Covers 50% of the core features (not: Incident posts, Service components)
Assumes you already pay for an agent that runs skills (any MCP client; a self-hosted Uptime Kuma 2.x instance); that agent's cost isn't counted. Needs A self-hosted Uptime Kuma 2.x server (open source; a small server you run): priced by usage, so this way isn't priced here. Setup (2 h) and upkeep (0.5 h a month) are Stackcut's estimates; not tested by Stackcut.
License: MIT
Install: npx -y @davidfuchs/mcp-uptime-kuma with UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME and UPTIME_KUMA_PASSWORD set (or the Docker image with -t streamable-http)
Sources: github.comraw.githubusercontent.comatlassian.com
Replace with AIReplace with AI: independent status page and basic checksSavings not modeled yet
Deploy maintained status tooling outside the primary application failure domain; add only required incident workflow.
Covers 100% of the core features
Sources: atlassian.com

Compare before you switch

Read the checked comparisons and workload guides for the tools this recipe replaces.

More Status pages recipes

All 139 recipes · Savings leaderboard · Every vendor, with prices and cancel steps