// Neon integration
Know when a compute is disabled or Neon's control plane fails — without being paged for scale-to-zero.
Beaam imports every Neon project the key can see and checks each one's computes and recent operations every minute. It alerts when a compute is disabled or when Neon's control plane fails an operation — and deliberately stays quiet when a compute is idle, because scale-to-zero is the product working as intended.
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 |
|---|---|
| Compute disabled | Any disabled compute → broken. |
| Failed operations | Any operation 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 Neon API key. Beaam imports every project it can see.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Beaam never writes to Neon. 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: Compute disabled, Failed operations. Everything else is collected for context but stays quiet until you opt in.
Paste a Neon API key. Beaam imports every project 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 Neon 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.