stativa

Features

Everything a status page needs, nothing it doesn't.

Monitoring, a public page, incidents, maintenance and subscribers in one place. Here is what each part does, in detail.

Monitoring

Checks that know what “up” means for you

stativa runs the checks itself and moves each service between operational, degraded and down on its own.

  • ✓HTTP checks with the method, accepted status codes, expected text in the body and basic auth you choose
  • ✓TCP checks for databases, brokers and anything else that listens on a port
  • ✓Check interval, request timeout and retries per service, so one slow answer doesn't page anyone
  • ✓TLS certificate expiry shown next to the service before it becomes an outage
  • ✓Heartbeats for cron jobs: a fixed period or a cron expression in your timezone, a grace window, /start and /fail pings, and a maximum run time
  • ✓Metric push: send a number and set the degraded and outage thresholds, in either direction, plus how long silence may last
  • ✓Failures inside a maintenance window are marked as planned work, not outages

Status pages

Pages your users can actually read

One workspace can run several pages — one per product, region or customer — each with its own services, look and address.

  • ✓Groups and sub-components, ordered by drag and drop
  • ✓90-day uptime ribbons and a history calendar of past incidents and maintenance
  • ✓A permanent link for every incident, with its full timeline
  • ✓Your own domain: add a CNAME, verify it, and the certificate is issued automatically
  • ✓Your logo and accent colour, light and dark themes
  • ✓English, Turkish and German pages; visitors can switch with ?lang
  • ✓RSS feed and an SVG status badge for every page
  • ✓Public responses are signed, so tools that read them can verify the source

Incidents & maintenance

Say what's happening, fast

Opening an incident at 3am should take seconds, not a form marathon.

  • ✓Open, update and resolve incidents from the ⌘K command bar
  • ✓Templates: save an incident as a template and start the next one with title, severity, message and services filled in
  • ✓Prometheus Alertmanager and Grafana alerts open incidents on the services you name and close them when they resolve
  • ✓Scheduled maintenance that starts and ends on time and sets its services to maintenance and back
  • ✓Maintenance windows and deploy markers from your CI pipeline over the API
  • ✓A preview of the page as you write, before anything goes public

Subscribers

Tell people before they ask

Visitors subscribe on the status page and hear about incidents and maintenance on the channel they pick.

  • ✓Email updates in the page's language
  • ✓Slack: subscribers add an incoming-webhook URL and updates post to that channel
  • ✓Webhooks: a JSON POST for every update, signed so the receiver can check it
  • ✓One-click unsubscribe in every message

Team & security

Room for the whole team, with guard rails

Give people the access their job needs and see who changed what.

  • ✓Owner, admin, editor and viewer roles
  • ✓Per-page access: limit someone to the pages they look after
  • ✓Two-factor sign-in
  • ✓An audit log of every change, filterable and linkable
  • ✓API keys with scopes — read, maintenance, incidents, services — optionally bound to one page
  • ✓Error-budget alerts to owners and admins when a service's SLO burns fast or runs out

Integrations

Works with what you already run

Signals in

What tells stativa something is wrong.

  • Prometheus AlertmanagerFiring alerts open incidents, resolved ones close them
  • Grafana AlertingWebhook contact point, same open and close
  • HeartbeatsCron jobs ping in; silence marks them down
  • Metric pushSend a number, set the thresholds

Notifications out

How subscribers hear about it.

  • EmailIn the page's language, one-click unsubscribe
  • SlackPosts to a channel's incoming webhook
  • WebhooksSigned JSON on every update

Automation & embeds

Wire it into your pipeline and your docs.

  • CI/CD pipelinesMaintenance windows and deploy markers with curl
  • REST APIScoped keys for services, pages and incidents
  • RSS feedEvery page, for readers and chat bots
  • Status badgeLive status in READMEs and dashboards

See it on your own services.

Create a workspace, add a check and your page is live. Free during early access.