Documentation

Guides

Twelve pages, one screen each. Read them in order if you have just signed up; go straight to the one you need if something is already awake at four in the morning.

Start here

• Getting startedAn account, a server reporting, a site watched from outside, and somewhere for the alert to land.
• Installing the agentOne command on the server. No listening port, no root, and it reports within a minute.
• Watching a websiteA URL loaded from outside, on a schedule, so you hear it from us and not from a customer.
• A job that reports inA backup, an export, a cron: it calls us when it finishes, and we alert when it stops calling.
• Real usersOne tag in your pages, and how fast the site really feels to the people visiting it.

Alerts people still answer

• A rule, and its waitWhat counts as wrong, and how long it has to stay wrong before anybody is told.
• Where alerts goChannels, policies, and the preview that shows who would be told before anything is sent.
• SilencesStop the notifications for planned work, including the work that comes back every Tuesday.

When somebody has to be woken

• On-callWho gets woken, in what order, what happens when nobody answers, and how to hand over one night.
• The status pagePublish a monitor on a page anyone can read, and know exactly what leaves with it.

Without the portal

• API documentationEverything the portal does, the API does. Here is how to call it, without signing in first.
• AI and MCP documentationWhat Mango AI does inside the product, and how to connect your own assistant to the same operations.

The portal is optional

Everything on these pages happens in the portal, and none of it needs the portal: the same operations are in the API and in MCP.

If a guide leaves you stuck, the gap is ours and not yours: write to us and we will fix the page.