Payload Infrastructure Guide
How to Host Payload CMS in 2026
Payload is open source and self-hosting is now the default path. The real question is where to run it.
There are four realistic hosting paths in 2026: Vercel, VPS with Docker, Cloudflare Workers, and managed container platforms like Railway, Render, and Fly.io. Each one fits a different project shape, operating model, and budget.
If you already know you want the Docker path, the self-hosted deploy guide covers the full implementation.
One-click deploy
Vercel
Persistent server
VPS with Docker
Edge-first
Cloudflare Workers
Managed middle ground
Railway / Render / Fly.io
Context: Payload CMS is MIT-licensed and free to self-host. After Figma acquired Payload in June 2025, new Payload Cloud sign-ups were paused. Existing customers kept access, but new projects now need to choose an infrastructure path directly.
Hosting Paths
Four real options, four different trade-offs.
Payload is not hard to deploy. Choosing the wrong runtime model is the harder mistake. The comparison below focuses on runtime fit, cost behavior, and where each option tends to break down.
One-click deploy
Vercel
Fastest path to a live Payload project, especially for solo developers and small marketing sites.
Payload has to initialize inside serverless functions, which means cold starts, connection pool churn, and tighter runtime limits for admin-heavy work.
Typical cost: $20-60/month typical, with usage-based upside.
Best for: Quick launches, light editor usage, teams already committed to Vercel.
Watch out for: Cold starts in the admin, Postgres connection exhaustion, bulk operations hitting timeout ceilings.
Implementation guides
Persistent server
VPS with Docker
The cleanest architectural fit for Payload because the app boots once and behaves like a normal long-running Node.js service.
Docker Compose plus Nginx on Hetzner, DigitalOcean, or EC2 gives predictable runtime behavior, fixed monthly cost, and room for multiple client installs on one box.
Typical cost: Usually EUR7-45/month total depending on database setup.
Best for: Active editors, agencies, jobs and bulk imports, multi-tenant setups.
Watch out for: You own the server setup: Docker, SSL, DNS, backups, updates, and deployment basics.
Implementation guides
Edge-first
Cloudflare Workers
The cheapest path and the newest official one, built on Workers, D1, and R2.
It is compelling for globally distributed, read-heavy content delivery, but the adapter story is newer and GraphQL support is still not fully there in this environment.
Typical cost: $5-10/month typical.
Best for: Cloudflare-native teams, globally distributed traffic, cost-sensitive deployments.
Watch out for: Paid Workers plan required today, D1 adapter is less battle-tested than Postgres, and documentation depth is still catching up.
Managed middle ground
Railway / Render / Fly.io
A persistent server without doing the full VPS setup yourself.
You still get a real long-running Node.js process, but the platform handles SSL, deployment pipelines, and much of the surrounding infrastructure work.
Typical cost: $15-40/month typical including the database.
Best for: Small teams that want persistent server behavior with less ops overhead.
Watch out for: Higher cost per project than a raw VPS and less freedom to pack multiple instances onto one machine.
Cost Comparison
What does it actually cost?
These are realistic small-to-medium production numbers, not free-tier screenshots. Hosting cost is only one part of the decision, but it often determines which path remains sane six months later.
Vercel
$20-60/month
Vercel Pro + Neon Postgres + Blob Storage. Heavy editor usage can push this above $100/month.
VPS with Docker
EUR7-45/month
Server plus optional managed Postgres. Costs stay predictable because billing is not tied to edge request volume.
Cloudflare Workers
$5-10/month
Workers paid plan plus D1 and R2. The lowest-cost option by a wide margin.
Railway / Render / Fly.io
$15-40/month
Container plus managed Postgres. Simple to start, but project cost scales linearly.
Payload Cloud was previously priced at $35/month, but new sign-ups are paused, so it is not a real option for new builds right now.
Decision Framework
Which hosting path fits your project?
The right answer depends less on traffic volume than on editor behavior, operational maturity, and whether you want to own the infrastructure or rent convenience.
Choose Vercel if
- You want the fastest possible launch.
- The site is mostly marketing pages with occasional edits.
- Your team already lives in the Vercel ecosystem.
Choose VPS with Docker if
- Editors use the admin panel daily.
- You need reliable jobs, imports, and media processing.
- You want the best long-term cost and full infrastructure control.
Choose Cloudflare if
- You are already standardized on Cloudflare.
- Global read latency matters more than ecosystem maturity.
- You want the lowest monthly bill and can tolerate a newer path.
Choose Railway, Render, or Fly.io if
- You want a persistent Node.js process without full server admin.
- Docker Compose and Nginx feel like unnecessary overhead for this project.
- A $15-40/month project budget is acceptable.
Payload Cloud
What happened to Payload Cloud?
Figma acquired Payload in June 2025. After the acquisition, the team paused new Payload Cloud sign-ups while building a replacement offering.
Payload itself remains MIT-licensed, open source, and free to self-host. What changed is not the license. What changed is that the managed hosting option is temporarily unavailable for new projects.
In practice, that makes the four options on this page the real deployment choices for anyone starting a new Payload project in 2026.
Related Reading
Implementation guides and next decisions.
If your hosting decision is already clear, these guides take the next step. If it is not clear, they provide the context around pricing, migrations, and broader CMS trade-offs.
Deploy Payload CMS with Next.js 16: Self-Hosted Guide
The step-by-step Docker, Nginx, and Postgres implementation path.
Open guide
Payload Jobs Queue on Vercel: Complete Production Setup
What it takes to make background work reliable on serverless infrastructure.
Open guide
Payload CMS Pricing in 2026
Broader build-cost context beyond hosting alone.
Open guide
Payload CMS Migration Guide
Relevant if hosting is part of a move from WordPress, Contentful, Sanity, or another CMS.
Open guide
FAQ
What is the best hosting option for most Payload CMS projects?
For most production Payload projects with active editors, a VPS with Docker is the best default because it matches Payload’s persistent-server architecture and keeps costs predictable.
Is Payload Cloud still available for new projects?
No. New Payload Cloud sign-ups were paused after Figma acquired Payload in June 2025, so self-hosting is the practical path for new projects in 2026.
Why can Vercel be awkward for Payload CMS?
Because Payload is optimized for a persistent Node.js process. On serverless infrastructure, initialization and connection-pool behavior can become the limiting factor before raw compute does.
What is the cheapest way to host Payload CMS?
Cloudflare Workers is usually the lowest-cost option, commonly around $5-10/month, but it comes with a newer adapter path and some platform-specific limitations.
When should I use Railway, Render, or Fly.io instead of a VPS?
Use them when you want persistent server behavior but do not want to manage Docker Compose, Nginx, SSL, and server maintenance yourself.
Need help choosing the right Payload hosting setup?
Describe the project and I’ll tell you which path fits, what it should cost, and what the first implementation step looks like.
Start the conversation