Monitor Polar.Hear only when it matters.
Know what share of your subscriptions have stopped paying, before the churn report does.
What Beaam does with Polar
Beaam reads Polar every minute for payment, checkout, order, refund, dispute, subscription, organization and webhook-delivery health. Revenue and conversion are charted as context, not alerted on by default.
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 |
|---|---|
| Organization and payouts | Alerts when the organization is not active or payouts are unavailable. |
| Revenue operations | Alerts on failed payments, failed checkouts/refunds, void orders and disputes needing response. |
| Webhook delivery | Alerts when endpoints are absent/disabled or recent deliveries fail. |
| Subscription payment health | Alerts when at least 10 subscriptions exist and 10% are past due or unpaid. |
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.
- Subscriptions
- Revenue trends
- Operational failures
What connecting needs
- Sign in with Polar, or an Organization Access Token (
polar_oat_). Either way:organizations:read,subscriptions:read,events:read,payments:read,checkouts:read,orders:read,refunds:read,disputes:read,webhooks:read,metrics:read. - One organization per connection: a credential that reaches more than one is refused.
- Sandbox organizations need a token — sign-in is production only.
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.
- Revenue, MRR, conversion and churn are charted, never alerted on.
- The subscription-health alert waits for at least 10 subscriptions.
- If more than 100 events land in a window, the check reports that it could not count them all rather than a short total.
setup
Designed to stay small
Sign in with Polar and approve read-only access to one organization — no token to create.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
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.
Questions
What does Beaam alert on for Polar?
4 signals can raise an incident: Organization and payouts, Revenue operations, Webhook delivery, Subscription payment health. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect Polar?
Sign in with Polar and approve read-only access to one organization — no token to create. 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 Polar?
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.
What does Polar 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 Polar?
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
DigitalOcean
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
Vercel
Hear about a failed production deploy — and nothing at all about your preview builds.
Netlify
Find out a deploy failed before you tell a customer the fix is live.
All integrations
Everything Beaam watches today, and what is on the roadmap.