Deploy Your World to a Server Safely

← All guides

The Seven Steps of a Safe Deployment

1. Version and space pre-check.Before deploying, check target-version compatibility and disk space to avoid failing partway through.
2. Create a remote snapshot.Before replacing anything, create a remote snapshot of the current live world as a rollback point.
3. Verify the snapshot is recoverable.Verify that the snapshot you just created really can be restored—this verification is free on your first full-management connection.
4. Upload to an isolated directory.Upload the new world to an isolated directory without touching the running active world.
5. Validate hashes and structure.Validate the uploaded content's hashes and world structure to confirm it is complete and intact.
6. Atomic switchover.Switch the active world to the new version atomically, keeping the switchover window as short as possible.
7. Health check and automatic rollback.Run a server health check; if it fails, automatically roll back to the pre-deploy snapshot and write an incident report.

Start with "monitor only" (free)

Monitor-only needs just the server address and port. It shows online status, version, player count, and latency—it never reads the world directory and has no write access. When you want deploy capabilities, upgrade to full management and explicitly authorize the connection method and world directory—authorization can be revoked at any time.

What happens on failure

If the health check doesn't pass, the deployment automatically rolls back to the pre-deploy snapshot and keeps a full operation log and incident report. As a result, your live world always has a known-good rollback point. Credentials stay in the iOS keychain the entire time and never appear in the interface or logs.

Related: Server FAQ · One-tap server hosting on your phone