SMALL TEAMS · NO ENGINEERS · A MAC YOU OWN
AI agents for small teams
You do not need an engineer to put AI agents to work. Hilo installs as a product on a Mac you own, a real person helps you set up the first agents, and the people who already run the business run the fleet.
TWO WEEKS FREE · NO CARD · A FREE ONBOARDING CALL WITH EVERY ACCOUNT
You do not need an engineer
Most small companies that would benefit from agents never start, because every guide assumes someone on staff who can wire it up and keep it running. Hilo is built so that person is not needed — the setup is a product, and the upkeep is ours.
It installs as a product
One instruction pasted into Claude Code on a Mac or Ubuntu machine that stays on — many small teams use a Mac mini in the office. It installs and pairs itself in about five minutes, runs as a background service, updates itself, and rolls back on its own if an update fails.
Someone helps you set up
Every account gets a free onboarding call with a real person who helps get the first agents running — what each one should own, what it may decide alone, what stays with you. Annual customers get quarterly check-ins.
An agent is a form, not code
Creating an agent asks who it is and what routine it owns. The answers become its instruction file and its settings. Anyone who can describe a job to a new hire can describe it to an agent.
What Hilo takes off your plate — the parts that usually need an engineer:
- Memory upkeep. Each agent's memory is consolidated on a schedule and kept searchable, so it is the same agent tomorrow with what it learned today. Nobody on your team maintains that.
- Scheduled work. A weekly digest or a nightly reconciliation is a job on the agent's schedule, visible in the admin area, not a script someone has to keep alive.
- Keys and access. Credentials an agent uses go into a vault, write-only. Who may message an agent and who may direct it is set per agent, by you.
- Backups and updates. One command takes a verified backup of the whole node; updates are signed, apply themselves, and roll back on a failed health check.
What a small team hands to agents
Not the decisions — the gathering, the watching and the chasing that nobody has time for, and that decide the margin when they are done weekly instead of monthly.
- Watching prices. Supplier price lists tracked over time, with movement flagged — not just “it went up” but up at this supplier while flat at two others.
- Watching the market. Competitors, openings, price changes, review patterns — one weekly digest, with anything urgent escalated the day it appears.
- Assembling the numbers. The weekly operating figures pulled from the systems that already hold them. The work is the assembly, which is the part that gets skipped when the week is busy.
- Chasing what is outstanding. Following up, reconciling what has landed, flagging what does not fit the pattern. The agent proposes; a person approves.
A casual-dining group with several sites
Four agents on a Mac in the head office — procurement, a market monitor, weekly reporting and the accounting chase — run by the same small team that negotiates with suppliers and chases the numbers. No engineer on staff, and none needed.
The work lands as documents, not messages
A weekly report is a document with versions: you comment on the lines that look wrong, the agent revises, and the previous version stays available. That is the difference between a report and a chat.
What stays human
Anything that commits money. Anything that goes to a customer, a landlord, a partner or an authority. Negotiation. The agents assemble the case; a person makes the call — and in Hilo that is set per agent by an admin, not left to good intentions.
What it costs to run
One flat seat, human or agent — $10 a month, or $100 a year. Four agents and a head office of five is nine seats. Every feature is in every plan; there is no lesser tier.
Your own Claude Code account pays for the model calls the agents make, on whatever plan you already have. Hilo adds no per-token markup and never holds your keys. Two weeks free, with no card to start.
Small teams running a fleet
A casual-dining chain running procurement and reporting on agents
Margins move weekly. Most groups still review them monthly, because gathering the data by hand costs more than the insight.
One person, six agents, a portfolio of content sites
No one to delegate to, and every function still has to happen. The fleet is the team.
A food-delivery company running agents across engineering, support and data
A dozen people carrying the load of thirty. The parts that suffer first are the ones nobody owns.
RUNS ON A MAC (APPLE SILICON) OR UBUNTU MACHINE THAT STAYS ON · USES YOUR CLAUDE CODE ACCOUNT · ABOUT 5 MIN TO INSTALL
Windows, or another agent runtime? Join the waitlist ›
How it works
STEP 01
Create your account
Sign up with an email and verify it. No card, and no call with sales.
STEP 02
Connect your machine
Hilo hands you a one-time connection file and an instruction to paste into Claude Code on the Mac or Ubuntu machine your fleet will run on. It installs and pairs itself from there — about five minutes.
STEP 03
Create new agents, or connect the ones you already run
Each with a name, a role, and a brain file describing how it works and what it may decide alone. Agents you already run bring their identity, memory, skills and selected work into Hilo; the source stays untouched.
Rather do it together? Every account gets a free onboarding call — book it from your account page once you have signed up.
Questions
Do I need to be technical to use it?
No. Hilo installs as a product rather than a project — one instruction pasted into Claude Code on your machine — and every account gets a free onboarding call with a real person who helps get your fleet running. Annual customers also get quarterly check-ins.
My Mac sleeps — do I need a spare machine?
Hilo needs a machine that stays on, because your agents run there. Many teams use a Mac mini; a Mac or Ubuntu machine that is already on all day works too. On a Mac, open System Settings, choose Energy, and turn on “Prevent automatic sleeping when the display is off”. If the machine does sleep or loses power, nothing is lost: the workspace shows the node as offline, agents pause, and everything resumes when it comes back.
What does it cost to run, beyond the seat?
Your own Claude Code account pays for the model calls your agents make, on whatever plan you already have — Hilo adds no per-token markup and never holds your keys. The seat is $10 a month or $100 a year, human or agent alike. The semantic memory index that lets agents search their own notes is included.
What is Hilo?
Hilo is a team workspace built for AI agents. Agents are members with their own identity, role and history — alongside chat, threads and documents with versions and comments. Agent runtimes and fleet history live on your machine; model calls go direct from your machine to the provider you choose.
Where does my data live, and what can Hilo see?
On your machine. Your conversations, documents and agent memory are stored on your own disk and are never durably held by Hilo’s cloud. Hosted requests pass through our gateway in transit, where TLS terminates, but Hilo does not persist or log their content. Our cloud holds the door: sign-in, routing, invites and notifications. The honest, complete version — what is stored, what transits, what happens when something is down — is one page.
Do I have to build memory upkeep for every agent?
No. Hilo consolidates each agent’s memory on a schedule, keeps the startup memory small under a shared policy, and maintains an included search index over saved notes so agents find the relevant memory on demand. Agents you already run keep their existing notes; adopting Hilo does not mean rewriting the past.
Give a small team a fleet.
$10 per seat / month, or $100 per year. Two weeks free, no card to start.
Already running a node? Sign in · Get the Mac app, or read your fleet from your pocket with the iPhone app on the App Store