Multi-Status-Pages: Give Every Client Their Own Status Page

The problem with one status page per account

When SiteBrief launched its status page feature, every account got a single page. That works fine for indie developers and small teams — but agencies hit a wall immediately.

If you manage 15 client sites, you don't want all 15 on the same status page. Client A shouldn't see Client B's incidents. Client B shouldn't know Client A even exists. And you certainly don't want to explain to a client why their status page shows an outage for a completely unrelated business.

Agencies need one status page per client. That's what we've built.

What's new: unlimited status pages

You can now create as many status pages as you need — one per client, one per project, one per environment. Each page is completely isolated:

• Its own slug — sitebrief.net/status/client-name
• Its own components (which sites appear on the page)
• Its own incident feed — incidents on one page never bleed into another
• Its own subscriber list — only subscribers for that client get notified
• Its own brand color, title, and settings

How to set it up

Create a page per client

Go to Status Page in the sidebar. You'll see a list of all your status pages — initially empty. Click New status page, enter a slug and title, and you're done in under 30 seconds.

Add components

Expand a status page and go to the Components tab. Add the sites that belong to this client. Each component shows a name, current status, and links to the live uptime history from your monitoring data.

Send the URL to your client

Share sitebrief.net/status/their-slug with the client. They can bookmark it and check it any time — no login required. If you want privacy, set a password in the Settings tab.

Custom domains

On the Agency plan, you can map a custom subdomain to each status page. Point a CNAME to proxy.sitebrief.netand enter the domain in the page's Settings tab. SSL is automatic.

This means clients see status.clientdomain.com — not SiteBrief at all.

What about existing status pages?

If you had a status page set up before this update, it still works exactly as before. Your existing slug, components, and subscribers are unchanged. The new multi-page system is fully backwards compatible.