Payload pricing teardown
https://payloadcms.com/pricingThis isn't a traditional pricing page — it's an open-source deployment hub with one real price point (Free/self-hosted) and three non-priced paths (Vercel template, Cloudflare template, Enterprise). There are no visible prices for hosting or enterprise, pushing everything beyond the free tier into a 'Talk to Sales' / 'Get a Demo' flow, which is deliberate given Payload's open-source, developer-first positioning post-Figma acquisition.
Tier structure
Free (self-hosted)
Vercel template
Cloudflare template
Enterprise
Contact Sales
Value metric
flat/free self-hosting vs. custom enterprise contract (no usage-based or seat pricing visible)
How limits scale
Escalation logic
The free tier is genuinely full-featured open-source self-hosting; the Vercel and Cloudflare 'tiers' are really deployment templates rather than pricing tiers, and Enterprise is a gated, price-hidden jump to dedicated support and advanced features like SSO and visual editing.
Psychological anchors
- Free tier as entry anchor — Open-source, MIT-licensed, 'free forever' self-hosting is the only concrete price on the page, anchoring everything else as an upsell.
- Enterprise as high-end anchor — Enterprise tier lists premium features (SSO, white-labeled email, roadmap influence) with no price, implying custom/high-cost deals and funneling to 'Get a Demo'.
- Recent acquisition trust signal — 'Payload is now part of Figma!' banner and GitHub star count (43.8k) used as credibility anchors rather than pricing anchors.
What this page is optimizing for
The page optimizes for developer self-serve adoption (via free open-source install and one-click templates) at the top of funnel, then funnels serious/paying use cases into enterprise lead-gen via 'Talk to Sales' and 'Get a Demo' — there's no self-serve paid tier in between.
Red flags
- No visible pricing for anything beyond the free self-hosted tier — Vercel, Cloudflare, and Enterprise all hide cost.
- Tier structure doesn't follow good-better-best pricing escalation; it's organized by deployment method, not by value/feature tiers with prices.
- No annual/monthly toggle or discount since there's no recurring paid plan shown.
- The 'Enterprise' tier bundles vague value props (roadmap influence, white-labeled email) without quantifiable limits or starting price, making it hard to self-qualify.
- Ambiguity introduced by the Figma acquisition ('not ready to share specifics yet') creates uncertainty about future pricing/roadmap.
Best-practices scorecard
What works · 2
- FAQ or objection handling — FAQ covers open-source status, self-hosting flexibility, and the Figma acquisition, addressing key buyer concerns.
- Trust signals present — GitHub star count (43.8k), Figma acquisition mention, and named enterprise customers (Microsoft, ASICS, Blue Origin) build credibility.
Half measures · 3
- Visible prices — Only the Free tier has an explicit price ($0); Vercel, Cloudflare, and Enterprise show no cost.
- Tier differences are scannable — Feature lists per card are readable, but differences between Vercel/Cloudflare and the actual value proposition of Enterprise vs free are not clearly contrasted.
- Clear CTAs per tier — Each card has a CTA (Deploy, Get a Demo) but they route to setup instructions or sales contact rather than transparent next steps with pricing.
What's missing · 3
- Clear recommended tier — No highlighted or 'most popular' plan; all four options are presented as parallel paths.
- Annual discount offered — No billing toggle or discount exists since there's no metered/subscription pricing shown.
- Value metric matches usage — Tiers are split by deployment target (Vercel/Cloudflare) rather than usage or feature scaling, so it's unclear what drives cost.