One audience per page, not one page per company.
Every organisation gets a root page on its subdomain, plus as many path-scoped pages as the plan allows. Each one has its own monitors, its own incidents and its own branding — and they all run from the same account and the same checks.
A root page, and a path for each one after it.
No second subdomain to register and no second account to invite people into. The first path segment names the page.
acme.statusowl.appThe default page for the organisation. Exactly one page holds this slot.
acme.statusowl.app/euA separate page with its own monitors, incidents and branding.
acme.statusowl.app/incidents/{uuid}The permanent public page for one incident, safe to link from a support reply.
acme.statusowl.app/eu/incidents/{uuid}The same, scoped under the page the incident belongs to.
acme.statusowl.app/eu/maintenance/{uuid}Scheduled against actual times, on the page that owns the window.
A path that does not match a page returns a 404, and so does a page that is unlisted or switched off.
They share an account. They share nothing else.
A second page is a genuinely separate page, not a filtered view of the first one.
Monitors
Each page carries its own set of attached monitors. The same monitor can appear on more than one page, so a shared database can show on both the customer page and the internal one.
Incidents
An incident belongs to one page. Opening an incident on the EU page does not put a banner on the US page, and deleting a page removes its incident history with it.
Maintenance
Windows are scoped the same way, so announcing work on one product's page leaves the others alone.
Branding
Logo, page name, description and light / dark / auto default are per page. A white-labelled customer page and your own page can look nothing alike.
Visibility
Public, Active and Default are per-page switches. One page can be published while the one next to it is unlisted.
Domain
A custom domain binds to a single page. status.acme.com resolves to the page it is attached to and does not expose the sibling pages under it — give each page its own domain if you want them all on your own DNS.
Unique within your organisation, checked before you save.
The slug is the path segment. Two pages in the same organisation can never claim the same one, and exactly one page holds the root — the database enforces both, not just the form.
apiadminsettingsconfighealthstatusembedwidgetsubscriberssfeedjsonxmlThese are held back because they collide with routes the platform serves or may serve. Reserving them now means adding a route later cannot break a page you have already published and linked.
- Length
- 2–50 characters
- Characters
- a–z, 0–9, hyphen
- First and last
- Letter or number
- Consecutive hyphens
- Not allowed
- Uniqueness
- Per organisation
- Root pages
- Exactly 1
Changing a slug changes the page’s URL. If you have already put the old one in a footer or a support macro, update it there too — the old path will start returning a 404.
Four ways people actually use this.
The common thread: the fewer irrelevant services a reader has to scroll past, the more useful the page is during an incident.
One page per product
If you sell three products to three different buyers, one combined page serves none of them well. Give each its own page and its own URL, and let a customer watch only the thing they pay for.
One page per region
A EU-only outage does not need to worry your US customers. Split the page by region and each audience reads a page that is actually about them.
One page per customer
Agencies and platforms can run a page for each client, branded with that client's logo and scoped to the services running on their behalf.
Public and internal, side by side
Publish the customer-facing page and keep an unlisted one for the queue workers, the staging stack and the internal tools — same account, same monitors, different audiences.
Priced per page, not per subscriber.
The page count is the axis the ladder is built on. Nobody is charged more because more people read the page during an outage.
| Plan | Per month | Status pages | Who it is for |
|---|---|---|---|
| Free | $0 | 1 | One page for a side project, an open-source tool, or a first product. |
| Starter | $19 | 3 | A team running one product that needs a page customers actually trust. |
| Growth | $49 | 10 | Several services, several audiences, and internal pages alongside public ones. |
| Scale | $149 | Unlimited | Agencies, platforms and enterprises running a page per customer or per region. |
One page per product, per region, or per customer. Private pages count against the same allowance as public ones.
Start with one page. Add the rest when you need them.
The root page is free forever, with your own domain and SSL. Adding pages is a plan change, not a migration.