Deploy, build, or administer Nautilo
Start with a claimed instance, then move into the code and operational paths.
The happy path does not begin with a dead, unclaimed server. It begins with an owner, a known login, at least one model key, and a running instance somebody can actually use.
Choose a deployment
Pick local Compose, a Linux Server over SSH, or a connection-only profile.
Run the operator quickstart
End with a claimed Server, known credentials, a model route, and a connected client.
Operate and recover
Inspect the intended instance, upgrade transactionally, and retain a verified recovery path.
Protect the trust boundary
Bound SSH, TLS, credentials, provider access, and recovery material around the Server.
Reuse a claimed development instance
Attach a source checkout without manufacturing a new owner or losing the login.
Build on Nautilo
Enter the developer path, including migration safety and source work.
Need to recover a broken path? Go to Troubleshooting.
How to read release state
- AvailableWorks inside the release scope named by the page.
- AlphaUsable alpha behavior whose interfaces or recovery paths may still change.
- PartialOnly the scope named by the page is supported; adjacent paths are excluded.
- In progressBeing built or reverified. Do not depend on it yet.
- PlannedAn accepted direction without a shipped implementation.
- ExploringA research direction, not a commitment or supported path.
- Not supportedOutside current support. Do not infer a workaround from adjacent features.