Monitor HTTP(s).Hear only when it matters.
Start with one production or health-check URL in about 60 seconds.
What Beaam does with HTTP(s)
Beaam requests your URL every minute and checks that it is reachable and returns the status (and optional body text) you expect. The K-of-N engine decides when it's a real outage, so a single blip stays quiet.
What raises an incident
Curated deliberately: a short list worth your attention, not every metric that exists. Signals that can blip need repeated evidence before Beaam calls them; a reading that is definitive by nature — the provider reporting a failure outright — alerts on the first observation.
| Signal | When Beaam speaks up |
|---|---|
| Endpoint healthy | No response or an unexpected status/body for 2 of 3 checks → broken. |
| Response time | ≥ 3s → degraded. |
Also collected, but quiet
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
- HTTP status
- Response time
What connecting needs
- A public
httporhttpsURL — no credentials. Private, local and internal addresses are refused, as are ports other than 80, 443, 8080 and 8443. Up to 3 redirects are followed. - A hostname, not a bare IP address. Beaam runs on Cloudflare's network, which can't call an IP address directly — point a DNS record at it and use that name.
- Up means a 200–399 response by default; set your own range per service. Optionally require text in the first 1 MB of the body. Requests time out after 10 seconds.
What Beaam will not tell you
Stated rather than discovered later. Some of these are deliberate — an alert that is not about your system is noise — and some are simply where this integration's view ends.
- Beaam sees only what the URL returns: a broken app that still answers 200 looks up. Use the expected-text check, or point it at a health route that tests what matters.
- Broken means 2 of 3 checks failed; slow (3 seconds or more) is degraded, not down.
- A bare URL has no change history, so there is nothing to correlate an incident against.
setup
Designed to stay small
Paste a public HTTP or HTTPS URL. Beaam starts watching immediately.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
Beaam never writes to HTTP(s). Credentials are encrypted with AES-256-GCM using a key held as a deploy secret, and are deleted immediately when you disconnect.
Questions
What does Beaam alert on for HTTP(s)?
2 signals can raise an incident: Endpoint healthy, Response time. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect HTTP(s)?
Paste a public HTTP or HTTPS URL. Beaam starts watching immediately. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
Does Beaam need write access to HTTP(s)?
No. Beaam only ever performs read operations — there is no code path that writes to a connected provider. Worth separating from that: what Beaam *does* and what a token *permits* are different things. Where HTTP(s) offers a read-scoped credential, use it; some providers only issue tokens carrying broader rights than Beaam uses, which is a property of their API rather than of Beaam's behaviour. Scope it as narrowly as the provider allows. Credentials are encrypted with AES-256-GCM before storage and deleted the moment you disconnect.
What does HTTP(s) monitoring cost?
The free plan covers two integrations and five watched services, with email, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations, services and organizations, with collaborators included — there is no per-host, per-check or per-alert metering.
Watching more than HTTP(s)?
Most stacks are several services with seams between them, and the seams are where the damaging failures hide. Beaam correlates across every connected integration, so a database problem reads as one incident rather than five alarms from five tools.