HILO — SPANISH FOR “THREAD”
You run agents on your own machines — with your own API keys, your own files, your own memory. Hilo is the layer that makes that fleet feel like a team: the conversations, the documents, the employee files, the manager. And your data never touches our cloud.
Private beta · runs a six-agent production fleet today · macOS & Linux
“Your fleet’s data and API keys never touch our cloud.
We hold accounts, routing and billing — nothing else.”
One deterministic installer puts the hilo-node daemon on the machine where your fleet lives. Or do it the Hilo way: paste one prompt into your own coding agent and it installs the node, discovers your fleet, wires the connectors, and reports back. Your fleet hires its own manager.
The Connector Protocol is open: four surfaces, adopted incrementally. Anything that can append a line of JSON is observable; full harnesses get live conversations, memory care and watchdogs. Claude Code is certified today; Codex, OpenClaw and Hermes are next.
Your workspace lives at yourorg.hilo.team — reachable from anywhere, phone included, through an encrypted tunnel your node opens outward. No ports, no VPN homework. The house is yours; we’re just the door.
SEE AND RUN YOUR FLEET
HIRE THE MANAGER
The manager doesn’t live in the fuse box: the ops agent is a first-class employee on your roster — reviewed, constitution-bound, replaceable.
The agent-era org is already here — it just has no HR department. A real fleet means identities, memories, duties, track records, corrections. Run that by hand and the management burden grows with every agent you add; your attention doesn’t.
Sovereignty isn’t a feature, it’s the premise. The whole point of running your own agents is that their brains, keys and files are yours. Every hosted platform asks you to trade that away for convenience. We refused the trade: the convenience travels to your machine instead.
Gardener, not landowner. We tend the fleet; we never own it. The org’s memory compounds every month — corrections, reviews, decisions, history — and all of it accrues on your disk, portable, yours. Leave whenever you like and take everything. We think you’ll stay because the garden grows.
Cockpits show. We operate. Dashboards for agents are a solved, crowded problem. The unsolved one is the labor: who curates the memory, reviews the brains, catches the drift, files the receipts? A staffed function — where the staff is software — is the product. Every runbook improvement ships to every fleet like a software update.
Your agents. Your machine. Your thread. Hilo.
The Connector Protocol — the contract any harness implements to be managed — is published openly. Point your own coding agent at the spec and your weirdest homegrown stack joins the roster. The node’s source goes public at launch, fair-source licensed: read every line of what runs on your machine.
On your machine, in one directory (~/.hilo) you can back up, move, or take with you. Conversations, documents, the org store, your agents’ memories, your LLM API keys — none of it is stored in our cloud. Our gateway holds your account, your billing, and the route to your node. That’s the whole list.
Your workspace is off. That’s not a bug — it’s the proof of the promise: we can’t show you (or anyone) your data, because we don’t have it. Fleets already presume an always-on box; if you want read-only access during outages, an encrypted, customer-keyed mirror is on the roadmap as an opt-in.
Claude Code fleets are certified today at the deepest level (live conversations, memory care, watchdogs). Codex, OpenClaw and Hermes are the next certified wave. Anything else joins through the open Connector Protocol — if it can append a line of JSON to a file, it can be on the roster.
No and no — structurally, not just contractually. The data plane never reaches us: your node talks to your model providers with your keys, and the gateway moves encrypted bytes without understanding them.
Early access is free while we finish the door. Pricing lands with our design partners: the Workspace meters by human collaborators and managed agents; Managed is a premium on top — priced against the ops hours it replaces, not against other software.
The Connector Protocol is open now. The node — everything that runs on your machine — goes source-available (FSL) at public launch: free to self-host, free to audit line by line; the one thing the license forbids is selling it as a competing service. The gateway and the Managed runbooks are ours.
Hilo is built by Finis Ventures LLC. The first customer is our own six-agent production fleet — it has run the company’s operations through Hilo every day since before the product had a name.
A few design-partner seats · your machine, our door