Documentation
Beacon Pulse
Beacon Pulse watches the things your customers depend on — websites, APIs, TLS certificates, DNS, TCP services and scheduled jobs — and tells you when one of them stops working, before they do.
Quickstart
Sign up and watch your first domain. About five minutes.
Authentication
Create an API key and make your first authenticated call.
CI & automation
Keep your monitors in a file in your repo and apply them on push.
API reference
Every endpoint, with the fields and a curl for each.
API console
Paste a key and call the live API from your browser.
How it works
You tell Beacon what to watch. It probes each target on a schedule from its own infrastructure — not from your servers, which is the point: a check that runs inside the thing it is checking goes quiet at exactly the moment it matters.
When a probe fails often enough to mean something, Beacon raises an alert and sends it wherever you asked — Telegram, Slack, email, or your own webhook. If you publish a status page, your customers see the same truth without having to ask.
The four things to know
- Monitor
- One thing being watched, of one type —
https,tcp,dns,heartbeatand so on. - Project
- A group of monitors. Most teams use one per environment or per product.
- Notification channel
- Where alerts go. Add as many as you like.
- Status page
- A public page showing only the monitors you explicitly publish.
Everything in the dashboard is available over the API, using the same permissions. There is no second-class API surface, because the dashboard uses it too.