Operator
You
Talk to any of them, any time
On your own machine
One bot for every job.
Not a chat you retrain every morning. A small crew that already knows the work, stays inside your walls, and cannot wander.
Create your bot army. Four starting types. As many as the work needs.
Private beta for individuals. Team and site deployments are quoted.
- You, to any of them
- Them, to each other
- The one you let out
Your computer
Grok
GPT
Claude Fable 5
Gemini
Allowed outmay reach the internet
House onlynever leaves your machine
Sealedno way out at all
You allowed this one
Correspondent
Inbox
answers the easy mail
GrokWriter
Posts
drafts and publishes
GPTStrategist
Chief
decides who does what
Claude Fable 5Analyst
Reader
reads the long things
GeminiMinute taker
Notes
writes up every call
Open weights
Bookkeeper
Numbers
does the sums
Open weights
Archivist
Files
keeps the paperwork
Open weights
Outside
Not yours
Somebody else's bot
Your roster
- Inbox
- Chief
- Reader
- Posts
- Notes
- Numbers
- Files
- Make one
Each bot runs whichever model suits its job, from the register on our security page. The sealed ones and the small jobs run open weights on your own machine instead, so nothing they touch ever reaches anybody's API.
Four ways in
Start with a specialist, not a blank box.
Each one arrives with a job already in mind. You point it at your files. It learns the rest on your machine.
Why one general assistant fails
You shouldn't be the one doing the remembering.
You explain the same thing every morning.
A bot is given its job once. It still has it in March.
It forgets the start of a long conversation.
There is nothing to forget. Each bot carries one job and only that.
One assistant doing everything does everything badly.
Nine bots doing one thing each. They cost the same as one.
How it starts
Give it the job once.
- 01
Pick a starting bot
Architect, Analyst, Scientist, or Operator. Each already knows its job.
- 02
Point it at your files
Your repo, your documents, your CRM. It learns the layout once and keeps it.
- 03
Let it run
It stays on your machine, talks only to the bots you allow, and cannot wander.
Who can reach what
Not every bot gets the same keys.
The Analyst processing your bank statements never touches external networks. The Operator handling communication has no access to sensitive ledgers. Enforced at the runtime, not as a prompt.
- Allowed out
Can reach external tools, public endpoints, and bots outside your boundary.
The Operator routing leads. The Architect pulling upstream repos.
- House only
Coordinates with you and your local bot fleet. Never leaves your machine.
The Analyst synthesizing documents. The Scientist running benchmarks.
- Sealed
Offline execution. No network egress. Hard invariants, not a prompt.
The one with your financial ledgers. The one auditing private IP.
A bot in the sealed band cannot get out by asking another bot to proxy for it.S.O.U.L architecture →Connect via MCP →
Early Access
Join the Genesis Beta.
Tell us the job you want taken off your hands. We deploy the first bots in small batches, on your machine.
01On your hardware
Runs on your computer or private network. Nothing has to leave.
02Four starting types
Architect, Analyst, Scientist, Operator. Then we fit the tools to your stack.
03A person on the other end
Direct access to the people configuring it, not a ticket queue.
Start with one. Scale to a fleet.
Pick the workflow you hate doing twice. For a laptop, join the beta. For a team or a site, send the job and get a number back.