Skip to main content

VM isolation

Each Suji VM has a separate guest operating system and filesystem. Marketplace apps on the same VM share that VM’s resources. The available plans use shared vCPUs: the physical server and CPU capacity are shared with other VMs. A separate public IP does not make a VM unreachable from the internet or other VMs. Access to exposed services depends on your firewall rules and application authentication.

Network protection

The dashboard and supported Suji web-app URLs use HTTPS. Suji’s management connection to the guest agent uses HTTPS with a per-VM pinned server certificate and token authentication. Services reached directly through a public IP use the protocol you configure. HTTPS on a Suji web URL does not encrypt every connection made by your apps. Configure TLS for services that need it. Use the Firewall tab to review inbound access. Suji’s management rules are protected; customer rules, including SSH and app ports, can be adjusted. Network-level restrictions may also apply, including SMTP restrictions. See Network.

Data and credentials

Install fields marked as secrets are encrypted before being stored in Suji’s database. Authorized dashboard actions can reveal supported saved secrets. VM administrators and applications may also access credentials required by running software. Do not treat database secret encryption as a promise of full-disk encryption for VM disks or snapshots. If your workload requires encryption at rest, configure and verify it for that workload, including key management and backups. Suji redacts sensitive fields in platform audit metadata, but applications and commands can still write secrets to their own logs. Avoid putting credentials in logs, support tickets, or public repositories. For an external API key, revoke or rotate it with its issuer as well as updating your app configuration.

Backups

System-disk snapshots for Suji’s EU regions are stored in the EU, separately from the live VM. Attached volumes are not included. Optional managed backups and manual snapshots have different prices and deletion rules; see Snapshots & backups. A backup operation can fail. Verify completed backups and test restoration for important data. Zero-balance recovery snapshots are attempted, not guaranteed; see When your credit runs low.

Account and access

  • Passwords are stored as Argon2 hashes rather than plaintext.
  • Optional TOTP two-factor authentication is available in account settings.
  • Password-reset links expire and are single-use. Password changes invalidate existing sessions and establish a new session for the current browser.
  • Sign-in and sensitive actions have rate limits. Some sensitive actions require re-authentication.
  • VM terminal and file access require authentication and access to the relevant project. Web-terminal sessions have concurrency limits and an idle timeout.

Audit log

The audit log records supported platform events, including user and background-system actions. Events include the resource and available actor/request information; background events do not necessarily have a browser IP or user-agent. Organization owners and admins can view organization events. The organization-wide view restricts ordinary members to their own events; project views are scoped to the selected project. The platform log is not a recording of every command or file change inside a VM.

Responsibilities

You manage the guest OS, installed packages, application settings, data, access permissions, and backup strategy. Keep them updated and review the access you grant to organization and project members. Suji operates its platform, provisioning and management services, and the integration serving supported Suji web-app URLs. Infrastructure operators manage the underlying data centers and physical hosts.

Data location and account closure

VM disks and snapshots for the offered EU regions are stored in the EU. This does not mean every platform processor or third-party app integration processes data exclusively in the EU. Consult the privacy policy for processing and retention details. Account closure has prerequisites shown in the dashboard, including handling resources in organizations you solely own. The account restoration link is valid for 30 days. Restoring an account does not recreate resources you already deleted or restore expired snapshots. Billing-record retention is separate from account access.

Reporting a security issue

Report a suspected vulnerability privately to support@suji.cloud, with the affected feature and reproduction steps. Do not include customer data or active credentials.

Practical precautions

  • Enable two-factor authentication and use a unique password.
  • Restrict SSH and other administrative ports to trusted addresses.
  • Keep your OS and applications updated.
  • Review team access and the audit log periodically.
  • Keep independent backups and test recovery before you need it.