// Netlify integration
Find out a deploy failed before you tell a customer the fix is live.
Beaam imports every Netlify site the token can see and checks each site's recent deploys every minute. A failed deploy is reported as degraded rather than broken: Netlify keeps serving the last good deploy, so the site is fine and stale — what you have lost is the change you thought shipped.
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 |
|---|---|
| Failed deploys | Any deploy failed in the last hour → 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 Netlify personal access token. Beaam imports every site it can see.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Beaam never writes to Netlify. Credentials are encrypted with AES-256-GCM using a key held as a deploy secret, and are deleted immediately when you disconnect.
1 signals can raise an incident: Failed deploys. Everything else is collected for context but stays quiet until you opt in.
Paste a Netlify personal access token. Beaam imports every site it can see. 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 Netlify 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.
Catch a sending domain going unverified before your email quietly stops arriving.
Monitor remote MCP endpoints alongside the rest of your product.
Start with one production or health-check URL in about 60 seconds.
Everything Beaam watches today, and what is on the roadmap.