YASP

What YASP is

YASP is a self-hosted status page for publishing service information, managing incidents, and notifying subscribers. Teams can add incident timeline updates, plan and announce maintenance windows, and organize services into logical groups. Public pages support dark and light themes with customizable colors and branding, as well as custom domains. A Payload CMS dashboard manages services, incidents, and notification settings. Subscriber notices can be sent by email through SMTP or by SMS through Twilio, and the project provides an API reference. YASP is available on the web and as an API, with self-hosting options. Its documentation recommends deploying a Helm chart on Kubernetes and also covers Docker Compose for a single host; the project publishes an amd64/arm64 container image to GHCR. The software is open source under the MIT License, and its Free Forever plan costs nothing. The demo resets every hour by deleting and reseeding application data, so YASP says to use it only with a dedicated or disposable database.

Who it suits

YASP suits teams that want to host their own status page and manage incidents, maintenance notices, and subscriber alerts. It may fit teams deploying on Kubernetes or using Docker Compose on a single host.

Limits

The Free Forever plan costs nothing and is self-hosted. The demo automatically resets every hour, deleting and reseeding application data, so it should use a dedicated or disposable database.

Getting started

1. Open the YASP website or documentation
2. Choose a self-hosted deployment route
3. Deploy the Helm chart on Kubernetes or use Docker Compose on one host
4. Configure services, incidents, and notifications in Payload CMS
5. Connect SMTP or Twilio for subscriber alerts
6. Use a custom domain for the status page if needed

Verdict

YASP brings incident updates, maintenance scheduling, and subscriber notifications into a self-hosted status page. Its hourly-resetting demo requires care with the database used.