People searching for Cloudflare VM usually want a simple answer: can you rent a normal virtual machine from Cloudflare the way you can rent an EC2 instance, DigitalOcean Droplet, or Raff VM?
The answer in 2026 is not exactly.
Cloudflare does not sell a traditional general-purpose virtual machine product where you choose a fixed VM size, boot a persistent Linux or Windows operating system, SSH or RDP into it, and manage it like a conventional cloud server. But Cloudflare's compute platform has expanded significantly: Workers provides serverless edge compute, while Cloudflare Containers can now run container images with full Linux-like environments on the Workers platform.
That makes the modern comparison more nuanced than “Cloudflare cannot run servers.” Cloudflare can now run much broader workloads, but its Containers product still has a different operating model from a traditional VPS or VM.
Cloudflare VM: quick answer
| Question | Answer |
|---|---|
| Does Cloudflare offer traditional virtual machines? | No, not as a general-purpose VM product with a fixed persistent OS instance |
| Can Cloudflare run backend code? | Yes, through Workers and related developer-platform services |
| Can Cloudflare run container images? | Yes. Cloudflare Containers is generally available on the Workers Paid plan |
| Is Cloudflare Containers the same as a VPS? | No. Containers are orchestrated through Workers, start on demand, can scale to zero, and use usage-based resource billing |
| Can you still put Cloudflare in front of a normal VPS? | Yes, and that remains a common architecture |
| Is there a Cloudflare VM price? | No traditional VM price exists; Workers and Containers use their own pricing models |
If you specifically want a normal VPS behind Cloudflare, see our Cloudflare VPS Hosting guide. This page focuses on the Cloudflare VM question and on when Containers or Workers can replace a conventional VM.
Does Cloudflare have virtual machines?
Cloudflare operates a huge global infrastructure fleet internally, but that is different from exposing a public general-purpose VM service to customers.
A conventional cloud VM normally gives you:
- a persistent guest operating system;
- root or administrator access;
- a fixed CPU/RAM/storage shape;
- long-running background services;
- your own package manager and system services;
- predictable server lifecycle under your control;
- SSH for Linux or RDP for Windows;
- attached or local storage options;
- arbitrary software stacks.
Cloudflare's public compute platform is designed differently.
Workers runs application code without provisioning servers. Cloudflare Containers extends that model by allowing applications packaged as container images to run with more CPU, memory, disk, filesystems, runtimes, and Linux-oriented tooling than Workers alone.
So the accurate 2026 answer is:
Cloudflare offers serverless compute and serverless containers, but not a traditional customer-managed VM product.
Cloudflare Containers changed the old “Cloudflare vs VPS” answer
Older comparisons often said Cloudflare could not run Docker containers or full Linux environments. That is now outdated.
Cloudflare Containers became generally available in April 2026. Cloudflare documents support for workloads including:
- applications packaged as container images;
- resource-intensive applications;
- software that needs a full filesystem;
- applications that require a specific runtime;
- CLI tools and broader Linux-like environments;
- images from Docker Hub and supported registries.
Cloudflare also supports SSH access for debugging live containers.
That means some workloads that previously required a VPS can now run on Cloudflare's platform without a traditional VM.
However, Containers are still not simply “Cloudflare VMs.” They are part of the Workers platform and are controlled by Worker code. Container instances start when needed and can go to sleep after inactivity. That usage-driven lifecycle is different from paying for a VM that stays allocated until you shut it down.
Cloudflare Containers vs VM
| Area | Cloudflare Containers | Traditional VM / VPS |
|---|---|---|
| Deployment unit | Container image + Worker integration | Full virtual machine |
| Operating model | Serverless / orchestrated | Customer-managed server |
| OS control | Linux-like container environment | Full guest OS control |
| Windows Server | No traditional Windows VM product | Available from Windows VM providers |
| Lifecycle | Can start on demand and scale to zero | Usually remains running until stopped |
| Billing | Resource usage | Commonly hourly or monthly VM allocation |
| SSH | Supported for live container debugging | Standard administration path on Linux |
| systemd / full machine management | Not a normal VM model | Yes |
| Fixed public VM IP | Not the conventional model | Common |
| Docker image support | Yes | Yes, if you install Docker |
| Multiple arbitrary system services | Possible only within platform constraints | Normal VM use case |
| Best fit | Containerized, elastic application workloads | Full infrastructure control and persistent server workloads |
The question is therefore not “can Cloudflare run Docker?” anymore. It can.
The better question is: does your workload fit Cloudflare's container lifecycle and platform model, or do you need a conventional server that you control directly?
Cloudflare VM pricing: what do you actually pay?
There is no traditional Cloudflare VM pricing table because Cloudflare does not sell fixed general-purpose VM instances.
Cloudflare Containers is available on the Workers Paid plan. As of August 2026, Cloudflare lists a $5/month Workers Paid plan with included monthly container resources:
- 25 GiB-hours of memory;
- 375 vCPU-minutes;
- 200 GB-hours of disk.
Above the included usage, Cloudflare currently bills Containers at usage-based rates for memory, active CPU, and provisioned disk.
Cloudflare's published additional rates are:
| Resource | Additional rate |
|---|---|
| Memory | $0.0000025 per GiB-second |
| CPU | $0.000020 per vCPU-second |
| Disk | $0.00000007 per GB-second |
Cloudflare says container charges begin when an instance receives a request or is manually started and stop after the instance goes to sleep. CPU is billed on active usage rather than simply on provisioned wall-clock time.
That can be attractive for bursty applications. A traditional VM can be easier to predict when the workload is continuously running and you want one fixed monthly infrastructure bill.
Always check Cloudflare's current Containers pricing page before budgeting because platform pricing and included allowances can change.
Workers vs VM
Cloudflare Workers is an even more abstracted compute model than Containers.
Workers is a strong fit when you want:
- API endpoints;
- request/response logic;
- authentication middleware;
- lightweight backend logic;
- edge personalization;
- routing and transformations;
- integrations with Cloudflare storage and developer services;
- globally distributed execution without managing servers.
A traditional VM is better when the application needs:
- direct operating-system administration;
- conventional daemon management;
- custom kernel-level behavior;
- a Windows Server environment;
- software that expects a persistent machine;
- arbitrary networking and long-lived infrastructure services;
- a traditional database server you manage directly;
- server software whose vendor explicitly expects a VM or dedicated host.
Cloudflare Containers fills some of the space between these two models.
Cloudflare Containers vs VPS
A VPS gives you a virtual server. Cloudflare Containers gives you a managed container execution platform.
Choose Cloudflare Containers when:
- your application is already containerized;
- you want instances to scale up and down automatically;
- you do not want to patch and maintain a guest operating system;
- usage is bursty enough that scale-to-zero economics are useful;
- your architecture already uses Workers or other Cloudflare services;
- the application fits Cloudflare's current container limits and lifecycle.
Choose a VPS or VM when:
- you need persistent machine-level control;
- you need Linux system administration as part of the workload;
- you need Windows Server;
- you run several tightly coupled services on one machine;
- you need direct access to system packages, networking, firewalling, or service management;
- a vendor application assumes a conventional server;
- you want one always-on server with fixed resources and straightforward monthly pricing.
Neither model is universally better. They solve different infrastructure problems.
When Cloudflare can replace a VM
Cloudflare can replace a traditional VM when the application maps cleanly to the platform.
Examples include:
- stateless APIs built for Workers;
- edge middleware;
- frontend applications;
- event-driven services;
- containerized web applications that can scale to zero;
- agent or sandbox workloads designed for Cloudflare's runtime;
- workloads that rely heavily on Cloudflare's distributed edge and storage services.
In those cases, avoiding a VM can reduce server maintenance.
When you still need a VM
A conventional VM remains the simpler fit for many workloads.
Examples include:
- Windows Server and RDP workloads;
- IIS-hosted applications that require Windows;
- self-managed PostgreSQL, MySQL, MongoDB, or SQL Server;
- Docker Compose stacks with several persistent services;
- VPN servers;
- control panels;
- legacy business applications;
- monitoring systems that expect machine-level access;
- long-running worker processes with conventional system-service management;
- software that requires root-level host configuration.
A VM is also easier when your team already operates Linux servers and does not need serverless orchestration.
Cloudflare + VM remains a strong architecture
Using Cloudflare does not require replacing your server.
A common production design remains:
Users
↓
Cloudflare DNS / Proxy / CDN / WAF / TLS
↓
Linux or Windows VM
↓
Reverse proxy / application
↓
Database and internal services
Cloudflare handles the public edge while the VM handles the application environment.
This is useful when you want Cloudflare's DNS, CDN, DDoS protection, TLS, caching, and security features but still need a conventional operating system.
For the detailed architecture and setup path, read Cloudflare VPS Hosting: What It Is, Pricing & How It Works.
Do you need both Cloudflare and a VPS?
Often, yes.
Cloudflare and a VPS are not direct substitutes when the workload needs a real server.
The VPS or VM can provide:
- Linux or Windows;
- CPU and RAM reserved for your server;
- Docker;
- Nginx or Caddy;
- application processes;
- databases;
- scheduled jobs;
- private networking;
- full filesystem and OS control.
Cloudflare can provide the public-facing layer:
- DNS;
- reverse proxying;
- CDN;
- TLS;
- DDoS protection;
- WAF and security controls;
- caching;
- edge logic.
This layered model is especially practical for SaaS applications, APIs, dashboards, WordPress, business software, and self-hosted developer tools.
Cloudflare VM vs Raff VM
Raff and Cloudflare are not equivalent products in this comparison.
Cloudflare is primarily providing edge and serverless platform services. Raff VMs are conventional cloud virtual machines.
A Raff VM is a better fit when you need:
- full Linux root access or Windows Server administrator access;
- a persistent VM;
- Docker or Docker Compose under your control;
- system packages and long-running services;
- self-managed databases;
- a predictable VM resource shape;
- direct server-level networking and firewall management.
Cloudflare can still sit in front of that Raff VM.
This means the choice does not have to be Cloudflare or Raff. For many workloads, the architecture is Cloudflare + Raff VM.
Cloudflare VM FAQs
Does Cloudflare offer virtual machines?
Cloudflare does not offer a traditional general-purpose VM product comparable to EC2, Droplets, or a standard VPS. It offers Workers and Cloudflare Containers, which provide different serverless compute models.
Does Cloudflare have a VPS?
Cloudflare does not sell a conventional VPS with a persistent guest operating system and root access. You can use Cloudflare in front of a VPS from another provider.
Can Cloudflare run Docker containers?
Yes. Cloudflare Containers can deploy container images and is generally available on the Workers Paid plan. This is different from renting a traditional VM and installing Docker yourself.
How much does a Cloudflare VM cost?
There is no Cloudflare VM price because Cloudflare does not sell fixed general-purpose VM instances. Containers and Workers use platform-specific pricing instead.
Is Cloudflare Containers cheaper than a VPS?
It depends on utilization. Containers can scale to zero and bill active resources, which can be efficient for bursty workloads. An always-on VPS can be simpler and more predictable for continuously running services.
Can Cloudflare replace AWS EC2?
Cloudflare Workers and Containers can replace EC2 for some application architectures, but they are not drop-in EC2 equivalents. Workloads requiring full VM control, Windows Server, or conventional host administration still need a VM or another infrastructure model.
Can I use Cloudflare with a virtual machine?
Yes. Point your DNS to the VM, proxy supported web traffic through Cloudflare, configure TLS correctly, and keep the VM responsible for the application and operating-system layer.
Conclusion
The old idea that “Cloudflare cannot run containers, so you always need a VPS” is no longer accurate in 2026.
Cloudflare now offers Workers and generally available Containers that can run much broader application workloads without a traditional VM. But Cloudflare still does not sell a conventional general-purpose virtual machine with the same lifecycle and administration model as EC2, a Droplet, or a Raff VM.
Choose Cloudflare-native compute when the application fits its serverless model. Choose a VPS or VM when you need persistent server control, Windows Server, traditional system administration, or software that expects a normal machine.
And for many production applications, use both: Cloudflare at the edge and a VM as the origin.
Sources
- Cloudflare Developers — Cloudflare Containers
- Cloudflare Developers — Cloudflare Containers pricing
- Cloudflare Changelog — Containers and Sandboxes are generally available
- Cloudflare — Plans and pricing
- Sources verified: 2026-08-28
