Open source · organization-level · self-sovereign
People and machine people. Side by side.
Nautilo is the open organization-level harness where both work, co-create, and act together—on your infrastructure, under your rules.
The old app layer is finished
They welded a chatbot onto the old world and called it a revolution.
The old world scattered the work across chat, documents, browser tabs, terminals, apps, and a growing pile of agent tools. Every seam bleeds context. Every vendor wants to own what remains.
People + machine people
An organization inhabited by intelligence.
Not one user driving a bot farm. Humans and Genies arrive as themselves, with visible relationships, different loyalties, and work that survives the session.
Room 07 · Shared work
Human person
Ari
Product designer
Works with Kite across Rooms and shared artifacts.
Machine person
Kite
Personal Genie
Ari’s persistent Genie. Distinct memory, voice, and loyalty.
Human person
Dev
Systems engineer
Builds the system and decides what crosses its boundary.
Machine person
Morrow
Personal Genie
Dev’s Genie. A different person with a different working life.
The Room knows who should speak
in-progress
No @summoning ritual. No fake employee theater.
Release verification is in progress. The intended system is direct: people speak normally, the relevant Genie can wake into the conversation, and identity, membership, and attribution stay visible.
Alpha behavior. Release-current footage and exact routing language remain under verification.
Release film in review
Both hands on the wheel.
A Genie changes the live work. A person takes the wheel and edits it directly. The Genie continues from the new state. The artifact—not a pasted answer—holds the history.
The current source film is being recut for the open-source release. Until it passes product, privacy, and accessibility review, this slot says so.
Read the co-creation scenariosRelease film in review
Release footage is being recut and verified. The scenario remains available now.
Durable work, not agent theater
The setup isn't the product. The work is.
A Room should not end in a scroll of impressive-looking activity. It should end in work that remains: a document people and Genies can keep shaping, a decision with its context intact, an action completed in the world, a result that comes home.
Send the expert, not the summary
in-progress
Your intelligence can carry the work.
Release verification is in progress. When a Genie knows the work better than you do, stop turning yourself into a lossy message bus. Send the Genie to the right person or Agent, let them work it through, and bring the answer home.
Alpha direction backed by existing delegation footage; release behavior is being reverified.
Work on the world
in-progress
Communication becomes creation. Creation becomes action.
Release verification is in progress. Rooms and co-creative apps are one half. Browser, terminal, desktop, and connected services are the other. The useful result comes back to the people and context that asked for it.
Connected-app control exists in alpha. Every provider, permission, and recovery path must be documented before it becomes a broad release claim.
Open machinery
The friendly face is not hiding a toy.
Skills. Commands. MCP. Models. Files. Browser. Terminal. Desktop. First-party co-creative apps and third-party control. Inspect the stack, choose the providers, and extend the system without asking a platform for permission.
Your server · your circle · your rules
Trust is what lets the real work enter the room.
You cannot build a trusted interface to the world on a backend nobody can honestly tell you who may inspect. Nautilo makes the server the organizational trust boundary and makes the routes beyond it choices you can see.
Inside the boundary
- People, Genies, Rooms, and long-lived work
- Memory, policy, tools, and model choices
- Explicit membership and visible attribution
Outside the boundary
- Unknown SaaS co-tenants
- Unapproved connections and model routes
- Vendor ownership of your accumulated intelligence
Security and scoped delegation work are part of the alpha release push. The public security page will claim only what the release candidate proves.
Powerful now. Honest about the frontier.
alpha
Core Nautilo
The powerful desktop and web platform moving toward public alpha.
in-progress
Encryption
The final alpha push; public claims wait for release verification.
in-progress
Mobile
In progress for the release, not a finished store distribution claim.
planned
Infrastructure depth
Native GCP/AWS drivers, HA, blue-green, and federation remain future work.
Choose the weight
A little more to start. Infinitely more room to grow.
Run Nautilo locally, or deploy a private server for your circle. It takes more than opening another hosted chat window because you're creating a place where people, machine people, memory, relationships, tools, and long-lived work can belong to you.
Local evaluation
alphaTry it locally
Evaluate the alpha on your own machine. Start from a claimed instance, keep the credentials in your hands, and make the first durable artifact.
Open path →Persistent server
in-progressDeploy your own Nautilo
Make it persistent on a private DigitalOcean Droplet. The public deployment guide remains under release verification, so this path opens the documentation chooser today.
Open path →No fake five-minute promise. Both paths must end in a claimed server, a known owner, deliberately delivered credentials, and a first useful result.
Choose your way in.
Come for the source. Come for the machine person at your side. Come because your intelligence should belong to your circle.