01
Volume ownership
Identify every persistent path and back it up independently from the replaceable container image.
Unmanaged container hosting
Docker hosting on an unmanaged VPS
Install Docker Engine and Compose on an unmanaged KVM VPS when you want control over images, networks, volumes, ports, and the Linux host beneath them.
Bitfoo opens for orders soon.
- Platform
- Unmanaged VPS
- Virtualization
- KVM
- Access
- Full root
- Storage
- Persistent NVMe
Linux administration required
Independent server kernel
Docker installed by you
Volumes share plan capacity
Choose by responsibility
Choose the operating model before the container model
Docker makes a workload portable and repeatable. It does not remove the need to operate the server, data, and release path.
Single-host control
Choose a Bitfoo VPS
Use a persistent server for a deliberate single-host Docker or Compose deployment.
- You want direct control over Docker and Linux
- The workload fits a single-host availability model
- Your team owns security, monitoring, and backup operations
Orchestrated platform
Consider a managed container service
Use an orchestrated service when the product requires platform-managed scheduling or multi-node behavior.
- Automatic rescheduling across hosts is required
- The team expects managed load balancing and service discovery
- No one should operate the underlying Linux host
Production foundation
Design for persistence and failure
The most important Docker hosting choices sit outside the Dockerfile: data, exposure, restart behavior, observability, and recovery.
02
Network exposure
Publish only required ports, place public services behind an intentional proxy, and keep private dependencies private.
03
Resource boundaries
Set appropriate container limits and leave capacity for Docker, Linux, logging, backups, and deployment operations.
04
Image lifecycle
Pin and scan trusted images, control registry credentials, and plan how updates and rollbacks change running containers.
Plan comparison
Size for the whole Compose stack
Add the peak memory and storage needs of every service, database, cache, worker, volume, build, and log stream—not only the public web container.
Swipe horizontally to compare every plan.
| Specification | VPS-1 Testing or one light containerized service | VPS-2 A small production Compose stack Recommended starting point | VPS-4 Several services, workers, or a database | VPS-8 Larger multi-service or data-heavy stacks |
|---|---|---|---|---|
| vCPU | 1 | 2 | 4 | 6 |
| RAM | 1GB DDR5 | 2GB DDR5 | 4GB DDR5 | 8GB DDR5 |
| Storage | 25GB NVMe | 50GB NVMe | 100GB NVMe | 200GB NVMe |
| Bandwidth | 1TB | 2TB | 4TB | 6TB |
| IPv4 | 1 | 1 | 1 | 1 |
| Price | Coming soon | Coming soon | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. VPS plans are unmanaged and do not include an automated backup service.
Before deployment
Document what survives a redeploy
A container should be replaceable without losing the state the product depends on.
- 01
Inventory persistent data
Map databases, uploads, certificates, queues, and configuration to named volumes or external stores.
- 02
Separate secrets
Keep credentials out of images and source history, then define how they reach each service at runtime.
- 03
Add health and restart behavior
Make service health visible and avoid restart loops that hide a persistent failure.
- 04
Restore on a clean host
Prove that images, Compose configuration, secrets, and backups can recreate the service after host loss.
Related hosting guidance
Common questions
Is Docker installed automatically?
No. You receive an unmanaged VPS and install Docker Engine, Compose, and any supporting tools using the method appropriate for the selected operating system.
Are Docker volumes backed up automatically?
No automated VPS backup service is included. You must identify persistent volumes, create backups, store them separately, and test restoration.
Can I expose container ports directly?
You can, but public exposure should be deliberate. Publish only required services, apply firewall rules, and use a reverse proxy where it improves TLS and request handling.
Is a single VPS a container orchestrator?
No. Docker or Compose on one VPS remains a single-host deployment. It does not automatically provide multi-node scheduling or host-failure recovery.