Beam's collector already runs on the endpoint and writes to local disk by default — nothing to change there. For teams that also want the fleet dashboard inside their own network, it's a Next.js app backed by Postgres that you deploy and own, so agent activity never has to reach Beam's cloud.
This isn't a separate product tier — it's the same open-source core, deployed on infrastructure you control instead of ours.
Beam is local-first at the endpoint by design. On-premise deployment extends that to the fleet dashboard, so the whole stack — collection, storage and review — sits behind your own perimeter.
Collector
127.0.0.1:4319 by default. Events never leave the machine unless you export them yourself.
Storage
The endpoint writes local NDJSON at 0600. The dashboard's Postgres instance lives wherever you run it — your VPC, your data center.
Dashboard
Same Auth.js-backed control plane Beam runs, packaged as a normal app: point it at your own Postgres and it's yours to operate.
Network
Self-hosted end to end, the stack has nothing to phone home to. Any egress you see is from the AI tools you're monitoring, not from Beam.
Access
Manager and team-member accounts live in your Postgres. Beam never holds a copy.
Source
The collector is open source, so you can read exactly what ships to your endpoints before you trust it with production repos.
01
It's local by default — this part needs no network decision to make.
02
A managed instance or a container you run — Beam doesn't require a specific host.
03
Point the dashboard at your database and set its auth secret. It serves your org from inside your network.
04
Endpoints keep recording locally; the dashboard aggregates what your team chooses to bring into it.
The endpoint collector already is: it binds to 127.0.0.1 and writes local NDJSON by default, with no cloud dependency. On-premise deployment is really about the fleet dashboard, which is a self-hostable Next.js + Postgres app rather than something you're required to point at Beam's cloud.
Not yet as a packaged installer — the dashboard is a standard Next.js app backed by Postgres via Prisma, and you deploy it the way you deploy any app in your stack. If you need help wiring it up, talk to us.
No. Redaction, event schema and local storage behavior are identical whether or not you run the dashboard in-house — self-hosting changes where the fleet view lives, not what the endpoint does.
Not in v1. Accounts use credentials login against your own Postgres. If your organization needs SAML or OIDC, tell us — it's a reasonable ask we don't want to overstate as already built.
The endpoint is local by default. Self-host the dashboard alongside it and nothing has to leave your infrastructure.