Hosted by us, on your premises, or in your own cloud.
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. Put it where your data policy says.
Hosted by Binary Elements
Sign in and start enrolling. Backups, patching, TLS and uptime are ours. Hosted in [REGION]. 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 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=… \ ghcr.io/[org]/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?
Does BE AI still call an external API when self-hosted?
Put BE Hub on ten machines this week.
A pilot takes an afternoon: one install link, your own approvals, your own data. Uninstall the agent and you are out.