Knowledge Base
Browse the documentation or search across every published article.
Documentation
Public guides and reference docs
Alerting rules reference
Alert rules decide when a failing check becomes a paged human. Conditions - Failure threshold — consecutive failed checks before an incident opens (default 2; set 1 for critical paths, 3+ for flaky
Updated Jun 28, 2026
Webhook payload format
Beacon delivers incident events as JSON POSTs with an HMAC signature. json { "event": "incident.opened", "incident": { "id": "inc_8f2c1a", "status": "open", "severity": "major", "
Updated Jun 17, 2026
REST API authentication
The Beacon API uses bearer tokens scoped to a workspace. Creating a token Settings → API tokens → New token. Tokens are shown once at creation — store them in your secrets manager, not your repo.
Updated Jun 15, 2026
FAQs
Frequently asked questions
Can I export my monitoring data?
Yes — your data is yours. - CSV export of check results and incident history from the dashboard (up to 90 days) - REST API access to raw check results, incidents, and uptime rollups (see REST API aut
Updated Jul 2, 2026
What counts as a monitor?
One monitor = one thing being checked on a schedule. Each of these counts as a single monitor: - An HTTP(S) endpoint check - A TCP port check - An SSL certificate expiry check - A cron/heartbeat chec
Updated Jun 25, 2026
How does alert deduplication work?
Beacon groups related failures into a single incident instead of paging you once per check. - Consecutive failures of the same monitor extend the open incident — they never create a new one - Failure
Updated Jun 22, 2026
Getting Started
How to begin using the product
Add your first status page
A status page turns "is it down for everyone?" support tickets into self-service answers. 1. Go to Status Pages → New page 2. Pick the monitors to display — group them into components your customers
Updated Jun 20, 2026
Complete onboarding guide for new customers
Complete onboarding guide for new customers Welcome to Beacon. This guide walks a brand-new workspace all the way to a monitored service with sane alerting, a public status page, and a team that kno
Updated Jun 14, 2026
Getting started with Beacon
Beacon monitors your services and pages the right person when something breaks. Setup takes about ten minutes. 1. Create your first monitor Add an HTTP monitor for your main app URL (Monitors → New
Updated Jun 5, 2026
Products & Services
What we offer and how it works
Beacon plans and pricing
| Plan | Price | Monitors | Best for | |---|---|---|---| | Free | $0 | 5 | Side projects | | Team | $29/seat/month | 50 per seat, pooled | Product teams without a dedicated SRE org | | Business | $59/
Updated Jul 8, 2026
Status pages overview
Beacon status pages are public, fast, and hosted off your infrastructure — so they stay up when you don't. What you get - Component-level status driven directly by your monitors (no manual toggling
Updated Jun 10, 2026
Public Policies
Terms, privacy, and public policies
Service level agreement (SLA)
For Business and Enterprise plans, Beacon commits to 99.9% monthly availability of the monitoring and alerting pipeline. What counts as unavailable: checks not executing on schedule, or alert notific
Updated Jun 8, 2026
Data retention policy
What we keep and for how long: - Raw check results: 90 days (Team), 13 months (Business+) - Incident history and timelines: retained for the life of the account - Uptime rollups (daily): retained for
Updated May 31, 2026