VMs

A VM, also called an instance, is an isolated Linux virtual machine where your apps run. It has its own guest operating system, filesystem, and root access. The available plans use shared vCPUs, not dedicated physical cores.

​

What’s on a VM

Suji prepares the selected supported Linux image with Docker, Docker Compose, the guest management agent, and the tunnel connection used for supported web apps. The guest agent powers dashboard operations such as Terminal, Files, Logs, and Metrics. You manage packages, guest OS updates, and software you install. Keep the Suji management components available if you want dashboard operations to continue working.

​

Sizes

Monthly estimates assume 730 hours. Compute is billed by the minute at the hourly rate, with a one-hour minimum per VM. Optional backups, retained storage, and traffic overage are separate charges. See Plans & pricing. Stopping a VM does not reduce its hourly charge. Delete it to stop compute charges. Retained snapshots and volumes remain billable until deleted. Resizing requires an eligible VM state and an available target size. It stops and restarts the VM. Disk size cannot shrink, so a smaller plan must accommodate the current disk. See Resize.

​

Regions

The configured regions are in Germany and Finland. The creation form shows the locations currently available for provisioning. Region selection applies to the VM; moving a workload requires a new VM and a suitable restore or migration process.

​

Network

The VM receives public addressing. Supported exposed web apps receive a *.suji.fr HTTPS URL. Other services use their configured ports and the VM’s public IP. Review inbound rules in the Firewall tab. Network-level restrictions can apply, including SMTP restrictions; do not assume every outbound port is available. See Network.

​

Storage

The system disk persists across ordinary restarts. Restoring a snapshot replaces disk contents with the captured state; it does not preserve later changes. Marketplace templates define how application data is stored. Named Docker volumes and bind mounts are on the VM unless you explicitly configure external storage. Application data retention during upgrades and uninstall depends on the template and selected options. System-disk snapshots exclude attached block-storage volumes. Back up those volumes separately. See Snapshots & backups and Volumes.

​

Access

The VM terminal provides root access. App terminal behavior depends on the container and its available shell. See Terminal for details.

​

Lifecycle

• Provisioning: asynchronous; follow the status and progress in the dashboard.
• Stop / Start / Restart: interrupt running workloads. Stop preserves disk allocation and does not pause compute billing.
• Restore: applies a snapshot to an eligible target; review the overwrite and downtime warnings first.
• Delete: removes the VM and its system disk. Managed backups tied to it are removed too. Separate snapshots and block volumes have their own deletion and retention rules.

​

Next