Documentation

Everything you need to get the most out of Beacon — from your first monitor to advanced alerting.

01

Getting Started

Beacon gets you up and running in under a minute. No complex configuration, no CLI tools — just a browser.

1

Sign up

Click 'Get started free' and sign in with your GitHub or Google account. No password to remember.

2

Add your first monitor

Click '+ Add monitor', paste your URL, choose a check interval (from 1 to 60 minutes), and hit save.

3

Set up alerts

Go to Settings → Alert Channels and add your email. You'll get notified the moment something goes down.

4

Create a status page

Go to Status Pages → New, pick a slug, and select which monitors to show. Share the public URL with your users.

02

Monitors

Monitors are the core of Beacon. Each monitor watches a single URL or API endpoint and checks it at your chosen interval.

How it works

Beacon sends an HTTP request to your URL using the method you specify (GET, HEAD, or POST). If the response status is 2xx, the check is UP. Anything else is DOWN.

Each check records: status, response time (ms), HTTP status code, and any error message.

If a request exceeds the configured timeout (5s, 10s, 30s, or 60s), the check is marked as TIMEOUT.

Check intervals

1 min, 5 min, 10 min, 30 min, or 1 hour

HTTP methods

GET, HEAD, or POST

Response times

Tracked in milliseconds per check

Timeouts

5s, 10s, 30s, or 60s configurable

03

Status Pages

Status pages are public-facing dashboards that show the health of your services. They're the window between your monitoring and your users.

Monitors vs Status Pages

Monitors
  • Private — only you see them
  • The engine that runs checks
  • Records raw uptime data
  • Triggers incidents and alerts
Status Pages
  • Public — shared with your users
  • The face your customers see
  • Shows selected monitors only
  • Custom domain support (Pro)

Each status page has a unique slug (e.g. /status/my-company). You choose which monitors appear and their display order. Your users see real-time status, uptime timelines, and any active incidents.

04

Incidents

Incidents are automatically created and resolved — you don't need to manage them manually.

Monitor goes DOWN

When a check fails for the first time after being UP, an incident is created automatically with the failure cause.

Ongoing outage

Subsequent failed checks keep the incident open. The duration timer keeps running.

Monitor recovers

When the monitor returns a healthy response, the incident is resolved with the total downtime duration.

Each incident records: start time, resolution time, duration (in seconds), and the cause (HTTP error or timeout reason).

05

Alerts

Alerts notify you when a monitor goes down or recovers. You configure alert channels in Settings — each channel is a destination for notifications.

📧

Email alerts

All plans

Receive detailed HTML emails with the monitor name, URL, status, and timestamp when something goes wrong — and when it's back up.

📱

SMS alerts

Pro only

Get text messages to your phone. Critical for on-call scenarios when you're not at your desk.

Alert channels are verified on creation. Free plan: 1 channel. Pro plan: up to 10 channels.

06

Plans & Limits

FeatureFreePro — $5/mo
Monitors3Unlimited
Alert channels110
Check frequencyEvery minuteEvery minute
Email alerts
SMS alerts
Data retention7 days1 year
Status pages
Custom domains
Priority support
07

Use Cases

Indie developers

Monitor your side projects and personal APIs. Know if your portfolio or SaaS goes down. Free plan covers most personal needs.

SaaS companies

Track uptime across your entire stack — API, web app, database, CDN. Share a branded status page with your customers.

API providers

Monitor multiple endpoints across versions. Give API consumers confidence with a real-time public status page.

Agencies & freelancers

Monitor client websites after launch. Demonstrate value by showing uptime reports and proactive incident management.

Ready to start monitoring?

Set up your first monitor in under 30 seconds.

Get started free