72 / 100

StackBlitz pricing teardown

https://stackblitz.com/pricing

StackBlitz's pricing page is clean and well-structured with a classic free-to-enterprise four-tier ladder, a highlighted Teams plan, and visible annual discounts. The page does a solid job of self-serve conversion for individuals and small teams, but the jump from a 1-seat Pro plan to a 10-seat minimum Teams plan creates a notable gap that could lose solo-to-small-team upgraders. Trust signals and FAQ coverage are good, though the value metric inconsistency (flat per-seat for Pro vs. per-member for Teams) adds minor cognitive friction.

Tier structure

Personal

$0/mo

Pro

$18/mo (annual) / $25/mo

Teams

$55/member/mo (annual) / $60/member/mo

Enterprise & Self-hosted

Contact sales

Value metric

per seat (per member for Teams+)

How limits scale

Users 1 → 1 → Up to 10 → 10+
File uploads Up to 1MB per project → Unlimited → Unlimited → Unlimited
Private GitHub repo access No → No → Yes (org repos) → Yes
Support level Community → Community → Email → Slack, Zoom & email + Dedicated Engineer
SSO / self-hosted No → No → No → Custom SSO + self-hosted/VPC

Escalation logic

Tiers escalate from a free individual plan through a paid individual productivity tier, then jump to a team collaboration plan capped at 10 users, with Enterprise handling 10+ users via sales. Each tier is strictly additive ('Everything in X and:'), making upgrade triggers clear.

Psychological anchors

  • Highlighted recommended plan — The Teams card is visually distinguished with a blue/highlighted background, acting as the decoy anchor and drawing the eye as the intended conversion target.
  • Enterprise high-price anchor — 'Enterprise & Self-hosted' with 'Let's chat' and no public price anchors Teams as the affordable, accessible option by contrast.
  • Annual discount with strikethrough-style callout — Pro shows '$18/month billed annually or $25 billed monthly' and Teams shows '$55 billed annually or $60 billed monthly', surfacing a 28% and ~8% discount respectively to nudge annual commitment.
  • Free tier as entry anchor — The $0 Personal plan with a 'Sign in with GitHub' CTA lowers the barrier to entry and seeds the funnel with users who can later be upgraded.
  • GitHub-native onboarding friction reduction — CTAs use 'Sign in with GitHub' rather than a traditional signup form, reducing friction and leveraging an existing identity layer.
  • Cross-sell tab (WebContainers) — A secondary 'WebContainers' tab and a dedicated section below the plans cross-sell a separate product line without cluttering the main pricing grid.

What this page is optimizing for

The page is primarily optimized for self-serve conversion of individual developers and small teams, evidenced by transparent prices, instant GitHub-based signup CTAs, and a free tier entry point. Enterprise lead-gen is secondary, handled via a single 'Contact sales' CTA with no form friction on the page itself.

Red flags

  • The gap between Pro (1 seat) and Teams (up to 10 seats, per-member pricing) leaves no plan for 2–3 person teams who may balk at paying for 10 seats minimum.
  • The annual discount for Teams (~8%) is significantly weaker than for Pro (~28%), which may undermine the annual upsell at the most important conversion tier.
  • No explicit 'Most Popular' badge on the Teams plan — the blue highlight is subtle and may not be enough to signal social proof on its own.
  • The Teams plan description says 'up to 10 users' but the FAQ clarifies seats are per-member and can be mixed free/paid, creating potential confusion about actual cost.
  • No free trial or money-back guarantee is mentioned, which increases perceived risk for the $55/member/mo Teams commitment.
  • The value metric shifts from flat per-seat (Pro) to per-member/month (Teams), which is technically the same but the labeling inconsistency adds minor cognitive friction.
  • Bolt Personal/Pro/Teams cross-references appear in feature lists without explanation of what 'Bolt' is, which could confuse new visitors unfamiliar with the product ecosystem.

Best-practices scorecard

What works · 5

  • Visible prices — All paid plan prices are publicly visible with both monthly and annual rates shown inline.
  • Annual discount offered — Annual pricing is shown for Pro and Teams with the monthly equivalent called out, though the Teams discount is a modest ~8%.
  • Tier differences are scannable — Each tier uses a clear 'Everything in X and:' additive structure with bullet lists, making differentiation easy to scan.
  • FAQ or objection handling — Seven FAQ items address common objections including GitHub requirements, team setup, and seat management.
  • Clear CTAs per tier — Each tier has a distinct, action-oriented CTA: 'Sign in with GitHub', 'Get started', 'Get started', and 'Contact sales'.

Half measures · 3

  • Clear recommended tier — Teams is visually highlighted in blue but lacks an explicit 'Most Popular' or 'Recommended' badge to reinforce the signal.
  • Value metric matches usage — Per-seat pricing fits a developer tool well, but the 10-user cap on Teams without a mid-tier option creates a mismatch for small growing teams.
  • Trust signals present — GitHub-based login and FAQ mentions of enterprise customers provide implicit trust, but there are no logos, testimonials, or user counts on the pricing page.