Nhost pricing teardown
https://nhost.io/pricingNhost's pricing page is well-structured for a developer infrastructure product, offering a clear free-to-paid funnel with a highlighted Pro plan and a detailed feature comparison table. The massive price jump from Pro ($25) to Team ($599) is a significant gap that may cause mid-market customers to churn or stall, and the absence of an annual discount option is a notable missed opportunity. Overall, the page is transparent and thorough but has structural pricing gaps that could hurt conversion at the Team tier.
Tier structure
Starter
$0/mo
Pro
$25/mo
Team
$599/mo
Enterprise
Contact us
Value metric
flat-rate base per tier with usage-based overages (compute, storage, egress, functions)
How limits scale
Escalation logic
Tiers escalate from a free hobbyist plan to a production-ready Pro, then a large jump to a team/compliance-focused plan, with Enterprise for custom infrastructure. Each tier includes a base compute credit and charges overages on database, storage, egress, and functions beyond included limits.
Psychological anchors
- Highlighted recommended plan — Pro is visually highlighted with a 'Most Popular' badge and a distinct blue/colored card treatment in the hero tier section, acting as the decoy anchor.
- Enterprise as price anchor — Enterprise with 'Contact us' and no public price anchors perception of value upward, making Team at $599 feel more accessible by comparison.
- Free tier as entry anchor — Starter at $0 lowers the barrier to entry and creates a natural upgrade path once users hit the 1-project or inactivity limits.
- Charm pricing — Pro is priced at $25 (not $30), and compute is $15/$50 — a mix of charm and round pricing depending on tier.
- Included compute credits framing — Both Pro and Team advertise '$15 in compute credits included,' making the base price feel like it delivers immediate tangible value.
- Pay-as-you-grow messaging — FAQ explicitly states 'We never stop your project and you will be charged for the excess usage. Pay as you grow.' — reduces fear of hitting limits and encourages sign-up.
What this page is optimizing for
The page is primarily optimized for self-serve conversion on the Pro plan, with transparent pricing, instant 'Get Started' CTAs, and a detailed feature comparison table. Enterprise lead-gen is secondary, with a 'Contact us' CTA but no dedicated enterprise landing path or form visible on the page.
Red flags
- The price jump from Pro ($25/mo) to Team ($599/mo) is a 24x increase with no intermediate tier, creating a massive dead zone for growing teams who need collaboration features but can't justify $599.
- No annual billing option is offered anywhere on the page, missing a standard 17-20% discount lever that could improve LTV and reduce churn.
- Pro and Team share identical resource limits (database, storage, egress overages) — the primary Team differentiators are compliance (SOC 2, HIPAA) and support SLAs, which may not justify the price for non-compliance-driven buyers.
- The Starter plan pauses projects after 1 week of inactivity, which is a punishing limit that could frustrate developers and create negative first impressions rather than smooth upgrade pressure.
- Compute pricing is separated into a distinct section below the main tier table, adding cognitive load and making true total cost harder to estimate at a glance.
- No social proof, customer logos, or testimonials are visible on the pricing page to build trust at the point of purchase decision.
Best-practices scorecard
What works · 5
- Clear recommended tier — Pro is visually highlighted with a 'Most Popular' badge and distinct card styling.
- Visible prices — Starter, Pro, and Team all have public prices; only Enterprise requires contact.
- Tier differences are scannable — A detailed comparison table with categorized rows (Database, Auth, Storage, Functions, etc.) makes feature differences easy to scan.
- FAQ or objection handling — An FAQ section addresses plan switching, data export, overage behavior, and project limits — covering key purchase objections.
- Clear CTAs per tier — Each tier has a distinct CTA ('Get Started', 'Contact Us') that is consistently placed in both the hero cards and the comparison table header.
Half measures · 1
- Value metric matches usage — Usage-based overages on compute, storage, and egress are appropriate for infrastructure, but the flat base + overage model makes cost estimation complex for new users.
What's missing · 2
- Annual discount offered — No annual billing toggle or discount is present anywhere on the page.
- Trust signals present — No customer logos, testimonials, review badges, or case studies are visible on the pricing page.