Pricing is positioning with a number attached, and for a developer audience it is read before the second paragraph of the homepage. “Contact sales” reads as something to hide; a legible price is a trust signal. This section is about the decision — what is free, what is metered, what a seat buys, where the enterprise door is — and about the page that decision lands on. The website section covers the page’s place in the layout; positioning covers the claim the number has to be consistent with.

The free tier is the motion

For most developer products the free tier or the open-source core is the top of the funnel, and self-serve is the default motion: a developer goes from evaluating to building to paying without talking to anyone, and the moment they should talk to sales is obvious and well-timed rather than forced early. Three things follow.

  • Free is a product decision, not a discount. The tier has to reach real value — a deployed app, a production-shaped workload at small scale — or it is a demo with a signup form. Railway’s accountless deploys (August 2026: build first, claim the project within 60 minutes) are the logical end state: value before identity, let alone before payment. Neon extended it to the agent in September 2026 — Claimable Neon provisions a Postgres project for a coding agent with no account, capped at 100 MB, 1 GB of transfer and 72 hours, for a human to claim later — so the unclaimed tier is now a pricing line written in three numbers, and the caps are the abuse control as much as the offer.
  • Free is a contract. Developers build on it literally, and changing it is a deprecation event with a date, an email and a migration path — developer experience has the benchmark windows and the brownout pattern. A free tier you cannot afford to keep is cheaper to shrink loudly than to keep silently.
  • Free is the audience you are sizing. The hobbyist segment that made free tiers “free marketing” is contracting — the audience section has the population numbers — so cost the tier against the professional developers it converts, not the signups it collects.

Whether the core is open source is the same decision with a licence attached, and it is read as one: the licence, the governance and what stays free for how long are positioning statements with legal force. The repo covers how developers read them.

Seat, meter, or both

The market settled the shape while the guide was being written. Kyle Poyar’s 2026 State of B2B Monetization survey (230 companies, April to May 2026; 43% of them hybrid SaaS-plus-AI products) found hybrid pricing — a base subscription with a metered component on top — the single most common primary model at 37%, ahead of pure per-seat and pure usage. AI credits are the fastest-moving piece of that: 29% of companies already price with them, a further 33% plan to within six to twelve months, and among companies above $50M ARR roughly one in two plan to introduce them this year, after credit models grew 126% in 2025. Developer tools converged earlier and harder. By mid-2026 the AI-assisted feature had one shape from code generation to code review: a per-seat licence plus metered model consumption — Copilot’s seats with draining AI credits, GitHub Code Quality’s $10 per active committer plus usage, CodeRabbit’s seat plus per-file usage billing.

The shape carries three obligations for the page.

  • Publish both parts. The seat is the floor, not the price. A meter the buyer discovers on the invoice is a trust debt you chose.
  • Publish the cap. The runaway-bill fear is what kills usage-based signups, and it has to be answered in the same eyeline as the meter, not in a FAQ. Supabase’s pricing page is the reference implementation: fixed and variable cost separated, the meter linked to a dashboard, and a spend cap on by default. Atlassian’s September 2026 meter expansion is the sequencing to copy: two new meters (automation steps and AI agent resolutions) announced 2026-09-01, admin usage views and limit controls shipped at once, the allowance (400 steps per Jira Standard user a month) and the overage ($0.50 per 1,000 steps) published in the support docs, and the first bill dated 2026-12-03 — the cap a quarter ahead of the meter. Automation steps are not an AI feature, which says the meter has become a billing habit rather than a pass-through of model cost.
  • Publish the number at volume. The buyer’s first question is what this costs at scale; a page that only shows the entry price makes the champion do the arithmetic in a meeting you are not in.

Pure per-seat is the wrong metric when one engineer uses the product all day and another once a month, and pure usage is the wrong metric when the buyer needs a number they can budget. The hybrid won because it answers both, and the honest version of it is the one where the reader can predict the invoice.

The meter’s unit is moving from the token to the outcome. By September 2026 the token had stopped being a price a vendor owns: Vercel’s gateway index put the average price per token down 23.2% in August, the third monthly fall in a row (Vercel’s own traffic, not a panel), and UC Berkeley’s HarnessTax study ran one model through three coding-agent harnesses at $1.540 and $0.441 per resolved task with no quality difference that survived correction across 42 comparisons — so a token meter passes through someone else’s price list, and the harness on top of it moves the bill 71% on its own. The answer arriving is to bill the unit the buyer already counts. Intercom’s Fin charges $0.99 per outcome, with the outcome defined on the pricing page; Atlassian’s September 2026 meters include AI agent resolutions; and Sourcegraph’s Agentic Batch Changes reached GA on 2026-09-16 billed per changeset merged into the codebase, with a rejected diff costing nothing. Two obligations come with the unit. Its definition belongs in the same sentence as the price, because the customer controls it — a team that merges three of ten proposals pays for three while the vendor paid for ten, and the rate has to carry that ratio, which is why the model suits an enterprise contract better than a $20 seat. And the rate has to be public to count as pricing: Sourcegraph’s is not — its pricing page reads “Enterprise, starting at $16K, includes credits for AI features” — which leaves outcome pricing a sales motion described in outcome language until the number appears.

The terms that are now priced

Two things joined the price list in 2026 that used to live in a trust centre.

The training-data policy now has a market rate. Meta’s Muse Code launched in August 2026 with a “contributor” tier roughly 12–21x below list in exchange for training on the user’s prompts and completions — as far as this desk can find, the first time a training-data policy carried a public price. Whatever your policy, it belongs on the pricing page rather than in a FAQ: “we don’t train on your code” is a positioning claim with a number attached, and its absence is read as an answer.

Self-serve enterprise is the other. The measure of “enterprise-ready” is shifting from what your support team covers to how much of the setup a customer can complete alone. Auth0’s August 2026 SafetyCulture case study — a self-serve SSO configuration wizard cut SSO support tickets 60% at a 50% self-completion rate (the second figure stated on a podcast, single-sourced) — puts a public number on what removing the human gate is worth at the bottom of the funnel, not just the top. The enterprise tier is still where SSO, compliance and a contract live; the change is that the developer expects to reach the door without a form.

Where self-serve hands off

The motion has three shapes and most companies run two. Product-led: the free tier converts to a card, and sales exists to expand accounts that are already paying. Sales-assisted: the developer adopts, the buyer signs, and a human appears at the moment the account crosses a threshold — seats, spend, a compliance question — that the product itself detects. Open-source-led: the core is free and the paid product is hosting, support or the features a company needs and a hobbyist does not. The choice decides what the rest of this guide weighs: product-led lives on activation, sales-assisted on the buyer’s door, open-source-led on the repo and community.

The handoff is the part most teams get wrong in one of two directions. Too early, and a developer evaluating on a weekend gets a calendar invite; too late, and an account running you in production has nobody to call. The trigger should be a fact the product already knows — the third seat, the first production deploy, the spend cap being raised — and the first message should offer something the developer wants (a higher limit, an architecture review) rather than a discovery call. First-party usage is the signal nobody else can buy, and measurement covers scoring on it.

The page, briefly

Put a real number on it. Show the seat and the meter, the cap beside the meter, the price at volume, the training-data policy, and one door for the buyer. Date it. Everything else on the page — the comparison table, the FAQ, the logos — is worth less than those six lines being true. Two September 2026 moves show where the number goes next: PlanetScale publishes its price list as a read-only Postgres database an agent can query in SQL, and PostHog put “97% of users pay us $0” under its signup button with no method given — a free tier stated as a statistic works only if the denominator is published, or the skeptic supplies one.