About · Edition 03
A tool for saying what's true
when something is broken.
StatusLayer is built by the same small team as SupportLayer — because the moment an outage starts, the line between "support" and "operations" becomes very thin. Both tools share a design language, an authentication system, and a single conviction: clarity beats theatre.
What we believe
Four
principles.
The opinions we refuse to compromise on.
-
01
A status page is writing, not dashboarding.
When production is on fire, the last thing anyone needs is a drag-and-drop interface. StatusLayer is optimised for the keyboard, for Markdown, and for the thirty seconds between noticing and publishing.
-
02
Communication is a commitment, not a feature.
Every published update is permalinked, auditable, and never silently edited. Readers can cite your page three years later and the URL still works. We think this is the minimum bar for a "status" product.
-
03
Your domain. Your brand. Your data.
You can run StatusLayer on your own domain from day one. You can export every subscriber, incident, and update as a CSV any time. Leaving is as easy as arriving.
-
04
Boring technology, honestly priced.
PHP and MySQL under the hood. One tier, one region, and a price you can understand. No growth-hack tier-gating on basic features — if something is useful to one customer, it is useful to all of them.
The story
How StatusLayer came about.
We built SupportLayer first — a customer-support helpdesk designed around the same conviction: do the fundamentals perfectly, then stop. Customers loved it, but there was a moment we kept seeing over and over.
A customer would file a support ticket at 14:02. By 14:04, three more tickets would arrive about the same issue. By 14:10 our customers — in turn — would be flooded with identical emails from their customers, and the support team would be manually copy-pasting the same explanation into every reply.
The right tool for that moment is not a helpdesk. It is a single URL that every affected user can bookmark, that updates in public, and that takes less effort to publish than a Slack message. So we built one.
StatusLayer is intentionally the sibling of SupportLayer, not a bundled "enterprise feature". Both products work on their own. When you use both, they share a login, a design language, and a habit of keeping the boring parts boring.
Who builds this
A small team in the UK.
StatusLayer is a product of xegen.co.uk — a three-person studio building long-lived software for operators. We ship quietly, answer email ourselves, and do not raise venture capital.
Jay
Founder / Engineering
Writes the code, signs the invoices, answers the email. Former platform engineer at a large UK retailer.
Remi
Design & Craft
Shapes the interface, the brand, and the defaults. Thinks in margins and keyboard shortcuts.
Iyo
Operations & Customers
Runs onboarding, support, and the parts of the business that are not a Twig template. Replies within a working day.
Talk to us
The quickest way to reach a real person.
Email goes straight to the founders. We reply in under a working day — usually sooner. For press and partnerships, prefix the subject with [PRESS].