// Polar integration
Know what share of your subscriptions have stopped paying, before the churn report does.
Beaam reads your Polar organization every minute and tracks how many subscriptions are past due or unpaid, as a share of your paying base. It alerts on the share, not the count, so the same threshold still means something after you grow.
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 |
|---|---|
| Failing payments | ≥ 10% of subscriptions past due or unpaid → 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 read-only Organization Access Token from your Polar organization settings.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Beaam never writes to Polar. 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: Failing payments. Everything else is collected for context but stays quiet until you opt in.
Paste a read-only Organization Access Token from your Polar organization settings. 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 Polar 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.
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
Hear about a failed production deploy — and nothing at all about your preview builds.
Find out a deploy failed before you tell a customer the fix is live.
Everything Beaam watches today, and what is on the roadmap.