Instances

An instance is a single game server: one template, one node, one Docker container. If you run a survival world and a creative world, that's two instances, even if they share a node.

Anatomy of an instance

Every instance is created from a template and carries:

• Configuration: the values you set in the template's settings form, stored as the container's environment.
• A deployed snapshot: the exact template version and configuration that is currently running. Editing settings doesn't touch the live server until you re-deploy.
• A container: created and managed by the daemon on the instance's node.

Lifecycle

create ──▶ deploy ──▶ running ⇄ stopped ──▶ delete
              ▲                    │
              └── re-deploy ◀──────┘

• Deploy pulls the image, creates the container from the current configuration and starts it.
• Start / stop / restart operate on the existing container without changing configuration.
• Re-deploy replaces the container to apply new settings or a new template version. Data in the server's volumes survives; the container itself is disposable.
• Delete removes the container and the instance. Backups outlive the instance.

The panel shows live status transitions as they happen. No refreshing.

Working with an instance

Each instance page gives you tabs for day-to-day operations:

Plus Environment for reviewing and overriding configuration, and Settings for renaming, version changes and lifecycle actions.

Permissions

Everything above is permission-gated per instance; a user might see the console on one instance and only the status badge on another. See access control.