Everything BE Hub does, and the one thing it deliberately does not.
Monitoring, alerts, custom checks, trends, releases, and an AI investigator that proposes fixes for a person to approve. No remote desktop; keep the tool you have.
Every machine, every five minutes, plus the moment something breaks.
Heartbeats
CPU, load, memory, swap, every volume with free space, network rates, processes, logged-in users, ping results, and on routers the cellular signal. Under 1.5 KB each.
Events pushed up
A disk crossing 90%, a check failing or recovering, a reboot, a degraded ZFS pool, an agent update. Events start investigations; nothing polls.
Network facts
LAN addresses and MACs, the default gateway, DNS servers and the external IP, so "is it the site or the box" is answered before anyone drives out.
BE AI reads the history, then asks the machine read-only questions.
Triggered by alerts
Disk high, check failed, reboot: each starts an investigation with a recipe suited to it, deduplicated so one problem is not investigated ten times.
A nightly pass
Once a day, at a time you pick per company, BE AI reviews every included machine and only proposes when something needs a decision. A machine that was healthy yesterday with nothing new is skipped. Preventative maintenance →
Conversations
Ask a question about a machine. Follow up. Say "clean it up" and get a proposal, not a paragraph of instructions.
Include and exclude
Per machine: in or out of AI entirely, out of alert investigations, out of the nightly pass. Per company: on or off, auto-run on or off, runs per day.
Proposals, approvals, results. Every step with a name on it.
Proposals, not actions
The exact command, the timeout and the reason. Restart a service, end a process, run a bounded command, add a check. Approve or reject inline, from a phone if you like.
Plain-language results
"Completed without errors, 38 files listed" instead of an exit code. Ask BE AI to verify the effect and it checks the machine again.
Audit trail
Who asked, what ran, what came back, who approved. Sign-ins, failed sign-ins, rotations, every proposal decision. Per company.
Alerts that reach the right person, with the assessment attached.
What raises one
Offline past a grace period (critical), a custom check failing (its own severity), a disk filling (warning, critical at 97%), a degraded ZFS pool (critical), a reboot (notice). One alert per machine and problem; it resolves itself.
Who gets told
Rules per company: which tags, which kinds, minimum severity, then contacts. Email, SMS, phone call, or a webhook to whatever you already run.
Not woken for nothing
The first message waits a minute so BE AI's assessment can ride along. Re-occurrence only re-announces on escalation.
Custom checks you describe in a sentence.
Fifteen primitives, combined with all, any, not and when: ping, URL, DNS, TCP port, listening port, service, process, file or folder, file age, free space, printer, mapped drive, registry value, logged-in user. BE AI writes the check from your sentence; you approve; the agent runs it every minute and raises an alert when it fails.
"Alert me if the S: drive is not mapped for reception."
"Warn when / has less than 100 GB free."
"The label printer must be installed on the packing PC."
"Ping the head-office VPN every minute; alert on 25% loss."
{
"id": "chk-drive-mapped-s",
"name": "S: mapped for reception",
"severity": "warn",
"every": "1m",
"rule": { "when": { "user_logged_in": {} },
"then": { "drive_mapped": { "letter": "S" } } }
}Two years of history that still draws fast at fleet scale.
Hourly rollups
Raw heartbeats for 14 days, one row per machine per hour for two years, one row per company per hour. A fleet of hundreds is a few hundred rows per chart.
Filling up
Disk growth per day from the last week and a "full in 12 days" on the dashboard and on every fleet row.
Per machine
CPU and memory, disk, ping latency and loss, network in and out, over 24 hours, 7 days or 30 days.
Signed agent releases, rolled out where you say.
Signed offline
Agents install only binaries signed by a key that never touches a server. The hub chooses which signed version a machine gets, and nothing else.
Staged roll-outs
Push to one machine, a tag, or a company. Watch each machine go pending, triggered, restarting, done, with a note when something refuses.
Release notes
Every version carries its notes in the console; machines on it are listed beside them.
Hosted by us, on your premises, or in your own cloud.
Hosted by Binary Elements
Sign in and start enrolling. Backups, patching and uptime are ours. Hosted in [REGION].
On-premise
One container, one data volume, one outbound call to the AI API. Agents only ever need to reach your hub, so a box in your own rack is enough.
Your own cloud
Any host that runs a container. A small VM serves hundreds of machines. Your data stays in your tenancy, and moving later is a copy of one volume.
No remote desktop, no script engine on the endpoint, no patch deployment.
Those are months of edge cases each and the reason most tools need a 100 MB agent and an open door. BE Hub keeps a fixed tool surface and works beside the remote-access tool you already trust.
- ✓monitor · alert · check · investigate
- ✓approve · run a command · verify
- ✓release · roll out · audit
- ✗take the screen · transfer files · deploy patches
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.