Skip to main content

The status page that can’t lie.

Most status pages go green when your servers respond. Kōdo watches the work actually finish — webhooks draining, jobs clearing, sagas completing — plus uptime, incidents, and on-call in one platform.

We run Kōdo on Kōdo — see our live status page

kodo apply · main
v1.4
$ kodo apply
observability3 services
synced
monitors6 endpoints
synced
status pages2 public
synced
incidents4 policies
synced
alerts8 channels
synced
✓ reliability applied in 1.24s
The status page that can’t lie

External monitors prove the edge is up. Kōdo proves the work finished.

A green ping only means your server answered. It says nothing about whether the checkout saga finished, the webhook queue drained, the nightly job cleared, or the cron actually ran. Wrap any process in kodo.workflow() and every run reports completion rate, p95, and exactly which step failed — with paging when a run gets stuck.

  • sagas completing
  • webhooks draining
  • jobs clearing
  • crons running
fulfillment.ts
kodo-sdk
import { Kodo } from "kodo-sdk";
const kodo = new Kodo({ apiKey: process.env.KODO_API_KEY! });

await kodo.workflow("checkout-fulfillment", async (wf) => {
  await wf.step("charge_card",       () => stripe.charge(order));
  await wf.step("reserve_inventory", () => inventory.reserve(order));
  await wf.step("notify_warehouse",  () => warehouse.notify(order));
});
Stuck runsexample · 3 not completing
checkout-fulfillmentrunning 18m
Uptime & synthetic checks
Errors, logs & traces
Process Health completion
Incidents & status pages
On-call & escalations
Slack, webhooks & API
The platform

Six tools your team needs. One surface.

Status pages

Public, password-gated, or SSO. Custom domains, six themes, surgical CSS. Every audience a different page.

status.kodostatus.com
API99.9%
Dashboard99.9%
Webhooks99.9%

Uptime monitoring

HTTP, heartbeat, SSL, and domain-expiry monitoring. Auto-open incidents after confirmed failures.

Heartbeat · us-east
42ms200 OK

Incidents

Templates, components, post-mortems. Updates fan out to every channel. Your timeline, written for you.

Investigating · 2m ago
Database read latency
→ posted to #incidents
→ status page updated
→ on-call paged

Alerting

Email, Slack, SMS, webhooks, Discord, PagerDuty. Smart dedup so a single outage doesn't fire fifty times.

Channels
emailsent
slackdelivered
smsdelivered
webhook200

On-call

Rotations, overrides, escalation policies. The person who's actually awake gets paged first.

Rotation · week 17
M T W T F S S· primary: you

Error tracking

Source-mapped stack traces. Linked to incidents automatically. Fewer tabs, more fixing.

Trace · checkout
TypeError: undefined is not
at checkout.ts:142:8
at handler.ts:88:3
occurrences17 · last 5m
How it works

How it works

Get up and running in under 2 minutes. Connect via dashboard, API, or CLI — we handle the rest.

01

Add your services

Register your endpoints via the dashboard, API, or CLI. Configure check intervals and alert thresholds.

zsh
$ kodo monitors create -n API -t http -u https://api.kodostatus.com/health
checking endpoint…
200 OK · 42ms · us-east
✓ 1-minute monitoring enabled
02

We monitor everything

Automatic HTTP and heartbeat checks, plus SSL and domain-expiry monitoring.

check · 60s intervalhealthy
12:04:00200 · 42ms
12:03:00200 · 48ms
12:02:00200 · 44ms
12:01:00200 · 51ms
12:00:00200 · 46ms
11:59:00200 · 43ms
03

Your team stays informed

Email, Slack, SMS, and webhook alerts the moment something changes. Auto-generated incident updates keep everyone in the loop.

incident · db-primary
email → team@kodostatus.comsent
slack → #incidentsdelivered
sms → on-calldelivered
page → status.kodostatus.comlive
Reliability, as code.

Production-grade, by default.

CLI-first config, SSO, audit logs, custom domains, sub-second metrics — the table stakes, done properly.

CLI & API-first

Everything configurable in code. GitOps-friendly.

Webhooks that make sense

Signed payloads, automatic retries, replay.

OIDC SSO & SCIM

Google, Microsoft, Okta, and custom OIDC providers. SCIM provisioning included.

Custom domains

Bring your own. Automatic TLS. CNAME or ALIAS.

Live operational data

Current checks, incidents, and process runs in one dashboard.

SOC2 in progress

Audit logs and configurable retention controls are available today.

Full change history

Every incident edit, versioned and attributable.

Role-based access

Fine-grained permissions down to each page.

Your status page, elevated

Served from 300+ Cloudflare edge locations. Custom-branded, lightning fast, and available even when your primary infrastructure isn't.

All Systems Operational
Last 90 days
API Gateway
99.99%
Authentication
99.98%
Database
99.95%
CDN
100%
Webhooks
99.91%
Webhook Delivery Delays

We are investigating delays in webhook delivery. Some events may be delayed by up to 30 seconds.

Updated 3 min ago
Pricing

Simple, honest pricing

No per-seat pricing. No surprise overages. Just straightforward plans.

Starter

For your first status page

$0
  • 1 status page
  • 3 services
  • 3 uptime monitors
  • Email notifications
  • 7-day history
Most popular

Pro

For teams shipping fast

$19/mo
  • 2 status pages
  • 20 uptime monitors
  • Unlimited services
  • Custom domain
  • 90-day history
  • Slack & webhooks

Team

For engineering teams on call

$49/mo
  • Everything in Pro
  • Unlimited uptime monitors
  • 365-day history
  • On-call scheduling
  • Escalation policies
  • Priority support

Enterprise

For organizations with identity and compliance requirements

Custom
  • Everything in Team
  • OIDC SSO
  • SCIM provisioning
  • Role-based access
  • Audit-ready access logs
  • Dedicated support
Free 14-day trial · no card

Ship with reliability built in.

Free forever on Starter. No credit card required.