Skip to main content
An app template describes a Compose stack and its configuration form. Public templates live in suji-hq/suji-templates; organizations can also have their own templates. An app install is a deployment of a template on one VPS. An install can be running, stopped or in another lifecycle state. Multiple installs share the VPS’s CPU, memory, disk and networking; a separate install is not a separate VM security boundary.

​
What deployment creates

Suji validates the submitted settings, renders Compose, sends it through the management connection and starts the stack. Each install has its own identifier, such as install_…, used for its Compose project and configuration directory:
The template determines the services and persistent storage. It can declare multiple named volumes, not just one. Exposed web services receive a public HTTPS route; a database, game server or other non-web service needs its supported connection protocol and port. Check the app guide and the connection details in the dashboard. Apps on the VPS can share the suji-net network. Give unrelated workloads separate VPSs when you need a stronger isolation boundary. Multiple installs may also conflict over a fixed public port; they cannot all reserve the same port on one VPS.

​
Status and operations

The dashboard shows installation, running, stopped and transitional states such as starting, stopping, restarting, upgrading and deleting. A running status is not proof that every external integration works: complete the app’s first-run setup and test your workload. Inspect deployment progress and Logs when an operation fails. From an install’s page:
  • Start / Stop / Restart control its containers. Stopping an app does not stop billing for its VPS.
  • Upgrade deploys an available catalogue version after confirmation. Read the release notes and back up before proceeding.
  • Variables → Apply changes saves supported configuration/environment changes and redeploys the app. Plan for an interruption. Customized Compose installs can have Variables editing disabled.
  • Uninstall removes the containers and deletes the install’s named volumes by default. Select Keep data volumes on the VM to retain them for manual recovery.
The Deployment tab may include app-specific Getting started instructions. The Console tab links to the VM tools. Secret visibility and changes depend on your permissions; sealed variables cannot be revealed.

​
Persistent data and backups

Named volumes normally appear on the VPS under a path like:
Use the Files selector or inspect the actual Compose mounts to find the correct data. Newer installs use an app-prefixed Compose project name; older installs may use the install ID, so do not assume the volume prefix. An app may also use an external database or storage service; those are outside its local Docker volumes. Named volumes persist across container restarts and are retained during normal app upgrades. Upstream migrations can still change or corrupt data, so take application-aware backups and test restores. A VPS system-disk snapshot includes local data on that disk, but not attached block-storage volumes or external databases. Keeping volumes during uninstall does not provide automatic restore on reinstall: Suji removes the install record, and recovery uses SSH and the retained Compose files. Deleting the VPS removes local Docker volumes unless you have a usable backup or snapshot. Block-storage volumes are a different resource with their own lifecycle.

​
Versions and sizing

The manifest declares a version, image references and upgrade-policy metadata (automatic, manual or breaking-changes-flagged). These do not guarantee immutable images, a safe migration or a detailed upgrade diff. Use the version and release notes shown by the marketplace for the proposed upgrade; customized deployments need separate review. Templates declare memory estimates and container limits. Estimates are not reserved resources. A container can reach its own limit while the VPS still has spare RAM, and resizing the VPS does not automatically change that limit. Leave room for the OS and all other apps, then monitor real usage.

​
Next

Marketplace guides

App-specific configuration and first-run steps.

VM terminal

Operate the VPS hosting your apps.