A global product. Put the hub where your policy says.
The hub is one container with one data volume and one outbound call to the AI API. Agents only ever need to reach the hub. Hosted by us, on your premises, or in your own cloud — in the region you already use. Sydney is one hosted option, not the product's identity.
Hosted by Binary Elements
Sign in and start enrolling. Backups, patching, TLS and uptime are ours. The hosted region we run today is Sydney. Best when you would rather not run another server.
On-premise
A box in your own rack or the customer's. One container, one volume. Nothing leaves the building except the AI API call, and that can be switched off per company.
Your own cloud
The account and region you already pay for. A small VM is plenty for hundreds of machines. Your data stays in your tenancy and your backups are your own.
One container, one volume, one hostname.
docker run -d --name be-hub \ -p 8001:8001 -v be-hub-data:/data \ -e PUBLIC_URL=https://hub.[yourdomain] \ -e ADMIN_PASSWORD=… -e ANTHROPIC_API_KEY=… \ be-hub:latest # put TLS in front (Caddy, Traefik, nginx) and open 443 outbound from the machines
The hub is a single Node process with an embedded database. Releases, the audit trail and history live on the volume. Upgrades are a new image and a restart; agents reconnect within two minutes. [Confirm the image name and the environment variables against the docs before publishing.]
About running it.
What does the hub need?
Can I move from hosted to self-hosted later?
Which cloud and which region?
Where is the hosted option?
Does BE AI still call an external API when self-hosted?
How is self-hosting priced?
One control plane. Named people approve every change.
Shadow your incumbent on up to 100 devices, or start a free trial. Your approvals, your data. Uninstall the agent and you are out.