Free status page self hosted

Run the MIT-licensed Logdash Next.js starter on your own server or in Docker for a free self-hosted status page, while the checks behind it stay on the Logdash free plan, because the monitoring itself does not self-host in one command yet.

A status page has two halves. The page is HTML that tells visitors what is up. The checks are what make that HTML true: something outside your stack hitting your endpoints every few minutes and remembering the answers. Self-hosting the page is cheap and boring. Self-hosting the checks means running a monitor that has to survive the outage it is supposed to report.

With Logdash you self-host the page and leave the checks hosted. The free plan covers 5 services with an HTTP check every 5 minutes, 1 published status page and Telegram alerts. The page reads that status page from a public JSON API with no key, so it runs on any box you own. A custom domain on the hosted page needs Pro. A self-hosted page on status.yourdomain.com does not, because the domain points at your server, not ours.

Status page self hosted with Docker

The starter is a small Next.js 16 app: one page, one component, Tailwind. Create it without installing, so the container installs its own Linux binaries.

npx create-next-app@latest status-page \
  --example https://github.com/logdash-io/logdash.io \
  --example-path templates/status-page-next \
  --skip-install
cd status-page
compose.yaml 
services:
  status-page:
    image: node:22-alpine
    working_dir: /app
    volumes:
      - ./:/app
    environment:
      LOGDASH_STATUS_PAGE_ID: your-status-page-id
    command: sh -c "npm install && npm run build && npm start"
    ports:
      - "3000:3000"
    restart: unless-stopped

Run docker compose up -d and open port 3000. The build fetches your status page once, so a wrong id fails with a 404 and an unpublished page with a 403, instead of shipping a blank page. After that, Next.js renders the page again at most every 60 seconds and the browser polls every 60 seconds. If the Logdash API cannot be reached, the page keeps the last data it had.

Host it apart from your app. People open a status page when your app is down, and a page that shares a server, a deploy or a DNS setup with the app goes down with it. A small VPS at a different provider, or its own Vercel project, is enough.

Can the checks be self-hosted too?

The starter, the shadcn component and the @logdash/status client are MIT. Fork them, restyle them, delete what you do not need. The Logdash server that runs the checks is AGPL-3.0 and public, but production self-hosting is not supported today. The backend does not boot without Stripe and Resend keys, login is GitHub or Google OAuth only, and there is no published image or compose file that runs the apps. It runs locally for development. The full list of blockers is at /docs/self-hosting.

  1. Publish a status page Create a service per app in Logdash, point each HTTP monitor at a health URL, add the monitors to a status page and publish it. Copy the id from the Build your own section.
  2. Start the container Paste the id into compose.yaml, run docker compose up -d on a host that shares nothing with your app, and point status.yourdomain.com at port 3000 through your reverse proxy.
  3. Break it once Stop your app. Within one 5-minute check the monitor flips to down, and your self-hosted page shows it within about 3 minutes of that. The Telegram alert does not wait: it arrives at the flip, with the monitor name and status code.

Logdash starter vs Uptime Kuma

FeatureLogdashUptime Kuma
Checks self-hosted tooNo, checks run on LogdashYes, one container
Checks survive your server dyingYes, they run elsewhereNo, they die with the host
Monitor typesHTTP checks, push heartbeats on ProHTTP, TCP, ping, DNS, keyword and more
Incident notes and maintenanceNot built inPinned incident banner and maintenance windows
Page designYour own React code with your Tailwind themeBuilt-in layout plus custom CSS
CostFree plan plus the boxFree plus the box

When Uptime Kuma is the better pick

  • Every byte, check history included, has to stay on your hardware.
  • You need TCP, DNS, ping or keyword checks. Logdash has none of them.
  • You want to post incident notes and schedule maintenance on the page itself.
Can I get a free status page self hosted?
Yes. The starter is MIT and costs nothing to run beyond the server. The data comes from a Logdash status page, and the free plan includes one with 5 services checked every 5 minutes.
What is the best self hosted status page?
If everything, checks included, must run on your hardware, Uptime Kuma: one container, many monitor types. If you want the page on your server and the checks somewhere that survives your server, the Logdash starter.
How do I run a status page self hosted in Docker?
Create the starter with create-next-app and --skip-install, then run the compose.yaml above with node:22-alpine and your status page id. It builds once, then serves on port 3000.

Point it at your own URL and watch it for real.