Hosted status pages · made in the UK

The status page
operators reach for.

Publish incidents in seconds. Subscribers get notified. Customers stay informed. Built for teams who treat outages as a craft, not a panic.

Start a free page See the product No credit card · 2-min setup
9.4×
Faster incident publication vs. email-first teams
97%
Of subscribers read the first update
2 min
From sign-up to a published status page
status.acme.com RSS · JSON
Acme Cloud
Last updated 14:47 UTC
All systems operational
  • APIcore Operational
  • Dashboardapp Operational
  • Webhooksdelivery Degraded
  • Scheduled jobsbatch Maintenance
  • Public S3 egressdelivery Operational
90 DAYS99.982% uptime
In the box
  • Unlimited components
  • Five-state workflow
  • Per-component subs
  • Custom domain · TLS
  • Audit log
What StatusLayer does

Three jobs, done with care.

A status page only matters on its worst day. StatusLayer is built around the three moments you can't afford to get wrong: declaring an issue, writing about it, and reaching the people who care.

01Declare

Capture reality in one click.

Flip components to degraded, partial_outage, or major_outage straight from the admin. Group, reorder, and hide what the public shouldn't see.

  • Component groups & reordering
  • Append-only status ledger
  • Keyboard-driven admin
02Write

Markdown, sanitised, signed.

Compose incident updates in CommonMark. We render to safe HTML on write, sandbox embedded HTML, and store both forms so subscribers see exactly what readers do.

  • Five-state incident workflow
  • Impact levels & affected components
  • Scheduled maintenance windows
03Reach

Deliverability as a feature.

Subscribers opt in by email, confirm with a signed token, and receive notifications through Amazon SES with proper List-Unsubscribe headers.

  • Per-component opt-in
  • One-click List-Unsubscribe
  • SES bounce handling
Built for the people holding the pager

Who reaches for StatusLayer.

Four teams, one tool. Each gets the same product — and uses it for something subtly different.

SRE & Platform

The team on the pager.

Publish a status change in under a minute at 3am without thinking. Components grouped the way your architecture looks. Templates prewrite the first update so your brain can stay on the incident.

Customer Support

The team answering the phone.

Support opens the status page before Jira. When customers email, the first thing Support does is point to the incident permalink — so the ticket queue stops doubling on every outage.

Founders & Operators

The team explaining it later.

Every incident becomes an artefact you can share with a board, a regulator, or a customer's procurement team. Postmortems live on the same timeline as the incident.

Infra Vendors

The team with customers who have customers.

White-label the page with a custom domain, offer sub-pages, and let users subscribe per-component. Status becomes a product feature, not a separate tool.

The honest comparison

Versus the alternatives.

A fair table. We'll update it when things change — or remove it if we're wrong.

What you're shippingRoll your ownAtlassian StatuspageStatusLayer
Time to first page2 weeks1 hour2 minutes
Incident timelineBuild itIncludedIncluded
Custom domainYourself£££ tierIncluded
Subscriber per-componentNoEnterpriseIncluded
Audit logCustomEnterpriseIncluded
Open pricingN/ATieredSimple
UK data residencyYoursUS by defaultUK · London
Pricing

Simple plans. Honest pricing.

A free Starter plan that's free forever — not a trial, not a teaser. Paid plans only kick in when you outgrow it.

Starter
Free/forever

For one product, one team, one page.

  • 1 page · unlimited components
  • 25 subscribers
  • RSS · Atom · JSON
  • Community support
Start free
Business
£79/mo

For multi-product orgs and infra vendors.

  • 10 pages
  • 50,000 subscribers
  • Concierge migration
  • Priority 1h SLA
Start Business
Frequently asked

Questions, answered.

If what you want to know isn't here, email us — we answer within a working day.

Is there a free plan?

Yes — the Starter plan is free forever. One page, twenty-five subscribers, every core feature included. No trial timer and no credit card. Paid plans only kick in if you outgrow it.

Can I use my own domain?

Yes. Point a CNAME at your tenant subdomain and add a DNS TXT record to verify ownership.

How do subscribers work?

Visitors subscribe by email. We send a signed confirmation link (double opt-in), store only the sha256 of the token, and include one-click List-Unsubscribe headers per RFC 8058.

Where is the data hosted?

United Kingdom. All application data, backups, and email delivery are hosted in the UK.

Can I migrate from Atlassian Statuspage?

Yes. We import components, incidents, and subscribers from a CSV export. A guided migration is available on the Business plan.

Is there an API?

A public JSON API is on the roadmap for v1.1 — GET for every public entity, POST for incident updates. Today, RSS and Atom feeds cover most read scenarios.

Start now

Your next incident
deserves better.

Two minutes to a live page. No credit card. Cancel by deleting — you own your data and can export it any time.