Discovered is not watched.You choose the second part.

Discovering and watching

Connecting a provider makes Beaam discover what is in the account — Workers, projects, sites, databases, droplets. Discovered resources are listed on the integration page. They cost nothing and nothing is collected from them.

A watched service is one Beaam actively checks, roughly once a minute, and can alert you about. Watching is the part your plan counts, and it is the part you decide.

What is watched when you connect

It depends on what you connected and how. Beaam follows one rule throughout: watch everything, or watch nothing and say so. It never watches a subset it chose itself.

• One resource, watched straight away. An HTTP check, an MCP server or your Stripe account is a single thing, so it is watched as soon as it connects.
• Approving access at Cloudflare, Supabase or Vercel. If everything Beaam found fits your remaining allowance, all of it is watched. If it doesn't fit, none of it is, and the connection message tells you to choose on the integration page.
• Everything else. Connecting with an API token, and connecting DigitalOcean, Hostinger, Netlify, Resend or Sentry, imports what was found with nothing watched. The connection message says so, and the integration page is where you pick.

An account with nothing in it still connects. Finding zero resources is a real answer, and Beaam reports it as one rather than refusing.

Watching and unwatching

In the web app, open the provider's integration page. Each connected account lists what was discovered, grouped by resource type, with a checkbox per resource, a watch all or watch none per group, and a count of how many are watched. Nothing changes until you press Save; until then the page says you have unsaved changes. The Services list also has an unwatched view, where you can start watching one discovered service at a time.

From the API or an assistant connected throughMCP, the same choices are capabilities:

• set-watchlist sets the whole list for one connection. The services you name are watched and every other one is unwatched.
• set-service-watched turns one service on or off without touching the rest.
• set-service-mute keeps a service watched but holds its alerts back for a while.

Unwatching stops collection for that service. Its past history stays, but nothing new is recorded. If you only want it to stop talking while you fix something, mute it instead.

The Free plan's five

Free watches up to five services across the organization; Solo has no limit (see plans and limits). Going past five is refused rather than quietly trimmed — whether you save a watchlist or switch on one service at a time — so what you asked for is always what is watched.

When a connection discovers more than you have room for, it still connects and watches none of it. Everything stays listed, so you can pick the five that matter now, and upgrading later is a matter of ticking more boxes rather than reconnecting.

The first check

A service you have just started watching has no result yet. Until its first check lands, it shows that it is settling, with a moving marker, so you can tell "not checked yet" from "nothing is happening".

That wait is timed from when you asked for the service to be watched, and it is bounded at 15 minutes. Collection runs every minute, so a first check that hasn't arrived by then is not still starting. The marker stops moving, because by that point it is stuck, and a spinner would be saying otherwise.

New resources

Beaam re-discovers each connection every 30 minutes. Anything new is added unwatched. Quiet by default applies here too: a resource you never chose should not start alerting you the moment it appears.

If you have just created something and don't want to wait, pressCheck for new resources on the account in the integration page. It runs the same re-discovery straight away. From the API or an assistant, it is rediscover-integration.

Re-discovery also refreshes names. It does not treat a short answer as a deletion: if part of a provider's inventory could not be read, Beaam adds and refreshes what it did see and leaves everything else as it was.

When a watched resource disappears

If the provider stops listing something you watch, Beaam marks it as no longer found and stops collecting it. It does not just go quiet:

• The service's status says so in words — no longer found at the provider since a given date, so Beaam stopped watching it — rather than looking like a late check.
• Your organization's default channels are told once per disappearance, not every minute after.
• On the integration page it is struck through and labelled no longer found, so you can't tick something that no longer exists and wait for alerts that can never come.

The row is kept, with its history and any thresholds you tuned. If the provider lists it again, the next re-discovery picks it back up. If it is gone for good, the account offers to remove everything no longer found; that is permanent and takes the history with it.

One case keeps its watch automatically. Sentry can report the same project under a second identifier — when a project has no production environment, for example. Beaam knows the two are one project, and moves the watch, your name for it, your tuned rules and its notification routes across to the new one.

Deployed sites: checking they answer

Netlify sites,Cloudflare Pages projects andHostinger websites have a gap. Those providers report deploys and settings, not whether the site is answering visitors. A static site has no request errors to measure.

So for each watched site that isn't covered yet, Beaam offers anAdd HTTP check for the site's own address, in an "Also check that they answer" card on the provider's page and the site's own page. One click sets up an HTTP check. That check is an integration of its own, so on Free it counts towards the two-integration limit. From the API or an assistant, the same list issuggest-http-checks.

Questions