3 October 2026
Each integration says what it needs, and what it will not tell you
Every integration page now lists exactly what connecting needs — the OAuth scopes Beaam requests, the token type and minimum permissions, and any limits that come from your plan with that provider — and what Beaam deliberately does not alert on or cannot see. Writing those pages turned up a correction: Beaam has always said it never writes to a connected provider, and two integrations do, once. Connecting Resend registers a webhook, and signing in with Vercel creates a runtime Log Drain, so those providers can push events to Beaam. Disconnecting does not yet remove them; both pages say where to delete them. Beaam still never changes your infrastructure.
3 October 2026
The API as an OpenAPI 3.1 document
The API reference now offers an OpenAPI 3.1 download beside the Postman collection, generated from the same production manifest: every operation's input and response schema, the shared error envelope, and a note on each operation that can refuse in-band, so a generated client knows to check data.status and not only the HTTP status. Each operation on the reference also has a copyable example request, and on a phone the operation index is a collapsed, filterable list.
27 September 2026
Alerts that were not about your system, removed
Five alerts were found to be describing something other than an outage on the customer's side, and each now stays quiet: a Free Supabase project with no backups (Supabase does not back up Free projects), Supabase's disk endpoint refusing sign-in grants (it now says that, instead of asking you to reconnect), an archived Neon branch (Neon unarchives on access), a Cloudflare Pages site with nothing to measure, and Beaam's own timeout reading a Hostinger VPS. Where Beaam genuinely cannot read something, that is now shown as Beaam's problem, never as yours.
22 September 2026
Reply STOP to stop SMS, and a dead connection is mentioned again
Replying STOP to a Beaam SMS now stops further messages to that number, and START resumes them. Separately, a connection that has been failing for a week is now said again, weekly, instead of being reported once and then never.
21 September 2026
SMS alerts are live
Solo accounts can receive incident alerts by SMS, delivered and confirmed in production — sent from an Australian number to Australian phones. A delivery receipt from the carrier, not just acceptance, is what marks an SMS as delivered.
15 September 2026
Incidents now end with an all-clear
When an incident Beaam alerted you about is over, you hear that too: what recovered, how long it lasted, what came back first, and the change the first alert pointed at. It is sent only where an alert went out, so a quiet incident stays quiet, and never by SMS.
14 September 2026
Alerts say how sure Beaam is, and you can correct what it learned
When an alert says a change explains a failure, or that several incidents are one story, it now says how strong that evidence is, instead of using the same words for a deploy two minutes before and an event half an hour before. Each service has a What happened timeline that puts changes and failures on one axis. And where Beaam has learned that two services tend to fail together, you can tell it whether that is a real dependency or a coincidence.
11 September 2026
Tell Beaam you deployed
A deploy Beaam cannot see — a VPS, a docker compose up, a release script — can now be recorded through the API or the MCP connector, and it is weighed as evidence when something breaks shortly after, named by its commit.
10 September 2026
A deploy on one provider can explain a failure on another
Change correlation now looks across the whole stack: a Vercel deploy can be offered as the likely cause of a Neon failure. Incidents that Beaam groups into one story now say why they were grouped, and several checks against the same website count as one website rather than several alerts.
9 September 2026
Google measurement asks only where the law requires it
Visitors in the EU, the wider EEA, the UK and Switzerland are asked before Google Analytics or Ads measurement runs; elsewhere it runs unless declined, and a decline is honoured on both beaam.app and app.beaam.app.
7 September 2026
See which AI assistants are actually connected
A new Assistant page lists the AI clients that hold a live connection to your Beaam account — active, authorised but not yet used, or idle — and lets you revoke one. An assistant that was authorised but has never made a call is the most common way a connection half-works, and it is now shown as exactly that.
7 September 2026
Consent-first Google Analytics
A GA4 web stream now measures the public beaam.app journey only after a visitor explicitly allows it. Page views, campaign/referral information, scrolls, outbound clicks and downloads help explain which content works; the signed-in application sends only one completed-signup event. No email address or product activity is sent, and Google signals, advertising personalization and enhanced conversions remain off.
6 September 2026
iOS and Android apps in closed beta
The Beaam mobile apps are in closed beta with a small group of founders and will be released publicly soon. They carry the same alerts, phrased the same way, as notifications on your phone, alongside the same view of what is wrong and what changed. Nothing changes in how Beaam decides what to send — the apps are another place to receive it.
6 September 2026
Consent-first advertising measurement
Beaam can now measure whether one of its own Google Ads led to a completed account signup. The Google tag is not requested until a visitor explicitly permits advertising measurement; declining leaves it unloaded. Enhanced conversions are off, so no email address or signed-in product activity is sent. The choice is shared across beaam.app and app.beaam.app and can be changed from the privacy policy or site footer.
20 August 2026
Free does more than we were saying
Push, Slack and generic webhook alerts have always worked on the free plan, and the public status page has never been paywalled — the pricing page said otherwise. Corrected: SMS is the only channel Solo adds. Provider lists across the site now come from the live integration catalog rather than being maintained by hand, so what you read on the homepage is what the product actually connects.
17 August 2026
Notification destinations and stacks became manageable objects
Notifications and stacks share one settings pattern — a readiness summary, grouped rows, creation in a modal and focused editing in a drawer. Multiple email addresses and devices stay separate rows instead of expanding the page into a form. A stack that is not finished set up says what is left, and stops saying it once telemetry arrives.
16 August 2026
Realtime updates, and AWS withdrawn
Screens now update over a websocket, with the existing poll kept as the backup — a dead socket costs a little latency and never silence. AWS monitoring was withdrawn the same day: it is built and its documentation stays up, but it cannot be connected while its setup flow is reworked, and existing connections have stopped collecting.
16 August 2026
Analytics on the marketing site
Plausible now counts visits to beaam.app — cookieless, EU-hosted, no cross-site identifier, no IP address stored, and never loaded inside the application. Announced here rather than added quietly, because the subprocessors page promises exactly that; it is listed there with what it receives. The same update corrected a stale data-residency line: the control-plane database moved to us-east-1 on 3 August and the page still said Mumbai.
24 July 2026
Launch foundations
Production signup, default email delivery, verified test-alert activation, secure public status publishing, account deletion, password recovery, security headers, and independent watchdog trip tests.
13 July 2026
Now + Workbench
A calmer operations home, focused incident acknowledgement, shared integration views, service workbenches, and mobile Situation Room.
19 June 2026
Capability architecture
AWS monitoring and a single capability contract spanning web, API, CLI, and MCP.