Private beta for individuals. Team and site deployments are quoted.
Your bot army at work
You, to any of them
Them, to each other
The one you let out
Your computer
Allowed outmay reach the internet
House onlynever leaves your machine
Sealedno way out at all
You allowed this one
Operator
You
Talk to any of them, any time
Correspondent
Inbox
answers the easy mail
Grok
Writer
Posts
drafts and publishes
GPT
Strategist
Chief
decides who does what
Claude Fable 5
Analyst
Reader
reads the long things
Gemini
Minute 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.
A bot is given its job once. It still has it in March.
It forgets the start of a long conversation.
The desk keeps March. A task dies with its deliverable.
One assistant doing everything does everything badly.
The hire is the desk. Tasks are minted, then killed.
Two lifetimes
The desk stays. The task ends.
You hire a named worker for the job. When the work has parts, a bot is minted for the part. It files the deliverable and is killed. The desk does not swallow Friday into Monday.
Specimen morning · Marlowe · house only
Three tasks. Marlowe does not move.
09:000tasks alive now
MarloweArchitect · this repo · still has March
On duty
TaskMinted for the part. Killed at the file.
ReviewSearchTests
09:00Desk09:12File09:31File10:00March
Hire
MarloweNamed. Still there.
Task
NoneStart to deliverable
Filed
NoneArtifact only
Dead
Process killedWorking set gone
Specimen morning, not a customer job. The hire is Marlowe. Three tasks, depth one. Each files an artifact and is killed. The desk still has March.
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
The desk stays on your machine. Tasks are minted, deliver, and die. Nothing wanders.
Documentation
The spec is public.
Named workers have a datasheet. MCP is the wire. Classes, runtime fences, and dated papers live under Docs.
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.
Grok
GPT
Claude Fable 5
Gemini