LanguageGB
Security & SSL

Platform security & isolation

Understand how CM Cloud isolates each customer's apps, email, hosting, and VPS workloads.

What this covers

CM Cloud uses different isolation layers depending on the service type — from dedicated VMs to filesystem virtualisation and per-app system users — so one customer's workload cannot read or interfere with another's.

Before you start

No action needed. This article describes platform architecture for informational purposes.

How to do it

  1. App deployment: each app runs as a unique Unix user with a dedicated port and systemd hardening (NoNewPrivileges, PrivateTmp, ProtectSystem=strict). Another customer's app on the same server cannot connect to your app's port, and that port is not open to the internet: visitors reach your app only through our web server.
  2. PocketBase backends: isolated the same way as apps — each runs as its own system user, its pb_data/ folder is readable only by that user, and other customers' apps cannot connect to it.
  3. Shared hosting and WordPress: CageFS kernel-level filesystem virtualisation prevents one user from seeing another's files or processes.
  4. Business email: Mailcow runs each component (SMTP, IMAP, spam filter, webmail) in its own Docker container.
  5. Cloud VPS: each customer receives a dedicated Proxmox VM with no shared kernel — full hardware-level isolation.
  6. Domains: managed via CentralNic with registrant-level access controls; DNS changes require authenticated portal actions.
  7. Location: our servers are in Helsinki, Finland, in the EU.
  8. Read the full security overview at cmcloudhosting.com/security for additional details.

What our team checks

Support reviews isolation concerns, VPS access control questions, email separation enquiries, and requests for security documentation.

Next step

Visit /security for a public overview, or open a support request for specific security questions.

Contact Support