Skip to content
Menu

Fee schedule

Fee schedule

The schedule that applies now.

Version
v1 current
Effective
2026-10-02
Currency
USD
Machine copy
/schedule/v1.json

Bands and lanes

The band is the payer's own consolidated-group revenue for the prior tax year — not a seat count, not a user count, and not anything about the software. The pricing page explains the threshold, the renewal semantics and the founding-cohort terms; this page is the version itself.

Schedule v1 — annual, in USD, before tax, effective from 2026-10-02 · current.

Revenue band Project, Standard repository Project, Utility repository the Pass Paid by
Under $5M $300 $150 $1,500 card
$5M–10M $450 $225 $2,250 card
$10M–50M $700 $350 $3,500 card
$50M–100M $950 $475 $4,750 card
$100M–500M $1,500 $750 $7,500 card
$500M–1B $2,300 $1,000 $11,500 Project by card; the Pass by invoice
$1B–5B $3,400 $1,000 $17,000 Project by card; the Pass by invoice
$5B and over $4,500 $1,000 $22,500 Project by card; the Pass by invoice

Prices are per year and before tax: Paddle, the merchant of record, adds any sales tax or VAT due in the buyer's country. A purchase up to USD 10,000 is paid by card; above that, Paddle sends an invoice, payable by bank transfer within 30 days of its date. A Utility repository is one whose library code, not counting tests, samples, documentation, generated or vendored code, is under 5,000 lines at the registered release; the Association sets the class, and the repository's owner may ask for a recount. Every other repository is Standard. Groups that are large by headcount alone pay in the first band.

The lanes

In this version the buyer chooses a Project or the Pass, both offered in one checkout.

Project

purchasable

Scope: one registered repository

Covers the one registered repository you select, at its Standard or Utility price, and all of your passed-on share is attributed to it.

the Pass

purchasable

Scope: every registered repository

Covers every registered repository. You may name up to fifty registered repositories you use: each is attributed 1% of your passed-on share, and the rest is split equally across all registered repositories active at each month's lock, the named ones included.

What this page does not carry

The deductions between a payer's card and a listed recipient are published as their own document, because every line in them travels with a sentence that qualifies it — an illustrative market rate, a cap stated as a ceiling and not a rate, a line shown at zero with its rule. They are on the money page and on the pricing page, and the machine copy of this schedule points at them rather than restating them without their qualifiers.

Every version, at its own address

  • Schedule v1 — current · effective from 2026-10-02 · you are reading this one

From launch, a version URL published on this domain never changes, and a schedule change never rewrites the version a payer bought under; until launch, version 1 is edited in place. /pricing/schedule and /schedule.json point at whichever version is current, so a reader who wants "the current one" does not have to know the number.