For SaaS providers · resellers · indie founders

Status pages.Multi-tenant, your region.

Self-hostable status-page platform instead of Atlassian Statuspage / Instatus / Better Stack. Many pages per instance, subdomain per customer, custom branding from tier 1, realtime without reload. Hosting in your chosen region, no per-page pricing. Live system: [publicstatus.eu](https://publicstatus.eu).

status.acme-cloud.de

Acme Cloud GmbH

All systems

Degraded
API · Region DE
Operational
Web app
Operational
Auth service
Degraded
File upload
Operational
Database
Operational
Increased login latency12 min ago

Authentication is currently responding more slowly. We are investigating the cause. Update to follow.

Sound familiar?

Today, in every second SaaS team.

Your status page is the trust signal to your customers. But it lives either in a US-cloud service with GDPR / data-residency risk, or in a PHP side project from 2018. Four typical symptoms:

What it looks like with PublicStatus.

Same pain, told the other way around.

„Atlassian Statuspage $99/mo per page, US-cloud."

One platform, any number of pages. One instance for all pages. No per-page pricing.

„PHP self-build from 2018, nobody touches it."

TypeScript, fully typed, audit-trail in the framework, multi-tenant by default. Generated code lives in your repo.

„Reseller subdomain with branding? Not out of the box."

Subdomain per customer (customer.yourstatus.io), custom domain with automatic TLS through Let's Encrypt. Branding (logo, colors) configurable per tenant.

„Manual status update at 08:30, the outage was at 03:00."

Webhook endpoint per component. Monitoring (Grafana, Prometheus, UptimeRobot) calls in, status flips automatically, subscribers get pushed.

„Realtime via polling, browser eats bandwidth."

Server-sent events. Status changes in <1s on every open browser, no reload, no external Pusher/Ably.

status.acme-cloud.de

Acme Cloud GmbH

All systems

Degraded
API · Region DE
Operational
Web app
Operational
Auth service
Degraded
File upload
Operational
Database
Operational
Increased login latency12 min ago

Authentication is currently responding more slowly. We are investigating the cause. Update to follow.

How you get there.

From first call to running status page.

Three options: managed service, self-host, or pilot. Self-host is doable today because PublicStatus runs open-source. Pilot program open to reseller customers.

1 / 3

Self-host: start today.

PublicStatus runs on Kumiko. Production runs as one container image and one Kubernetes deployment. Self-host costs only hosting, no license markup.

2 / 3

Pilot program: we build, you use.

If you don't want to self-host: pilot program for reseller customers. 3 months free (setup + hosting) in exchange for case-study rights. Just ask whether a place is currently open. Regular customers afterward with fixed price per subdomain.

3 / 3

Reseller model: your customers, your brand.

If you resell status pages to your own customers (e.g. as a cloud provider with status-page upsell): reseller tier with markup pricing, your customers see only your domain. Pricing scales with volume.

Self-host is always an option, no vendor lock-in. Open-source code, your servers, your data. Service tier is optional for SaaS teams without DevOps capacity.

Tech-Substanz für IT-Leitung

Wie das technisch funktioniert

Status page as a service, or self-hosted?

Live system at [publicstatus.eu](https://publicstatus.eu), with real tenants, realtime and tenant isolation in production. Pilot program open, self-host path always available.