Skip to main content

​
Welcome to Kodo Status

Kodo is the developer-first status page platform. Unlike legacy tools that require clicking through dashboards, Kodo is built API-first with a powerful CLI, so you can manage incidents, monitors, and status pages the same way you manage code.

Quick Start

Deploy your first status page in 5 minutes

API Reference

Full REST API with 50+ endpoints

CLI Tool

Git-like workflow for incident management

Monitoring

Built-in uptime, SSL, and heartbeat monitoring

​
Why Kodo?

The Problem: Traditional status pages force you into clunky web UIs. Creating an incident means clicking through forms while your users are waiting.Kodo’s Solution: Create incidents from your terminal, CI/CD pipeline, or monitoring alerts. One command: kodo incidents create --title "API Degraded" --severity major.
The Problem: You’re paying for a status page AND uptime monitoring AND error tracking. Three tools, three dashboards, three bills.Kodo’s Solution: Uptime monitors, heartbeat tracking, SSL/domain monitoring, and client-side error tracking—all feeding into your status page automatically.
The Problem: When something breaks at 3 AM, you’re manually updating status pages, paging on-call, and copying error messages.Kodo’s Solution: Workflows automatically create incidents from monitor failures, notify the right team, and update your status page. You focus on fixing, not communicating.
The Problem: “Site is up” doesn’t mean “site is working.” Your uptime monitor says 100% while JavaScript errors frustrate users.Kodo’s Solution: The Beacon SDK captures frontend errors, performance issues, and user impact—then correlates them with your status page.

​
Key Features

FeatureWhat It Does
Status PagesBeautiful, customizable pages with your branding, custom domains, and real-time updates
Uptime MonitoringHTTP checks from multiple regions with automatic incident creation
Heartbeat MonitoringTrack cron jobs and background tasks—know instantly when they fail
SSL & Domain MonitoringNever let a certificate expire or lose a domain again
Incident ManagementFull lifecycle from creation to postmortem with subscriber notifications
Error TrackingCapture frontend JavaScript errors with stack traces and user context
WorkflowsAutomate incident response with trigger-based actions
On-Call SchedulingRotation schedules with escalation policies
Multi-channel NotificationsSlack, Discord, PagerDuty, email, SMS, webhooks

​
Quick Examples

​
Create an incident from CLI

kodo incidents create \
  --title "Payment processing delayed" \
  --severity major \
  --service payments \
  --message "Investigating increased latency in payment processing"

​
Auto-create incidents from monitoring

// Your uptime monitor fails → Workflow triggers → Incident created
{
  "trigger": "uptime.down",
  "actions": [
    { "type": "create_incident", "title": "{{monitor.name}} is down" },
    { "type": "notify", "channel": "pagerduty" }
  ]
}

​
Track frontend errors

import { Beacon } from '@kodo/beacon';

Beacon.init({
  apiKey: 'your_beacon_key',
  service: 'web-app'
});

// Errors automatically captured and sent to Kodo

​
Base URL

All API requests should be made to: 
https://kodostatus.com/api/v1

​
Authentication

Authenticate using the X-API-Key header: 
curl "https://kodostatus.com/api/v1/incidents" \
  -H "X-API-Key: your_api_key_here"
Get your API key from the Dashboard.

​
What’s Next?

Quick Start

Set up in 5 minutes

Status Management

Learn incident workflows

Monitoring

Configure monitors