// faq
If a question here has an evasive answer, tell us — support@beaam.app.
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.
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.
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.
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.
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.
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.
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.
Email, mobile push, Slack and generic webhooks on every plan, including Free. SMS is the one channel Solo adds. The webhook covers Discord, Zapier, n8n and anything else that accepts JSON.
Free for two integrations and five watched services, with email, push, Slack and webhook alerts and a public status page. Solo is $19/month flat: unlimited integrations and services, and SMS on top. No per-host, per-check, per-alert or per-seat metering.
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.
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.
In billing, in one click. Billing runs through Polar as merchant of record, so invoicing and tax are handled properly for wherever you are.
Read-only, always. Beaam never writes to a connected provider. Most integrations use a read-scoped API token you create in the provider and can revoke at any time. Credentials are encrypted with AES-256-GCM and deleted the moment you disconnect.
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.
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.
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.
The free plan answers most of this faster than we can. It takes about five minutes to a first watched service.