Last updated 15 September 2026.
These terms are between you (the organisation that signs up) and Binary Elements, the company that runs BE Hub. By creating an account, ticking the box on the signup page, or using the service, you agree to them.
If you are signing up for a company, you confirm you can bind that company. If you cannot, do not create the account.
BE Hub is a remote monitoring and management service. You install a small agent on machines you are authorised to manage. The agent connects out to the hub. Your people use the console to see those machines, get alerts, run saved scripts, manage patches, browse files, take remote control, and ask BE AI to investigate.
The agent’s tool list is the security boundary. There is no generic remote eval. Custom checks are declarative data, not code we push. A mutating action that BE AI suggests still needs a person in your organisation to approve it, except where the product already documents a narrower rule (for example a signed-in technician deleting a file they can already see).
Self-serve signup opens a pending organisation. The trial starts when the owner verifies their email (or finishes signup with Google or Microsoft). The published trial is fourteen days and ten machines, with BE AI included and no card required, unless the hub you are on has been configured differently.
Machines past the trial cap still report and alert. BE AI does not look at them until you are on a paid plan or a superadmin lifts the cap.
You must give a real work email, keep your login to yourself, and tell us promptly if you think an account was taken over. Named seats are one person each. Sharing a login to dodge seating is a breach.
You may only install the agent on machines you own or are contracted to manage. You are responsible for telling the people who use those machines whatever your local law requires.
Uninstalling the agent (or decommissioning the machine from the console) stops it talking to us. That is how you leave. Leftover files next to a broken install are yours to delete.
run_shell and proxy_shell stay gated by a flag in that machine’s own agent.json. The hub cannot turn shell on remotely. If you enable it, commands run as the agent’s user — typically SYSTEM on Windows and root on Linux.
A signed-in technician can open a remote-control session on an online machine. There is no prompt and no notice on the machine itself; that is a deliberate product decision, not an omission. Your organisation can turn remote control off. Sessions are opened only by a signed-in person, never by an API key. Every session is recorded and written to the audit trail. Keystroke content is not stored.
The file explorer lets a signed-in technician list, read, download and delete files on a machine they manage. Paths are audited. File contents are not written to the audit log, because configuration files often hold passwords.
BE AI investigates using the facts the agent already reports, the history on the hub, and notes you have marked for it. Machine output (process names, event logs, file paths, command results) is treated as untrusted text. The model proposes; a person approves anything that changes the machine.
Using BE AI means we send that investigation context to our model provider (currently Anthropic) so it can answer. Do not paste secrets into a question if you do not want them sent. Notes for BE AI are the one channel besides the question that we treat as trusted technician instructions.
After the trial, BE Hub is billed monthly through Stripe in US dollars. The published price is a named technician seat plus optional BE AI run packs. Machines themselves are not metered on the current plan.
You can cancel from the billing page. Agents of a cancelled organisation are told to stop. We keep the account for a short hold (thirty days unless configured otherwise) so you can export, then we delete it. Failed payments move the account through past-due, then pause BE AI, then suspend. Alerts keep delivering while the account is read-only.
Taxes, if any, are added by Stripe for your location. We do not store full card numbers.
Do not use BE Hub to break the law, to watch or control machines you have no right to manage, to attack other systems, or to send malware. Do not probe the hub, scrape other customers, or try to cross tenant boundaries. Do not feed the service into a model or product that competes with it by copying our console, prompts or agent protocol.
We can suspend an organisation that is being abused or that puts other customers at risk. We will mail the owner when we can.
We will run the hosted hub with reasonable care, keep an audit trail of operator actions, and not sell your machine data. Hosted availability is best-effort; this is not a contract for a specific uptime percentage unless we have signed something else with you.
The software is provided as is. We are not liable for lost profits, lost data on a customer machine, or a decision a technician or BE AI made with the facts on screen. If a court nonetheless finds us liable, our cap is the fees you paid us in the three months before the claim — or one hundred Australian dollars if you were on a trial and had paid nothing.
You keep ownership of your machine data, notes, scripts and check documents. We need a licence to host, process and display them so the product works, including sending slices of them to the subprocessors listed in the privacy policy.
We may update these terms. Material changes will show a new date at the top of this page. Continuing to use BE Hub after that date is acceptance. If you do not agree, export your data and cancel.
These terms are governed by the laws of Victoria, Australia. The courts of Victoria have exclusive jurisdiction, except that we may seek an injunction anywhere to stop a breach.
Questions: csteam@binaryelements.com, or reply to any BE Hub email. A person answers.