Choose a deployment

Choose the smallest path that gives your circle a Server it can actually own. Railway is the shortest hosted route. Docker Compose gives you direct custody on a Linux host you control.

You want to…	Choose	Nautilo owns
Get a hosted Server running with the least infrastructure work	Official Railway template	Template verification, safe adoption, and the receipt-owned day-two lifecycle
Run a persistent Server on infrastructure you control	Docker Compose	The packaged Compose lifecycle and durable local state
Evaluate one machine locally	Local Compose	The local Compose lifecycle
Reach a Server from another computer on one trusted LAN	LAN-only HTTP	A bounded Desktop-client path over SSH-managed Compose, without transport encryption
Operate a Linux host over SSH	Linux Server over SSH	Compose on that host, reached through SSH
Connect to a Server operated elsewhere	`transport=remote`, `lifecycle=external`	The connection only—not deployment
Develop Nautilo itself	Builder documentation	A source-development environment, not a packaged install

Railway and Docker Compose are the documented public paths. Railway's host upgrade transaction creates provider-native backups and an encrypted portable recovery copy, then uses host resume after interruption or when it must continue into a replacement project. There is no independent Railway backup or fresh-project recovery command. DigitalOcean Droplets and other VPS hosts use the same SSH + Compose path. LAN HTTPS, automatic multi-region failover, and native AWS or GCP deployment drivers are not currently supported.

Next: deploy on Railway or deploy with Docker Compose.