Payload CMS pricing in 2026 is a trick question. The software itself is MIT-licensed — you download it, run it, own it, never pay a license fee. What you actually pay for is the infrastructure you run it on: a server or serverless platform, a database, and somewhere to store uploaded files. This post breaks that down by project size with numbers from Railway, Fly.io, Vercel, Neon, and AWS S3's pricing pages at the time of writing — check each vendor before you budget, as several of them changed their pricing models recently.
What Payload CMS actually costs (spoiler: $0 for the software)
Payload Cloud, Payload's own hosting service, paused new project deployments after Payload joined Figma in 2025 (existing Cloud projects keep running). Payload 3.x installs into a Next.js app, so your CMS and your front-end live in the same codebase and deploy to the same host. That's architecturally elegant, but it also means you're responsible for every layer of the stack. Unlike Strapi Cloud or Sanity's hosted backend, there is currently no first-party managed platform for a new Payload project that you can point a credit card at and call done.
The five cost buckets to plan for:
- Compute — where the Next.js + Payload app runs
- Database — Postgres, SQLite, or MongoDB (Payload 3.x has official adapters for each)
- File storage — uploaded media, since the local disk on a serverless host is ephemeral
- Bandwidth / CDN — egress for media delivery
- Email — transactional email for Payload's auth flows (optional but usually needed)
Hosting options compared
Vercel is the natural choice for a Next.js project. Payload 3.x runs inside Next.js route handlers, so it deploys without any special config. The Pro plan ($20/month per developer seat, with a $20 usage credit) is effectively mandatory for client work, because Vercel's Hobby plan is for personal, non-commercial use only. Edge function restrictions mean your Payload API must live in Node.js runtime, not Edge; keep that in mind.
Railway is the most straightforward option if you want a persistent Node.js process rather than serverless. Railway bills per resource, per second (about $10 per GB of RAM and $20 per vCPU per month), so a small always-on service typically runs around $5–15/month depending on RAM. Railway also offers managed Postgres, which simplifies the stack. The Hobby plan is $5/month including $5 of usage; Pro is $20/month per workspace (seats included) with $20 of usage.
Fly.io is worth considering for teams who want full control. Fly no longer offers a free allowance for new organizations; a shared-cpu-1x machine running continuously costs about $2/month with 256 MB RAM and about $6.70/month with 1 GB (US region). You'd run Postgres as a separate Fly app or use Neon.
Render sits between Railway and Fly. Its free tier spins services down when idle and free Postgres databases expire after 30 days, so production needs a paid instance and paid Postgres — check Render's pricing page for current instance prices.
Database costs
Postgres is the sensible default for most new Payload 3.x projects:
- Neon (serverless Postgres) has a generous free tier (1 GB storage and 100 CU-hours of compute per project per month, 10 branches) that covers a staging environment or a small production site. The Launch plan is usage-based with no monthly minimum ($0.106 per CU-hour of compute, $0.35/GB-month storage) — a small, mostly idle production database that scales to zero stays cheap.
- Railway Postgres is billed like any Railway service — RAM, CPU, and $0.15/GB-month volume storage — so a small database typically runs around $5–10/month.
- Supabase free tier is 500 MB; Pro is $25/month. Reasonable alternative if you want the dashboard.
- MongoDB Atlas still works with Payload 3.x via the official MongoDB adapter. Free M0 cluster is 512 MB; M10 (the first dedicated cluster) is roughly $57/month — a significant step up.
For most Payload projects in 2026, Neon (free or usage-based Launch) or Railway Postgres is the right call.
File storage
Payload's local disk storage is not usable on Vercel (ephemeral filesystem) and unreliable on most containerised hosts after deploys. You need an external storage adapter:
- AWS S3 is the default recommendation. A typical editorial site with 50 GB of images and video thumbnails costs about $1.15/month in storage (S3 Standard, ~$0.023/GB) plus roughly $9 per 100 GB of egress beyond AWS's monthly free data-transfer allowance. For low-traffic sites the total is under $5/month.
- Cloudflare R2 has zero egress fees. Storage is $0.015/GB/month. For media-heavy sites this is meaningfully cheaper than S3 — 100 GB of assets costs $1.50/month, full stop.
- Uploadthing bundles storage and delivery with a simpler API. Free tier is 2 GB; the $10/month plan is 100 GB. Worth considering for small agencies that don't want to manage bucket policies.
Cost table by project size
| Project size | Compute | Database | Storage | Monthly total |
|---|---|---|---|---|
| Hobby / staging | Railway Hobby $5 or a small Fly machine ~$2–7 | Neon free | S3 ~$1 | $6–$10 |
| Small production (< 10k visits/month) | Vercel Pro $20 or Railway $10 | Neon Launch (usage) ~$5–20 | R2 $2 | $30–$45 |
| Medium (10k–100k visits/month) | Vercel Pro $20 + usage or 2× Fly 1 GB ~$14 | Neon Launch (usage) ~$10–25 | R2 $5–10 | $45–$65 |
| Agency multi-tenant (multiple clients) | Dedicated VM $40–80 | Neon Scale (usage) or self-hosted PG | R2 $15–30 | $120–$180 |
| High-traffic / enterprise | Fly.io performance or AWS ECS $100–200+ | RDS Postgres $100+ | S3 + CloudFront $30+ | $230+ |
These are rough, infrastructure-only estimates — usage-based database and compute bills depend heavily on traffic. Add Vercel developer seats ($20/seat/month) if you're on Vercel Pro, and any third-party email service such as SendGrid or Resend (check their current plans).
What actually triggers a cost increase
Serverless cold starts on Vercel can push you into higher function execution tiers if your Payload API routes aren't cached intelligently. Profile your route handler usage before assuming the free tier is sufficient.
Media volume is the most unpredictable line item. A client who uploads 4K source images without size limits will blow through an S3 budget. Set maxFileSize in your Payload upload config and enforce image optimisation at the adapter level.
Database connection limits become a problem the moment serverless functions, a staging environment, preview branches, and a local dev machine all hit the same database. Postgres max_connections scales with compute size (about 100 on Neon's smallest compute), so use Neon's pooled connection string (PgBouncer, up to 10,000 client connections) rather than paying for a bigger compute just for connections.
Postgres vs MongoDB on cost: if you're starting fresh in 2026, use Postgres. MongoDB Atlas's first dedicated tier (roughly $57/month) is hard to justify when Neon's usage-based Postgres often costs a fraction of that for a small site.
Realistic monthly totals
For a freelance or agency project with one client site, a realistic 2026 Payload CMS infrastructure budget is:
- Bare minimum (hobby/staging): $6–10/month
- Small business production site: $40–50/month
- Content-heavy or multi-environment: $80–120/month
Compared to a managed headless CMS: Sanity's Growth plan is $15 per seat/month; Contentful's first paid tier (Lite) has been listed at around $300/month, though third-party trackers report it changed during 2026 — check Contentful's pricing page. Payload's infrastructure floor is competitive — but you're owning ops, updates, and backups yourself. That's a real cost even if it doesn't show up on a hosting invoice.
Top comments (0)