// DigitalOcean integration
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
Beaam imports every Droplet the token can see and reads each one's state every minute. DigitalOcean's Droplets API reports lifecycle rather than health — active, off, archive — so Beaam charts that state and leaves the alert switched off by default: a powered-off Droplet is usually someone turning it off deliberately.
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 |
|---|---|
| Droplet not running | Droplet powered off or archived → broken. Off by default; turn it on per Droplet. |
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
Sign in with DigitalOcean — read-only, no token to create. Beaam imports every Droplet it can see.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Beaam never writes to DigitalOcean. 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: Droplet not running. Everything else is collected for context but stays quiet until you opt in.
Sign in with DigitalOcean — read-only, no token to create. Beaam imports every Droplet 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 DigitalOcean 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.
Find out a deploy failed before you tell a customer the fix is live.
Know when a compute is disabled or Neon's control plane fails — without being paged for scale-to-zero.
Catch a sending domain going unverified before your email quietly stops arriving.
Everything Beaam watches today, and what is on the roadmap.