Status pages, uptime checks, alerts, on-call, errors and logs.

One monitor, one day

An API on an example page, from the minute its monitor is added to the same time the next day.

Eight kinds of check from six places

Two failed checks in a row make an outage, and one passed check ends it. A second location confirms every failure before it counts.

What a monitor can be

• HTTP: a website or an API

  method, headers, body, status, keyword

• TCP port

  open or not

• DNS

  a record, and the text it must hold

• Ping

  one echo to a host

• Certificate

  checked hourly, fails before it expires

• Domain expiry

  the registry's date, every 6 hours

• Heartbeat

  your cron job requests a URL

• Component

  set by hand, or follows a vendor's page

Where the checks run from

• Copenhagen, Falkenstein, Helsinki

  Europe

• Ashburn

  North America

• Singapore

  Asia

• Sydney

  Oceania

• London, Paris, San Jose, São Paulo, Toronto

  $4 a month each

• Johannesburg, Tokyo

  $8 a month each

• A fixed IP on an added place

  $4 a month

On Hobby and Pro the regions take turns every minute, and a page picks which ones count toward its response times. Free checks every 5 minutes, from Europe.

One alert per change: down, slow, back

Email on every plan. Hobby and Pro add these channels, set per page, with a delivery record for each one.

On-call, compatible with PagerDuty and Opsgenie

Anything that sends to PagerDuty's Events API, Opsgenie's Alert API or Sentry's webhooks sends to api.statoss.com instead, with a source's key.

Incidents, subscribers and your own domain

Everything on the status page besides the strips, and who gets to see it.

Errors from your apps, with any Sentry SDK

Change the DSN and events land in an app, grouped into issues, on every plan.

# Any Sentry SDK takes the DSN. So do @statoss/sdk and the Python statoss package.
import * as StatOSS from "@statoss/sdk";

StatOSS.init({
  dsn: "https://<key>@ingest.statoss.com/<app number>",
  environment: "production",
});

# Source maps and releases, from CI
export SENTRY_URL=https://statoss.com
export SENTRY_AUTH_TOKEN=<a StatOSS API key that writes>
export SENTRY_ORG=statoss
export SENTRY_PROJECT=<the app's slug>
sentry-cli sourcemaps upload ./dist

Logs, $5 a month with 15 GB

An add-on to Hobby and Pro, kept beside the errors of the same app. $0.25 a GB past 15. Lines kept 30 days count twice.

npx @statoss/cli logs tail 'level:>=warn service:api' --app web
npx @statoss/cli logs search '"timed out"' --since 1h --limit 50

• Lines come from @statoss/sdk, the Python package, Sentry's SDKs, OpenTelemetry, the Vercel, Fly, Cloudflare and Heroku drains, and plain JSON.
• One search box takes words, phrases, regular expressions, key:value, ranges and levels.
• Live tail, patterns with their counts, saved views, and log alerts through on-call.
• Kept 14 days, or 3, 7 or 30. A daily cap per team, 1 GiB unless you set another.

LogsSend logs

The API and MCP server do what the dashboard does

Pages, monitors, incidents, alert destinations, subscribers, the team and API keys. Keys read or write, and reach every page or one.

# An MCP client, with a key
claude mcp add statoss https://statoss.com/api/v1/mcp \
  --transport http \
  --header "Authorization: Bearer sk_..."

# The same key makes a page, and its first monitor, over REST
curl -X POST https://statoss.com/api/v1/pages \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{"name": "Northwind", "url": "https://northwind.example/health"}'

# A deploy marker, from CI
curl -X POST https://statoss.com/api/v1/pages/PAGE_ID/deploys \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{"version": "v2.14.1"}'

Set up with an agent

Paste this into Claude Code, Codex or Cursor, in the project's folder.

Set up StatOSS for this project.

1. Read https://statoss.com/auth.md and follow it: register as an anonymous agent, solve the proof of work, and exchange the assertion for a token.
2. Look through the project for what to watch: the public URLs it serves (the site, the API, health endpoints), the scheduled jobs that should check in, and whether it writes logs.
3. PUT a draft to https://statoss.com/api/v1/agent/draft: one status page named after the project, an http monitor for each URL, a heartbeat monitor with periodMinutes for each scheduled job, and one app for the project's errors with its platform. Ask me only what the project cannot tell you.
4. Ask me for my email address and start the claim with it. Give me the claim link and the 6-digit code in one message, and say that the code goes into the page, not back to you. Poll the claim grant at the interval it names until I have confirmed.
5. After the claim, for the app draft_result made: read its dsn with GET https://statoss.com/api/v1/apps/{appId}, install the SDK for the project's language as https://statoss.com/docs/send-errors describes, keep the DSN in the project's configuration rather than in its code, and send one test error. If the project writes logs, send them to the same app as https://statoss.com/docs/send-logs describes. For each heartbeat monitor it made, read its pingUrl with GET https://statoss.com/api/v1/pages/{pageId}/monitors/{monitorId} and add the ping to the job.
6. Tell me what you set up, with the dashboardUrl draft_result gives for each page and app, and what draft_result.leftOut says the plan left out.

Pricing

Free needs no card. Hobby and Pro bill monthly through Polar and can be cancelled from the billing page.

The open source core, on your own server

statoss-standalone is MIT licensed: the same kinds of check, the same strip and page, incidents, maintenance windows and alerts to the same ten places. No limit on pages or monitors.

curl -o config.yaml \
  https://raw.githubusercontent.com/kroqdotdev/statoss-standalone/main/config.example.yaml
# Edit config.yaml; the example explains every field.
docker run -d --name statoss --restart unless-stopped \
  -p 127.0.0.1:3000:3000 \
  -v "$PWD/config.yaml:/data/config.yaml:ro" \
  -v statoss-data:/data \
  ghcr.io/kroqdotdev/statoss-standalone:latest