// faq
Straight answers,even the awkward ones.
If a question here has an evasive answer, tell us — support@beaam.app.
Is this for me?
Who is Beaam actually for?
A solo technical founder, or a two-to-three person team, running a real product on a handful of services with nobody to delegate monitoring to. If you have a dedicated SRE, or you want to tune your monitoring, Beaam will frustrate you — the curation is the product.
I already use UptimeRobot. Why would I switch?
If all you need is "is my marketing site up?", you should not — a free pinger does that well. Beaam is for when a 200 response stops being the same thing as working: a Lambda erroring, a webhook backlog, replica lag. Uptime tools cannot see those, and cannot correlate across them.
Do I need to be on a particular cloud?
No. The fastest start is a single HTTP URL, and Beaam watches 14 providers across hosting, databases, payments, errors and email. If you already export OpenTelemetry, point it at Beaam and skip connecting anything.
What if my stack isn't supported?
Beaam connects 14 providers today — Cloudflare, DigitalOcean, Hostinger, HTTP(s), MCP Server, MongoDB Atlas, Neon, Netlify, Polar, Resend, Sentry, Stripe, Supabase and Vercel. Any HTTP endpoint works too, and OTLP covers anything you can instrument. Firebase, Fly.io, Google Cloud, Railway and Render are next on the roadmap. Email support@beaam.app and tell us what you run — it genuinely shapes the order.
Alerting
How do I know it won't spam me?
A signal must fail repeatedly in a window before Beaam calls it broken, correlated incidents arrive as one message, and a 30-minute cooldown per service stops a bad deploy becoming twenty alerts. See how alerting decides for the full rules.
Will Beaam tell me when it's over?
Yes. When everything in a correlated group recovers, Beaam sends the all-clear: what came back, how long it was out, which service recovered first when that was not the one that broke, and the same change the opening alert pointed at. It goes only where the alert went — if a failure was not worth waking you for, its recovery is not either — and never by SMS.
How fast will I hear about a real problem?
Typically a few minutes: collection runs every minute and confirmation takes a poll or two. Beaam is deliberately slower than a single-sample alerter, because firing on one reading is what makes tools ignorable.
What if Beaam itself goes down?
Three things cover it. A daily heartbeat tells you Beaam is alive on a normal day. Per-account silence detection watches your own collectors and alerts you if they stop reporting — it has caught a real outage in production. And an independent watchdog on a separate cloud account probes Beaam every minute and alerts Beaam's operator if the whole service goes quiet; it shares no infrastructure with the app, otherwise it would fail at exactly the moment it is needed.
Where do alerts arrive?
Email, Slack and generic webhooks on every plan, including Free. The webhook covers Zapier, n8n and anything else that accepts JSON.
Is there a mobile app?
Yes — iOS and Android apps are in closed beta with a small group of founders and will be released soon. They bring the same alerts, phrased the same way, to your phone as notifications, with the same clear view of what is wrong and what changed. Until they ship, email, Slack and webhooks carry every alert on every plan, and nothing about your setup changes when the apps arrive.
Pricing and billing
What does it cost?
Free for two integrations and five watched services, with email, Slack and webhook alerts and a public status page. Solo is $19/month flat: unlimited integrations, services and organizations, collaborators included. No per-host, per-check, per-alert or per-seat metering.
Why flat pricing?
Metered monitoring makes coverage another thing to manage. A founder who declines to watch their payment webhook because it is "another $2/monitor" is one bill shock from churning and one missed incident from disaster. Flat pricing removes the maths.
Is there a free trial of Solo?
The free plan is the trial, and it does not expire. It is deliberately enough to prove the whole path — connect, first signal, real delivered alert — and deliberately not enough to run a production stack.
How do I cancel?
In billing, in one click. Billing runs through Polar as merchant of record, so invoicing and tax are handled properly for wherever you are.
Security and data
What access does Beaam need?
As little as each provider allows, and Beaam never changes your infrastructure. Most connections are read-only; Netlify and Resend cannot grant less than full access, and Beaam only reads with those. The one write Beaam makes is registering a delivery endpoint — a webhook in Resend, a Log Drain in Vercel — and each integration page names exactly what it needs. Credentials are encrypted with AES-256-GCM and deleted the moment you disconnect.
How long do you keep my data?
Raw metric samples expire after 30 days. Incidents, alerts and delivery records are kept while your account is active, because that history is the thing you look back at. Deleting your account removes your control-plane data immediately.
Are you SOC 2 compliant?
No, and we will say so rather than imply otherwise. SOC 2 is out of scope until an enterprise customer asks. If that is a hard requirement, Beaam is not the right fit yet.
Where does my data live?
Supabase Postgres for the control plane and Tinybird for telemetry, with the app on Cloudflare Workers. Every subprocessor is listed publicly, along with its data-processing agreement status.
Still unsure?
The free plan answers most of this faster than we can. It takes about five minutes to a first watched service.