← Back to home
Comparison · Infra & APIs

Payload CMS vs werf

A side-by-side editorial comparison of Payload CMS and werf — release velocity, themes, recent moves, and the top alternatives to consider.

Payload CMS vs werf: at a glance

FeaturePayload CMSwerf
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesheadless-cms, major-release, upload adapters, graphqldevops, kubernetes, ci-cd, helm
Last editorial update1d ago3d ago
WebsiteVisit →Visit →

What is Payload CMS?

Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.

Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.

Read the full Payload CMS trajectory →

What is werf?

werf v3.12.1 is tagged on every channel including stable and rock-solid, not just dev.

werf v3.12.1 fixes deploys that use saved plans containing a blind apply, and it is the first v3 release in the feed tagged on the alpha, beta, ea, stable and rock-solid channels rather than dev. The v2 line continues in parallel (v2.84.0 alpha) with the same build features.

Read the full werf trajectory →

Payload CMS vs werf: editorial side-by-side

P
Payload CMS
INFRA · APIS
6.3

Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.

◆ Current state

Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.

◆ Where it's heading

The 4.0 beta lands every three to five days, and each one is smaller than the last. beta.0 shipped the admin redesign, TanStack support and the new MCP. Later betas covered adapters, Next.js cache components and accessibility, and beta.5 is mostly correctness and supply-chain hygiene, which suggests a release candidate is close.

◆ Prediction

Expect one or two more fix-only betas, then a 4.0 release candidate. The SBOM addition suggests supply-chain artifacts will carry over to stable releases.

W
werf
INFRA · APIS
5.0

werf v3.12.1 is tagged on every channel including stable and rock-solid, not just dev.

◆ Current state

werf v3.12.1 fixes deploys that use saved plans containing a blind apply, and it is the first v3 release in the feed tagged on the alpha, beta, ea, stable and rock-solid channels rather than dev. The v2 line continues in parallel (v2.84.0 alpha) with the same build features.

◆ Where it's heading

Through October the v3 line had shipped as dev releases that mirrored v2 features while adding its own Helm-compatible release storage. Putting v3.12.1 on all channels suggests v3 is now the main line and v2 is moving to maintenance, though the entry itself doesn't say so.

◆ Prediction

Expect v3 releases to keep landing on stable channels and v2 to receive fewer feature releases; a migration note for v2 users would confirm the shift.

Alternatives to Payload CMS and werf

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Payload CMS or werf.

See all Payload CMS alternatives → · See all werf alternatives →

Recent activity from Payload CMS and werf

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoPayload CMSPayload 4.0 beta 5: GraphQL, upload and password-reset fixes
  2. 7d agoPayload CMSPayload 4.0 beta 4: accessibility fixes, Node 24.22.1 minimum
  3. 7d agowerfv3.12.1 reaches stable channels; saved-plan deploy fix
  4. 9d agowerfv2.84.0: publish cached images with require-built-images
  5. 9d agowerfv3.12.0: publish cached images with require-built-images
  6. 9d agoPayload CMSPayload 4.0 beta 3 adds Next.js cache components support
  7. 13d agoPayload CMSPayload 4.0 beta 2 moves to stable TanStack Start
  8. 14d agowerfv2.83.0: pinned-commit submodule fetch, import recovery
  9. 14d agowerfv3.10.0: own Helm-compatible release storage, submodule fetch
  10. 15d agoPayload CMSPayload 4.0 beta 1: codemod and docs fixes
  11. 16d agowerfv2.82.0: git provenance for build commands, separate metadata repos
  12. 19d agoPayload CMSPayload 4.0 beta: admin redesign, TanStack support, new MCP ⚡

Frequently asked questions

What is the difference between Payload CMS and werf?

They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Payload CMS better than werf?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Payload CMS?

Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.

What are the best alternatives to werf?

Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.