Two plans.One of them is free.
What each plan includes, what the limits are counted against, and exactly what happens when you reach one.
What each plan includes
| Free | Solo — $19/month | |
|---|---|---|
| Integrations | 2 | Unlimited |
| Watched services | 5 | Unlimited |
| Organizations | 1 | Unlimited |
| Collaborators | — | Included |
| Alert channels | Email, Slack, webhook | Email, Slack, webhook, SMS |
| Public status page | Yes | Yes |
| Daily heartbeat | Yes | Yes |
| Collection-silence alerts | Yes | Yes |
| Detection and correlation | Full | Full |
One flat price. Nothing here is metered per host, per check, per alert or per seat — see pricing for the reasoning behind that.
What Solo actually adds
Two things, and it is worth being precise because most of Beaam is on both plans. Solo adds capacity — unlimited integrations, watched services and organizations, with collaborators — and it addsone channel, SMS.
Detection is not a paid feature. Repeated evidence, cross-service correlation, the delivery ledger with its retries, the daily heartbeat and collection-silence alerting all run identically on Free. A free account watching five services gets the same engine as a paying one watching three hundred — it is watching fewer things, not watching them worse.
What the limits count
Limits are enforced per organization, because the organization is the billing unit. Two consequences worth knowing:
- Stacks do not multiply anything. Splitting five services across three stacks is still five watched services against the same allowance.
- An organization's plan derives from its owners. If any owner is on Solo, that organization is Solo — so inviting a Free teammate into a Solo organization does not downgrade it.
An integration is one connected account — your Cloudflare account, your Stripe account, one HTTP endpoint. A watched service is a single resource inside one of those that Beaam actively checks: a Worker, a cluster, a project. Discovering a resource does not count against anything; watching it does, which is why you choose what to watch after connecting rather than before.
Reaching a limit
Nothing degrades quietly. Connecting a third integration on Free refuses and says which limit it hit, rather than connecting and then silently collecting nothing.
Bulk discovery is the interesting case. Connect a provider holding thirty resources with two of your five services already watched, and Beaam watches up to the three you have left rather than refusing the connection outright — the account still connects, and you pick which resources keep the slots. Everything else is discovered, listed and unwatched, so upgrading later is a toggle rather than a reconnect.
Upgrading and cancelling
Billing runs through Polar, which is the merchant of record — it handles payment, invoicing and sales tax, and Beaam never sees your card. Upgrading takes effect when Polar confirms the subscription; there is no in-app path that grants a paid plan without that confirmation.
Cancelling leaves your data alone. Organizations, integrations and watched services you already have keep working, and the limits apply to creating more. Raw metric samples expire after 30 days on every plan; incidents and alert history are kept while the account is active.
Questions
Does the free plan expire?
No. There is no trial clock and no card at signup. It is deliberately enough to prove the whole path — connect something, get a first signal, receive a real delivered alert — and deliberately not enough to run a production stack, which spans more than two providers.
Are limits counted per person, per stack, or per organization?
Per organization. An organization is the billing unit, and counts are scoped to it — so splitting services across several stacks inside one organization does not multiply the allowance.
What happens when a connection would exceed the limit?
Connecting refuses and names the limit it hit. Where a provider discovers many resources at once, Beaam connects and watches up to your remaining allowance rather than refusing the whole connection — you choose which ones to keep.
If a collaborator is on Free, does the organization lose Solo?
No. An organization is Solo if any of its owners is Solo, so a Free teammate working inside a Solo founder's organization gets everything that organization has — that is the collaboration Solo pays for.
What happens to my data if I downgrade?
Nothing is deleted. Existing organizations, integrations and watched services keep working; the limits apply to creating more. Raw metric samples expire after 30 days on every plan.