Runtime and processes
Check self-managed Docker workloads on a VPS where the customer owns container images, compose or orchestration files, volumes, updates, firewall exposure, and backup strategy.
Docker workload VPS
Run your own Docker containers on a Linux VPS. You manage images, updates, networking, volumes and backups; this is not a managed container platform.
This is a self-managed VPS for Docker workloads, not a managed container platform.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check self-managed Docker workloads on a VPS where the customer owns container images, compose or orchestration files, volumes, updates, firewall exposure, and backup strategy.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hosting