Monitor Supabase.Hear only when it matters.
Keep watch over the backend behind your product.
What Beaam does with Supabase
Beaam imports every Supabase project you can access and checks all eight provider health components. It also watches database disk and connection pressure, expected backups, API 5xx rates, PostgREST and pooler saturation, memory, latency, restarts, WAL, and read-replica health when the grant exposes them. Sustained failures earn attention; brief blips stay quiet.
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 |
|---|---|
| Core services | Database, REST, Auth, Storage, or Realtime unhealthy → broken. |
| Capacity | Disk exhaustion, database or pooler connection pressure, and REST pool pressure. |
| Recovery | Configured backups overdue, or a read replica disconnected, paused, or materially lagging. |
| API reliability | 5xx responses alert only after at least 20 requests in five minutes. |
| Database crash loop | PostgreSQL restarting twice or more in an hour, or PostgREST requests timing out for a database connection → attention. A single restart is recorded as a change, since Supabase restarts Postgres for upgrades. |
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.
- All health components
- Database performance
- Connection paths
- Recovery posture
What connecting needs
- Sign in with Supabase: the permissions are fixed on Beaam's registered app rather than chosen at sign-in, and are read permissions.
- Access token instead: a personal access token (
sbp_). It is account-wide and carries your own permissions. - Disk utilisation is token-only: Supabase rejects that endpoint for sign-in grants.
- Free projects have no scheduled backups, so Beaam does not alert on backups there. Logs and some other endpoints are limited by plan.
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.
- The 5xx-rate alert waits for at least 20 requests in the window.
- Supabase's Metrics API is in beta at Supabase.
- There is no history of restarts, resizes or restores to correlate against.
- Memory, latency and coverage alerts are off by default.
setup
Designed to stay small
Sign in with Supabase and approve read-only access — no token to create. Beaam discovers your projects; an account access token still works instead.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
Beaam never writes to Supabase. 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 Supabase?
5 signals can raise an incident: Core services, Capacity, Recovery, API reliability, Database crash loop. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect Supabase?
Sign in with Supabase and approve read-only access — no token to create. Beaam discovers your projects; an account access token still works instead. 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 Supabase?
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 Supabase 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 Supabase 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 Supabase?
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.
Other integrations
Polar
Know what share of your subscriptions have stopped paying, before the churn report does.
Hostinger
Catch Hostinger VPS, website, mail and subscription trouble before customers do.
DigitalOcean
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
All integrations
Everything Beaam watches today, and what is on the roadmap.