pngr.dev docs
pngr is HTTP monitoring for teams that like their tools inspectable. Set up checks against any URL, alert through the channels you already use, and drive the whole thing from the web, a CLI, or an MCP-compatible agent.
These docs are short by design. Start with the quickstart, then read up on whichever concept you hit first.
start here
- quickstart — sign up, your first monitor, your first alert. About two minutes end to end.
concepts
The model, and why it's shaped the way it is.
- monitors — what a monitor is, its fields, and its lifecycle.
- check conditions — the five things a check can assert and how they compose.
- monitor states — up, degraded, down, paused, pending.
- incidents — how trouble is recorded from open to recovery.
- notification channels — where alerts go.
- rules & escalation — when and where to notify.
- status pages — a public, monitoring-native health page derived from your monitors.
guides & integrations
- set up notifications and alerting & escalation — task walkthroughs.
- stack as code — declare your whole fleet in one YAML file and reconcile it from CI.
- the pngr cli and mcp server — run everything from the terminal, or hand it to an agent.
- platform — orgs, roles, API tokens, plans & billing, and keyboard shortcuts.
tip
The OpenAPI reference is the source of truth for the public API's endpoint shapes. These docs explain the why; the API reference points you at the what.
Searching the docs: there's no search box yet — the surface is small enough that your browser's find (Cmd/Ctrl F) covers a page, and the sidebar covers the rest.