Edition 01 · Status communication
StatusLayer is the hosted status page for teams who take outages seriously. Publish incidents in seconds. Keep customers calm by saying what you know, when you know it. Keep your own inbox out of the fire.
Faster incident publication vs. email-first teams
Of subscribers read the first update
From sign-up to a published status page
What StatusLayer does
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.
Flip components to degraded, partial_outage, or major_outage straight from the admin. Group components, reorder them, and hide what the public shouldn't see — all versioned as an append-only status history.
Compose incident updates in CommonMark. We render to safe HTML on write, sandbox any embedded HTML, and store both forms so subscribers and readers always see the same content — never a surprise from a retroactive edit.
Subscribers opt in by email, confirm with a signed token, and receive notifications through Amazon SES with proper List-Unsubscribe headers. Queued asynchronously so your admin never waits on SMTP.
The timeline
Every update posts to a public, permalinked timeline — investigating, identified, monitoring, resolved, postmortem. Readers see what changed and when; search engines index it; your future self can answer "what happened on the 14th?" without squinting at Slack.
Started 14:02 UTC · Impact: Minor · Components: webhooks, scheduled_jobs
Root cause identified as a stuck consumer on queue shard 3. Drained and rotated. All pending events delivered.
Retries catching up — queue depth back under 500. Watching error rate for 15 min.
Issue localised to webhook dispatcher. Failing over affected shard.
We are seeing elevated 5xx responses on the webhook queue. Failovers are healthy, no data loss. Next update in 15 minutes.
Domains & branding
Point status.your-domain.com at StatusLayer with a CNAME, prove ownership with a single DNS TXT record, and your customers never leave your brand. Every page is rendered with the typography, colour, and display name you choose.
Everything included, nothing upsold
Unlimited components, grouped, reordered, with optional descriptions and per-component subscribe toggles.
Investigating → Identified → Monitoring → Resolved → Postmortem. Driven by Symfony Workflow under the hood.
Announce in advance, remind one hour before, auto-transition when the window opens and closes.
Double opt-in, signed unsubscribe tokens, per-component scoping, SES-delivered.
Append-only status ledger — render 90-day strips, calculate uptime, answer "what was the state on X?" in SQL.
Owner, admin, editor, viewer. Tenant-scoped permissions via an explicit access voter — not global roles.
CNAME + DNS-TXT verification per tenant. Multiple domains per status page.
Feed-able timeline so oncall tooling, status aggregators, and your own dashboards can subscribe.
Every admin action — publish, edit, resolve — recorded with actor, IP, and timestamp. Exportable.
Built for the people holding the pager
SRE & platform
You need to publish a status change in under a minute at 3am without thinking. Components are grouped the way your architecture actually looks. Templates prewrite the first update so your brain can stay on the incident.
“If publishing status is harder than opening the runbook, nobody will do it.”
Customer support
Support opens the status page before Jira. When customers email, the first thing Support does is point to the incident permalink. Subscribers email themselves in, so the ticket queue stops doubling on every outage.
“Our CSAT stopped tracking uptime the moment we started subscribing customers.”
Founders & operators
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, so the record is always intact.
“We quote our own status page more than our marketing site.”
Infra vendors
White-label the page with a custom domain, offer your users their own sub-pages, and let them subscribe with per-component granularity. Status becomes a product feature, not a separate tool.
“Our SLA renewals cite the status page — our customers trust what they can see.”
Field notes
Quotes from folks who use StatusLayer day-to-day. Names swapped where requested; details intact.
“StatusLayer replaced three tools — an aging Statuspage plan, a lashed-up RSS feed, and a shared inbox people kept CC-ing. One URL now; everyone found it.”
“The markdown editor is quiet. That's high praise. Nothing is asking me to drag or toggle during an incident — just write the truth and press publish.”
“Custom domain verification worked on the first try. That has literally never happened to me with any other vendor. I told the team.”
The honest comparison
| What you're shipping | Roll your own | Statuspage | StatusLayer |
|---|---|---|---|
| Time to first page | 2 weeks | 1 hour | 2 minutes |
| Incident timeline | Build it | Included | Included |
| Custom domain | Yourself | £££ | Included |
| Subscriber per-component | No | Enterprise | Included |
| Audit log | Custom | Enterprise | Included |
| Open pricing | N/A | Tiered | Simple |
| UK / EU data residency | Yours | US by default | EU / eu-west-1 |
Last reviewed April 2026. We update this table when things change — or drop it if we're wrong.
Integrations
Email delivery via Amazon SES today. Slack, Microsoft Teams, PagerDuty and a public JSON API are on the roadmap — designed as webhook-in, webhook-out so nothing is baked in.
Pricing
Every feature is free while StatusLayer is in beta. When we introduce paid plans, existing pages are grandfathered for 12 months. Full table on the pricing page.
Free for now
1 page · 25 subscribers · community support
Start →£19 /mo
3 pages · 2,000 subscribers · custom domain
Start → recommended£79 /mo
10 pages · 50,000 subscribers · priority support
Start →Frequently asked
If what you want to know isn't here, email us — we answer within a working day.
Yes — every feature is free while we are in beta. When paid plans are introduced, existing tenants are grandfathered for 12 months so you are never surprised.
Yes. Point a CNAME at your tenant subdomain and add a DNS TXT record to verify ownership. A single tenant can run on path-based, subdomain, and custom-domain URLs simultaneously.
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 on every notification.
EU — London (eu-west-1) by default. Email delivery uses Amazon SES in the same region. No customer data leaves the EU unless you configure a different residency yourself.
Yes. We import components, incidents, and subscribers from a CSV export. A guided migration is available on the Business plan; it is a one-time concierge task, not a DIY script.
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.
SupportLayer is a customer support helpdesk. StatusLayer is a status page. They share a design language and authentication system; we run them as sister products rather than bundling them, so you can adopt either independently.
Start now
Two minutes to a live page. No credit card. Cancel by deleting — you own your data and can export it any time.