A status page company should be the last business on earth to oversell. So this is the unflattering list: what StatusOwl cannot do today, what each of those things will do once it ships, and where it actually stands right now. Several of these are things a competitor would simply not mention.
If you are choosing a status page, the thing you most need to know is what it will not do for you during the outage you are buying it for. Every item below is written to be checkable against the product on the day you read it.
There are no quarters, no target releases and no promises on this page. When something ships it moves to the changelog and gets a real date there. That is the only date you will get from us.
Some of these have working code behind them and are still capped, unwired or missing an interface. Where that is the case the entry says so, in the same words we would use internally.
None of this appears in a pricing table, a feature list or a comparison row anywhere else on this site. If you cannot use it today, it is not on the invoice.
Being worked on right now. These are the gaps we think do the most damage to the product as it stands.
Let visitors subscribe to a page by email and get notified when you open, update or resolve an incident — and when maintenance is about to start.
Not built. There is no subscribe form on status pages and no subscriber list in the dashboard. Publishing an incident today updates the page; it does not send anything to anyone.
Route a failing check to email, Slack, Discord, Microsoft Teams, ntfy or a signed webhook, with a recovery notice when it comes back.
The six notification channels are built, tested and in production — but the only thing that currently triggers them is a Watch Owl server-metric alert rule. A failing HTTP, ping or TCP check opens an incident on your status page and notifies nobody. This is the single biggest gap in the product and it is what we are working on right now.
Queued behind the work above. Several of these are partly built already — each entry says which parts exist and which do not.
Check each monitor from several regions at once and require agreement before an incident opens, so a single flaky vantage point cannot post a false outage.
Fully built and deployed — monitors carry a region list, nodes are assigned per region, and the scheduler already dispatches per region. It is capped at one region per monitor on every plan until we have enough node capacity in more locations to promise it.
Bring your own stylesheet and header/footer markup for a page that matches your product exactly.
The renderer supports and sanitises custom CSS, header and footer — but there is no editor in the dashboard yet, so the fields cannot be set.
Put a shared password or SSO in front of an internal status page, instead of relying on the URL being unlisted.
Private pages exist today but 'private' means the page returns a 404 to anyone without the link. There is no password and no SSO gate.
Open and update incidents from your own tooling, and receive a webhook when page state changes.
The public API is live with per-key rate limiting and scopes, but only two read routes exist today: list monitors and get monitor. There are no write endpoints.
Not started. Listed so you can see they are not close, rather than assume from a feature grid that they exist.
Bring your components, past incidents and subscribers across in one step.
Not started. Migrating today means recreating components by hand.
Enterprise single sign-on for the dashboard.
Not started. Sign-in today is email and password with session cookies. The previous version of this site listed SAML as a Pro feature; that was never true.
If one of these 8 items is the reason you cannot use StatusOwl, email hello@statusowl.net and tell us which one. It is the clearest signal we get about what to build next.
A straight answer about where it sits and what is in front of it — or, if it is something we are not going to build, we will say that instead of leaving you waiting on it. Nobody wins from you choosing StatusOwl for a feature that never arrives.
Here is what we can: a branded status page on your own domain that opens its own incidents when checks start failing. Free forever on one page.