Statup

EN Français

GitHub
Statup

Everyone in the company knows what is going on.

The Wi-Fi is down on the second floor. Payroll was updated this morning. The VPN goes off on Saturday night. IT writes it once, on one page, and nobody has to ask.

View the source AGPL-3.0

Self-hosted, open source, pre-v1.

The Statup dashboard: an open incident on the API, an upcoming maintenance, six services with thirty days of history, and a chronological activity list.
A running instance on demo data. Flip the theme above to see it in dark.

One Tuesday, hour by hour

A scenario, not a customer: Statup has not run in production yet. Every entry below is something the product does today.

The time of day in the scenario: 08:52

Five entries, one form each. Written once by IT, read by everyone.

  1. Is the Wi-Fi down, or is it just me?

    Asked 23 times in the support channel before nine.

    Incident Major · Wi-Fi

    Wi-Fi unavailable on floors 2 and 3

    Access points are rebooting. Wired desks are not affected. Next update at 09:30.

  2. Any news?

    Asked by everyone who missed the first answer.

    Update Monitoring · Wi-Fi

    Access points are back

    Watching for an hour before closing. If it drops again, it will say so here first.

  3. Why does the accounting software look different today?

    Asked by the whole finance team.

    Changelog Sage · Finance

    Sage updated to version 2026.3

    The invoice export moved to the Documents menu. Nothing else changes for you.

  4. Will the VPN work this weekend?

    Asked by the people on call.

    Maintenance Scheduled · VPN

    VPN gateway replacement

    Saturday from 22:00 to 02:00. The page counts down to it and says when it is done.

  5. When did we last touch the mail server?

    Asked by the new hire in IT.

    Search 1 result · Mail

    Mail server moved to the new cluster

    A changelog from 14 August, found by typing one word. Thirty days of history sit under every service.

Two readers, one page

Built for the person who is not an engineer, and for the team that has to keep it true.

For everyone in the company

For the IT team that runs it

Opens the link from the support channel on a phone and reads the outage at arm’s length. Every state carries a word, never a colour alone.

Incident

Declares it in one form: kind, severity, services, one sentence. Templates for the ones that come back.

Sees the latest word first, with the time it was posted, and thirty days of history under every service.

Updates

Posts an update as the situation moves. The timeline keeps every one, in Markdown if you like.

Knows on Tuesday that the VPN goes off on Saturday night, with a countdown to it.

Maintenance

Schedules it, or declares an urgent one, and the page counts down and says when it is done.

Learns what changed in the accounting software, in plain words, before having to ask.

Changelog

Publishes what changed after an update, in three lines, from the same form.

Finds any past incident, update or changelog by typing one word.

Search

Answers “when did we last touch the mail server?” with a link instead of a memory.

Reads without an account in public mode, or signs in as a member. Follows the Atom feed from a reader, Slack or Teams.

Access

Reader, Publisher and Admin roles. One binary on your own server, one SQLite file, nothing sent anywhere.

The Statup status page on a phone: a red incident banner filling the top of the screen, the affected service and how long ago it started. A Statup incident page: severity and lifecycle, a plain-language description, and three timestamped updates from the team.
An incident as IT updates it, and as everyone else reads it.
  • 1 binary to run
  • 1 file to back up
  • 0 services beside it
  • 0 calls to anyone else

What it does not do yet

Better here than after you deploy.

  • No email, no webhook

    Updates reach people through the page and its Atom feed. Email and webhooks are the largest gap before v1.

  • Unproven in production

    Never a full week on real infrastructure, under real incidents.

  • Self-hosting only

    No hosted version. statup.dev serves this page and nothing else.

  • The schema still moves

    Expect migrations and reworks before the first stable release.

Running it

Docker, or build from source.

Runtime
One binary. Docker and compose files included.
Storage
Embedded SQLite, one file. No database server.
Config
One .env. Only the session secret is required.
Languages
English and French, chosen per visitor.
Licence
AGPL-3.0.

Read the README

Questions

Is it free?
Yes, under the AGPL-3.0. Redistribute a modified version, or offer it over a network, and the same licence applies to your changes.
Does it need a database server?
No. SQLite is embedded in the binary and writes to a single file.
Does it send anything to statup.dev?
No. No telemetry, no update check, no third-party request at runtime.
Is this the older Statup?
No. An unrelated status page called Statup, written in Go, has been unmaintained for years. This one is a different codebase, in Rust, started in 2026.

One repository away.

Nothing to sign up for, nothing to pay. Clone it and judge for yourself.

Open the repository