stativa
Early access · free

Status pages that ship in minutes.

stativa turns your monitoring signals into a public status page your users actually trust. Beautiful by default. Customisable when it matters.

Free during early access · We won’t ask for your card · HTTP, TCP, heartbeat and metric checks

status.acmecloud.io
✓
All systems operational
Last checked 14:32 UTC · next check in 6s
90-day uptime
99.987%
  • Public REST API
    Operational
  • GraphQL gateway
    Operational
  • Edge network
    Operational
  • Dashboard
    Operational
  • Database
    Operational

Everything you need

Built for the way
incidents actually happen.

Monitoring built in

HTTP, TCP, heartbeat and metric checks run from stativa itself. Services update their own status — you don't babysit them.

Alerts open incidents

Point Prometheus Alertmanager or Grafana alerts at stativa. A firing alert opens an incident; a resolved one closes it.

Subscribers on their channel

Email, Slack and webhook. Subscribers pick the channel that suits them and can leave with one click.

Your domain, HTTPS included

Add a CNAME, verify it, and the certificate is issued automatically. Your logo and colours on top.

Incidents in a few keystrokes

Open, update and resolve from the ⌘K command bar. Templates save you from typing the same words at 3am.

Maintenance that runs itself

Windows start and end on schedule, or straight from your deploy pipeline. Checks inside a window don't page anyone.

Speaks your users' language

Status pages, notifications and the RSS feed in English, Turkish and German.

Feeds, badges, signatures

RSS feed and an SVG badge for every page. Public responses are signed, so tools can verify where they came from.

Teams without the worry

Owner, admin, editor and viewer roles, per-page access, two-factor sign-in and an audit log of every change.

All features in detail →

Integrations

Plugs into what you already run.

11 integrations, all included. No plugins to install, no marketplace.

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

How to wire them up →

From developers, to developers

Everything you click,
you can script.

We run our own products in production and built stativa as the status page we wanted: no sales call, no per-seat maths, and an API for every routine job.

  • ✓A cron job pings a URL; a missed ping marks the service down
  • ✓Your pipeline opens a maintenance window and closes it after the deploy
  • ✓Alertmanager and Grafana open and resolve incidents for you
  • ✓Scoped API keys, per page and per job
API and examples →
# cron: tell stativa the backup ran
curl -fsS https://app.stativa.io/api/v1/heartbeat/$TOKEN

# CI: maintenance around a deploy
curl -X POST https://app.stativa.io/api/v1/maintenance \
  -H "Authorization: Bearer $STATIVA_KEY" \
  -d '{"services":["api"],"minutes":15,"announce":true}'

Early access

Free while we’re in early access.

Every feature included, no trial clock. Your credit card is none of our business — keep it in your wallet.

  • ✓Status pages on your subdomain or your own domain
  • ✓HTTP, TCP, heartbeat and metric monitoring
  • ✓Email, Slack and webhook notifications
  • ✓Incidents, templates and scheduled maintenance
  • ✓Team roles and audit log
  • ✓REST API and webhooks
Start free