The anchor
Growth tier as anchor
The Growth tier at approximately $550/mo anchors the page for serious dev-tool companies, making Pro at approximately $150/mo read as the reasonable starting tier. The free OSS tier is the entry; Enterprise sits ready for procurement. Anchoring is conventional; the unusual move is the AI-feature gating that makes upgrading a forward-looking decision rather than a feature-gap fix.
The upgrade trigger
AI feature gating and brand removal
Two upgrade triggers work together: brand removal (the OSS free tier carries Mintlify branding; Pro removes it) for buyers ready to publish to a marketing-grade audience, and AI feature gating (search, chat, advanced AI) for buyers whose users expect LLM-powered docs. The AI trigger is forward-looking — buyers upgrade for capability that becomes table-stakes over the next year, not for a feature they already need.
What works
- • Free OSS tier seeds visible-customer presence across the dev-tool category — every Mintlify-built docs site advertises the platform.
- • Brand removal as Pro trigger aligns with the moment a buyer is ready to publish without third-party branding.
- • AI feature gating creates a forward-looking upgrade trigger — buyers upgrade for capability that becomes expected, not for missing basics.
- • Per-editor pricing on Pro and Growth captures revenue from teams as they scale.
- • Visible customer roster on the marketing surface (Anthropic, Cursor, Resend) borrows authority from category-recognizable companies.
What to copy
- • Gate the forward-looking feature, not the table-stakes one. Buyers upgrade for what they do not yet have but will soon need.
- • Use a free tier with branding to seed visible-customer presence; remove branding at the trigger where the buyer's willingness to pay structurally spikes.
- • Per-editor pricing works when each editor produces value the team consumes; combine with visible customer roster for compounding authority.
What to avoid
- • Do not gate features your buyer already considers table-stakes; the gating reads as nickel-and-diming and lowers trust.
- • Do not free OSS without the bandwidth to support OSS users; bad OSS support poisons the customer-roster flywheel.
- • Do not adopt per-editor pricing if seats do not get clear individual value.
Trial behaviour
Free OSS tier IS the trial for open-source projects. Paid tiers can be trialed via direct conversation; standard self-serve evaluation is mostly via the OSS tier or a sandbox.
Apply this to your own idea
Run your product through the Pricing Fit Calculator to see where your intended price lands against developer documentation benchmarks, then validate whether the market supports it.
Source: unlocksaas.com — indie-saas-teardowns (CC BY 4.0). Pricing page https://mintlify.com/pricing. Verified 2026-05-17.