// HTTP(s) integration
Start with one production or health-check URL in about 60 seconds.
Beaam requests your URL every minute — any HTTP response means 'up', a network error or timeout means 'down'. The K-of-N engine decides when it's a real outage, so a single blip stays quiet.
Curated deliberately: a short list worth your attention, not every metric that exists. Each one needs repeated evidence before Beaam calls it — a single bad reading is not an incident.
| Signal | When Beaam speaks up |
|---|---|
| Endpoint reachable | No response (network error / timeout) → broken. |
| Response time | ≥ 3s → degraded. |
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
setup
Paste a public HTTP or HTTPS URL. Beaam starts watching immediately.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
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.
2 signals can raise an incident: Endpoint reachable, Response time. Everything else is collected for context but stays quiet until you opt in.
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.
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.
The free plan covers two integrations and five watched services, with email, push, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations and services, adding SMS — there is no per-host, per-check or per-alert metering.
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.