55 / 100

Strapi pricing teardown

https://strapi.io/pricing-cloud

The page itself failed to load (a CloudFront 403 error), so no visual or textual pricing content could be verified from the fetch. However, verified pricing data shows Strapi Cloud uses a clean 3-tier flat-rate model (Starter $35, Pro $90, Business $450) with clear feature and infrastructure scaling across tiers.

Tier structure

Starter

$35/mo

Pro

$90/mo

Business

$450/mo

Value metric

flat-rate per tier with usage limits (API requests, storage, environments, bandwidth)

How limits scale

Runtime Sleeps when idle → Always on → Always on
Uptime SLA - → - → 99.9%
API requests / month 100,000 → 1,000,000 → 10,000,000
Asset storage 50 GB → 250 GB → 1,000 GB
Backup frequency - → Weekly → Daily

Escalation logic

Plans escalate from a basic sleep-when-idle hobby tier to always-on production tiers with progressively higher resource caps, faster support, and stronger reliability guarantees (SLA, backups) at the top.

Psychological anchors

  • Featured/recommended tier — Pro is marked as is_featured, positioning it as the go-to plan between a limited Starter and a much pricier Business tier.
  • High-priced tier as anchor — Business at $450/mo (5x Pro) anchors perceived value and pushes mid-market buyers toward Pro.
  • Add-on upsell pricing — Additional environments priced per tier ($60/mo on Pro, $300/mo on Business) create clear expansion revenue paths.
  • No free trial — Absence of a free trial removes a common anchor, likely pushing users to evaluate via self-hosted/open-source Strapi instead.

What this page is optimizing for

This looks optimized for self-serve conversion and expansion revenue — three flat, visibly-priced tiers with a featured mid-tier and metered add-ons (extra environments) that encourage upgrades as usage grows, rather than a pure enterprise contact-sales model.

Red flags

  • The page failed to load (403/CloudFront error), so actual layout, CTAs, toggles, and trust signals could not be verified.
  • No free trial is offered, which may increase friction for self-serve signup on a developer-focused product.
  • Uptime SLA and backup guarantees are absent on Starter and Pro, only appearing at Business — this gap could concern production-minded evaluators on mid tier.
  • Large price jump from Pro ($90) to Business ($450), a 5x increase, which may feel steep without an intermediate step.

Best-practices scorecard

What works · 3

  • Clear recommended tier — Pro is marked as the featured plan per the underlying data, though this couldn't be visually confirmed due to the page error.
  • Visible prices — All three tiers have explicit monthly prices ($35, $90, $450) per verified data, though not confirmed via the actual page render.
  • Value metric matches usage — Pricing scales with real usage drivers (API requests, storage, bandwidth, environments) relevant to a headless CMS/hosting product.

Half measures · 2

  • Annual discount offered — Annual billing option exists but the discount percentage isn't specified in the available data.
  • Tier differences are scannable — Limits data suggests a comparison table exists, but layout/scannability couldn't be verified since the page failed to load.

What's missing · 3

  • FAQ or objection handling — No FAQ content was retrievable from the page due to the load error.
  • Trust signals present — No trust signals (logos, testimonials, security badges) were visible or extractable from the failed page load.
  • Clear CTAs per tier — CTA presence and wording could not be assessed since the actual page content did not load.