Skip to content

Northplane

Monitoring and alarming in one static binary — from the first ping to the phone call that wakes someone up.

Install in five minutes

One binary, one container, or a Compose stack with automatic TLS. Open /setup, create the admin, add a host. Quickstart →

Monitor anything

17 built-in checks, Nagios plugins, SNMP polling and traps, the np-agent, heartbeats, discovery, business services and SLAs, dashboards and reports. Monitoring →

Alarm everyone

Phone, SMS, MQTT, ESPA, e-mail and webhooks in — voice calls with IVR, SMS, push, ntfy, Slack, Teams and tickets out. On-call schedules, escalation chains, durable retries, full audit. Alarming →

API-first, AI-ready

Every capability is a REST endpoint with RBAC and tenants; the UI, the np CLI, the AI agent chat and the MCP server all use it. API reference →

Server northplaned — one static Go binary with the React UI, this manual, Swagger UI and the MCP server embedded
Storage SQLite (default, zero-ops) or PostgreSQL; NP-TSDB for metrics; durable outbox; tamper-evident audit chain
Inputs built-in checks, Nagios plugins, np-agent, SNMP v1/v2c/v3 polling and traps, heartbeats, webhooks, Alertmanager, IMAP, MQTT, ESPA 4.4.4 / ESPA-X, phone (Twilio or Asterisk), SMS
Outputs voice with IVR acknowledgement, SMS, e-mail, mobile push (FCM/APNs), Web Push, ntfy, Slack, Teams, webhooks, MQTT, ServiceNow / Jira / Zendesk tickets
Control plane REST API with RBAC, tenants, sites (federation), API tokens, OIDC / LDAP, YAML config bundles, np CLI
AI agent chat over 10 LLM provider types with policy gates and approvals; MCP server for Claude, Cursor, VS Code and friends
Runs as binary + systemd, Docker (distroless), Docker Compose with Caddy TLS, or behind your own reverse proxy

These pages are shipped inside every Northplane binary at /docs/ and mirror the version they came with. The public showcase instance is doktrace.com (its docs: doktrace.com/docs). Machine-readable copies for AI assistants: llms.txt, llms-full.txt.