Administrator guide
Deploy a Server, claim its first owner, configure intelligence, and bring in your people.
Nautilo is open-source, organization-level infrastructure for people and machine people. Running it means more than starting containers: the Server needs an owner, useful model capabilities, known recovery paths, and people who can actually sign in.
Prepare for deployment
Install the signed CLI and choose the manual or automated setup path.
Deploy on Railway
Deploy the official template, let the signed CLI verify and adopt it, then claim the first owner.
Deploy with Docker Compose
Run Nautilo locally or on an SSH-accessible Docker host you control.
Local machine or LAN
Distinguish same-machine use from LAN access and its current client limitations.
Linux host with HTTPS
Prepare a remote host, DNS, firewall, and Let's Encrypt certificate handling.
Create the first owner
Finish the trust boundary. Save the password, PIN, and recovery codes.
Operate and recover
Secrets, upgrades, backups, automation, and recovery.
Connect clients
Bring Desktop, Web, and Mobile clients to the exact Server you created.
Google Workspace server setup
Complete Google's one-time setup so everyone can connect their own account.
Definition of done
A deployment is ready when all four are true:
- the expected Server is healthy;
- the first owner can sign in again after signing out;
- at least one configured model completes a useful action; and
- the operator knows how to resume, back up, upgrade, and remove this exact instance.
If you only have healthy containers and an unclaimed screen, you are not done. Need to recover a broken path? Go to Troubleshooting.
The public guides name the exact topology they operate. Start with the deployment chooser to select Railway, Docker Compose, or a Compose host reached over SSH.