Monitor Neon.Hear only when it matters.
Watch project, default-branch, compute, quota, and control-plane health without paging for scale-to-zero.
What Beaam does with Neon
Beaam imports every project in the API key's authorized scope, including shared projects, and checks its default branch, computes, quotas, and complete recent operation history every minute.
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 |
|---|---|
| Database availability | No compute, a disabled compute, or an unavailable default branch → broken. |
| Control-plane operations | An unresolved failed or stuck operation → degraded. |
| Quota | A quota at 80% → degraded; exhausted → broken. |
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.
- Compute state
- Quota utilization
What connecting needs
- A Neon API key: personal, organization or project-scoped. A project-scoped key is the least privilege. Beaam only calls read endpoints. There is no sign-in option.
- Neon allows 700 API requests a minute per account; Beaam stays under 600 and reports projects beyond that budget as a collection error rather than as empty.
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.
- Idle computes and scale-to-zero never alert, and an archived default branch is not an outage — Neon unarchives on access.
- Neon's control plane does not expose SQL availability, CPU, memory, connections, cache, deadlocks, database size or replication lag, so Beaam does not see them.
setup
Designed to stay small
Paste a personal, organization, or project-scoped Neon API key. Beaam imports its complete authorized project scope.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
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.
Questions
What does Beaam alert on for Neon?
3 signals can raise an incident: Database availability, Control-plane operations, Quota. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect Neon?
Paste a personal, organization, or project-scoped Neon API key. Beaam imports its complete authorized project scope. 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 Neon?
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.
What does Neon 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 Neon?
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.