add new billing page

[alexcasalboni]

Context for why we need this new page: https://www.growthunhinged.com/p/ai-pricing-visibility-data

TL;DR: Our docs have no billing content. Buyers increasingly ask AI assistants what Unleash costs, and with nothing published, the answers get assembled from Reddit, Vendr, and competitor comparison pages instead. Competitors are currently the top result for "Unleash pricing" and are making claims we've never responded to.

The only risk I see is that we need to keep this page updated if/when the pricing model changes. But that doesn't happen too often :)

Before merging, I'd suggest we get an in-depth review from leadership.

[github-actions]

🌿 Preview your docs: https://unleash-preview-new-billing-page.docs.buildwithfern.com

Here are the markdown pages you've updated:

• support/billing

[Copilot]

🟡 Changes recommended

The new page contains internal contradictions (seat minimums) and publishes specific quantitative claims that are explicitly marked as unverified/possibly unapproved.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds a new “Plans and billing” support page to explain Unleash pricing/billing concepts (seats, API traffic allowances/overages, retention, add-ons, self-hosted considerations) and wires it into the Fern navigation under “Support and community”.

Changes:

• Introduce a new billing documentation page with tables and FAQs covering plan-level billing details.
• Add the new page to fern/docs.yml so it appears in the Support navigation.

File summaries

File	Description
fern/pages/support/billing.mdx	New billing/pricing explainer page with plan overview, metering details, retention, add-ons, and FAQs.
fern/docs.yml	Adds “Plans and billing” to the Support and community navigation.

Review details

Suppressed comments (3)

fern/pages/support/billing.mdx:133

• This section publishes specific self-hosting total-cost figures while the embedded TODO notes they may not yet be approved for public docs. Consider removing the specific numbers (and the TODO) until the figures are cleared, and keep the guidance qualitative.

Self-hosting removes the Unleash Cloud API traffic allowance, because traffic goes to your own servers. It does not remove the cost of running the service. Operating a highly available Unleash installation to a 99.99% target typically costs \$50,000 to \$200,000 per year in infrastructure and engineering time, and each additional Edge location adds roughly $15,000 per year. Compare that against the per-seat cost of Unleash Cloud when choosing a deployment model.

{/* TODO: Verify these TCO figures are approved for public documentation. They are in the
    internal messaging guide (facts.md) but this would be their first appearance in public docs.
    They are genuinely useful for the build-vs-buy comparison, so worth clearing rather than

fern/pages/support/billing.mdx:37

• This paragraph says Enterprise bills on only two dimensions, but the same page later describes Enterprise add-ons and support tiers priced separately. Consider rewording to cover all paid plans and clarify that seats and API traffic are the only usage-metered dimensions, while add-ons/support can add fixed fees.

Unleash Enterprise bills on two dimensions only: **seats** and, on Unleash Cloud, **API traffic above the included allowance**. Nothing else is metered.

fern/pages/support/billing.mdx:71

• This worked example includes specific request-volume numbers while the adjacent TODO indicates the billable-unit assumptions aren’t confirmed yet. To avoid publishing potentially incorrect calculations, consider replacing this with a generic estimation formula until finance/product confirms what counts toward the allowance.

**Worked example.** 200 backend SDK instances polling at the 15-second default make 4 requests per minute each, or about 173,000 requests per instance per month. Across 200 instances that is approximately 34.6 million requests per month, within the included 53 million allowance. Doubling the poll interval to 30 seconds halves it.

{/* TODO: Confirm the billable unit before publishing the worked example. Specifically:
      - Do metrics posts (POST /api/client/metrics) count toward the allowance?
      - Does traffic between Unleash Edge and the upstream server count, or only client-to-Edge?

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[alexcasalboni]

I am not sure about these doubts. I think we need to run it through Seb or Nick.

[afronski]

+1 for asking CS, but I remember to almost always answer 1st and 3rd on a few calls with prospects.

[alexcasalboni]

Same here - we need explicit confirmation from engineering/CS.

[alexcasalboni]

I'd tend to trust the doc page here :) Let's verify and then update the /pricing page accordingly.

[alexcasalboni]

Are we open to publishing this kind of info? If not, we can just say that it's quoted per contract.

[ivarconr]

Its quoted per customer, as it it usually a tailor-fit for their exact needs. Its only top 10% of customers that require these, and it normally comes up after they have validated that unleash is a fit for them.

[melindafekete]

Please merge with the availability page and ensure that all links in the docs that reference plans like OSS and Enterprise link to the right place. Also a good time to remove Pro from the availability page

[melindafekete]

Add impact metrics

[ivarconr]

should we also have an example showing the total number of connected backend instances possible with 53Million monthly request and call out that other platforms count these as "service connections"? Competitive platforms usually charge in the thousands per month for those numbers.

[alexcasalboni]

Done!

[afronski]

Minor remarks from my end.

[afronski]

After reviewing this table in the preview, I find it confusing that it includes both cloud-based and self-hosting perspectives.

IMHO, if we split earlier, since the decision about cloud vs. self-hosting is made earlier anyway, it will be simpler to understand.

[afronski]

+1 for asking CS, but I remember to almost always answer 1st and 3rd on a few calls with prospects.