Everything behind your selection, in one place. Read the full statements here before confirming your purchase.
By ticking the purchase checkbox, you confirm all three statements below and accept the linked Entitlement terms and the refund policy for your selection. Together they form one acceptance. This is the purchase acceptance (v1).
I am authorised to make this purchase for my organisation. I certify that the selected revenue band is correct for our whole consolidated group in the prior tax year. There is no audit right or inspection clause under these terms.
I confirm that the band above was assessed across my whole consolidated group as the licence defines it. Quoting Purpose Source License 1.0, §2: “An organization's group is that organization plus all organizations that control it, that it controls, or that are under common control with it. Control means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.” A small subsidiary of a large parent is inside the parent's group.
I accept the Entitlement terms identified below, including the selected coverage, annual term, fee, renewal and vesting rules, the respective roles of the Association and the project stewards, and the rules for using official badges and logos. Selecting coverage does not opt my organisation into public naming.
Project stewards are responsible for maintaining and publishing their code. Purpose Source manages your Entitlement and its coverage record.
The project’s licence and any agreement with its licensors govern software rights, support, warranties and liability. Purchasing an Entitlement does not add software guarantees or transfer the project’s responsibilities to the Association.
Read the Entitlement terms for coverage, fees, renewal, vesting, refunds and the respective responsibilities.
Purpose Source License 1.0 was published on 2026-10-01. Licence credentials are sold through our online reseller Paddle. Checkout opens at launch; no payment is taken before then.
Help people discover Purpose Source. You are welcome to mention our name, link to our website and official social profiles, and use our official logos and badges on your website, in repository READMEs, presentations, announcements and social posts.
You may write in your own words, in any language. Publicity is optional and needs no prior approval. The Association does not undertake to monitor purchasers’ communications. These rules apply to use of our official artwork and identity.
Permission is non-exclusive and free of charge. We may ask for a particular use of our artwork to be corrected or stopped if it breaches these rules. This does not create a duty to monitor your publicity or a requirement to submit it for review.
This permission covers the Association’s own marks. Purchasers remain responsible for their own statements and for any rights needed to use other organisations’ material. Nothing here authorises another organisation’s logo or implies its endorsement.
I choose the lane and what it covers. A Project covers the one registered repository I select; the Pass, every registered repository. What is passed on from this fee after the published, capped costs is attributed under the published allocation rule: for a Project, all of it to the selected repository; for the Pass, as the optional declaration below sets out. A selected repository that is not active at a lock drops out for that month: a Project's part is split equally across every registered repository active at the lock. Nothing is ever given to a project, contributor, owner or administrator: the money reaches only listed recipient organisations, by the category or listed recipient organisation designated for each repository, and otherwise under the allocation key the board publishes before each month. Attribution is advisory under the statutes and the board decides finally.
Optional, and for the Pass only. I may name up to fifty registered repositories my organisation uses, or none. Each named repository that is active at a month's lock is attributed 1% of what is passed on from this fee for that month, so fifty names take at most 50%. The rest, and all of it when I name none, is split equally across every registered repository active at the lock, the named ones included. A named repository that is not active at the lock drops out and its 1% returns to the equal split. Naming changes neither what the Pass covers nor its price, is advisory like every attribution, and is never published as a per-purchaser list. Every named repository is checked against the registry when the purchase is recorded.
Optional, in every lane. Ticked, I ask that my organisation's registered legal name be shown publicly: on the list of covered organisations, in the signed entitlement record, on the public record of its certificate and beside the ledger rows of its purchases. Unticked, my organisation is listed as “Unlisted organisation” under its reference code and is named in none of those places. The reference code does not itself display your name. Anonymity is not guaranteed: the reference code, the lane, what the Entitlement covers, its term dates, its status and the fee amount of each purchase stay public, and a domain my organisation verifies resolves publicly to that identifier. If our registered legal name is a person's name, ticking publishes that name. I may later ask to be unlisted; from then on the name is removed from the list, the signed entitlement record, the public certificate records and the ledger pages — the ledger rows themselves never carry it — and a signed certificate already published stays in copies others made.
The purchase checkbox does not select either optional choice. Public naming is controlled only by its separate, unticked option.
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 steward alone writes the numbers. Repository administrators never set prices, and a request for bespoke pricing is answered by pointing at the governance process — propose a schedule change for everyone — never by a private deal.
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, our merchant of record, adds any sales tax or VAT due in your country at checkout. 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.
Choose a Project or the Pass on the pricing page. A Project covers exactly one registered repository, which you pick. The Pass covers every registered repository. The registry record and your certificate name the scope you bought.
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.
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.
Your passed-on share is your part of what is passed on in a month: your net Purpose Fee (after the merchant of record's fee), less the published, capped costs and the measured currency drag in the fee stack below. It is attributed to registered repositories by the lane you bought, and from each repository it reaches listed recipient organisations by the categories chosen for that repository, and otherwise under the allocation key the board publishes before each month. No project, contributor, owner or administrator ever receives any of it (Art. 5 of the statutes).
| Repositories named | Attributed to the named repositories | Split equally across all registered repositories active at the lock |
|---|---|---|
| None | 0% | all of it |
| 1 | 1% | 99% |
| 10 | 10% (1% each) | 90% |
| 50 | 50% (1% each) | 50% |
If a repository you chose or named is not active at the lock — it quit, was suspended or delisted, or never resolved — it drops out for that month. A Project's share joins the equal split; a named repository's 1% returns to the equal split.
From each repository, the share follows the choice of the people who administer that repository: among the seven categories, or left to the Association, which directs it each month to where it is most needed. Inside a category, the amount is split equally among its active recipients. A share left to the Association, or that nobody designated, follows the allocation key the board publishes before each month; until the first key is published, such shares go equally to all active recipients. Contributors' designations are published from the first day and route money only after at least a quarter of data and a published fairness and misuse review. Attribution is advisory: the Association's board decides finally (Art. 8 of the statutes). The repositories a Pass holder names are never published as a per-organisation list.
Illustrative — no transaction has settled yet
Every deduction between what a payer pays and what a listed recipient receives. Percentages are illustrative until the first real transaction settles, at which point they are replaced by measured figures carried with the ledger row. Nothing stands between the fees account and a listed recipient: no pooled vehicle, no instruction that carries no money, no handling fee — what is passed on goes directly, from the fees account, to the public-benefit organisations on the published Recipient List.
Illustrative fee stack — Schedule v1
| Deduction | Illustrative share | Who takes it |
|---|---|---|
| Merchant of record | ~5% + a fixed USD 0.50 (illustrative) | Payment provider acting as seller of record, including card fees and tax handling |
| Running costs charged to fees | annual cap 15% of the year's net Purpose Fees — a ceiling on the year's itemised running costs, never a share of any fee | Everything the movement costs to run, charged to fees only inside this one cap and only where no listed supporter settled it: third-party invoices that exist solely for the movement — hosting, domains, email, monitoring, payment-rail charges, and the transfer charges on the outbound transfers to the listed recipients — and the pay of the people who do the work, employees, contractors and board members alike. Never a shared bill. People are published monthly as one line per function, never by name; pay to a board member stays within a maximum per function that the general assembly approves and needs the prior minuted approval of the other board members, the payee taking no part in it, and that approval is published too. Nobody is paid at founding. Bank-transfer and currency-conversion charges on the outbound transfers to the listed recipients are direct costs of their own eligible class (transfer charges), inside the annual cap when the fees account pays them, published per transfer. Transfers go by a regulated low-cost transfer rail chosen and published by the board; small monthly transfers are the price of the thirty-day rule. |
| Reserve retention | at most 5% of the Purpose Fees of each payout, until the target (adopted in the statutes of 2026-10-01; no cap is ever raised for a purchase already made) | The Association's operations reserve — an account that is not the fees account, with a published target of six months of the activity's running costs (half of the previous financial year's direct costs, set and published by the board each January). Filled from the other activities' income, sponsors and other unrestricted money, and from Purpose Fees only under this cap and only until the target is held; above target nothing is retained. It may be spent only on running costs not charged to Purpose Fees because of the cap — people included — and on the transfer charges of the final sweep. It is never a refund reserve. Movements, balance and target are published monthly, and the retention is its own ledger line. |
| Currency drag | measured per transaction | Currency conversion drag on the rail's cross-border settlement into the fees account, measured per transaction and carried on the ledger row's captured rate rather than estimated once. Conversion on the outbound transfers to the listed recipients is a transfer charge, a direct cost published per transfer. |
The same stack applied to a single fee from the published table, so the total is ours to state rather than someone else's to compute. Every figure in this walk is illustrative, the running-cost line carries none (it is a monthly invoice list, not a rate), and the reserve retention is shown at zero with its rule beside it, so what reaches a listed recipient is stated as a ceiling. Nothing here has been charged to anyone.
Illustrative end-to-end walk — $5M–10M band, Project lane, Schedule v1
| Step | Amount | Of the fee | What it is |
|---|---|---|---|
| Purpose Fee paid | USD 450.00 | 100% | $5M–10M band, Project lane, annual |
| Merchant of record (~5% + USD 0.50) | − USD 23.00 | 5.11% | Payment provider acting as seller of record: card fees, tax determination, remittance, refunds |
| Net Purpose Fee | USD 427.00 | 94.89% | What the payment rail pays out to the fees account — the amount the pledge is stated on |
| Running costs charged to fees | no figure | within the annual cap (15%) | Not a share of the fee: the month’s running costs that no listed supporter settled — hosting, domains, email, monitoring, payment-rail charges, the transfer charges on the outbound transfers to the listed recipients, and any pay for the work of running the movement — itemised on the transparency page, people as one line per function and never by name. Capped over the financial year. Nothing is printed here until the first monthly table exists, so every line below is a ceiling |
| Reserve retention (at most 5% until target) | − USD 0.00 | 0% | At most 5% of the Purpose Fees of each payout, retained into the operations reserve — an account that is not the fees account — only until the reserve holds its published target of six months of the activity's running costs (half of the previous financial year's direct costs, set and published by the board each January); above target nothing is retained. Shown at zero here so that the last line is a ceiling, not because nothing will be retained: the reserve starts at zero, so real payouts can carry this retention until the target is held. The numbers are adopted in the statutes of 2026-10-01; no cap is ever raised for a purchase already made |
| Currency drag (~0.5%) | − USD 2.14 | 0.48% | Conversion on the rail’s cross-border settlement into the fees account. Measured per transaction and carried on the ledger row, never estimated once and reused |
| Reaches the listed recipients — at most | USD 424.86 | 94.41% | What the public-benefit organisations on the Recipient List receive, in their published shares, before the month’s charged running costs (capped) and before any reserve retention under its cap — a ceiling, not a total |
At most about 94.41% of an illustrative $5M–10M-band Project fee reaches the listed recipients. The month's running costs charged to fees come off before that — never a share of the fee, capped over the year, itemised on the transparency page — and so would any reserve retention under its cap, so the figure is a ceiling, not a total. It moves when real settlement rates are measured, and it will move in public: the components above are published individually so a reader can recompute it instead of trusting it.
Worst case, published as such: at least 80% of a financial year's net Purpose Fee proceeds pass on to the listed recipients (100 − 15 − 5), every cap drawn in full. Net Purpose Fee proceeds are the statutes' base: after the payment provider's fee, without the taxes charged at purchase, and after refunds and chargebacks — never the amount the buyer paid. The operations reserve starts at zero, so until it holds its target of six months of the activity's running costs (half of the previous financial year's direct costs, set and published by the board each January), up to 5% of every payout can be retained into it. Sponsors, the Association's other activities and other unrestricted money can fill it sooner. The numbers are adopted in the statutes of 2026-10-01; no cap is ever raised for a purchase already made.
The pledge, in its only wording: 100% of net Purpose Fees go to the listed charities within 30 days of each payout, after published, capped costs: running costs at most 15% of a year's net fees, and the reserve at most 5% of each payout until it holds six months of costs, so at least 80% every year. Listed supporters lower the costs, never what is passed on. No cap is ever raised for a purchase already made. Every cost and transfer is published monthly.
The single end-to-end flow-through figure is published here as soon as a real month has settled and been measured. Until then the components above are published individually and the total is stated as a ceiling, not as a number we cannot yet stand behind.
The rest of the schedule
Below the threshold, this licence behaves like a permissive one: nothing to pay, nothing to register, no account. The test is dual — both conditions must hold for an organisation to be below it, so failing either one puts you above it — and it is measured across the whole consolidated group:
Non-profit and public bodies. A non-profit or public-benefit body, a public educational institution or a public body meets the threshold whatever its size; a commercial organisation such a body controls is measured like any other (section 5 of the licence).
Group consolidation. Section 2 of the licence groups the organisation with those it controls, those that control it, and those under common control, directly or indirectly through ownership, votes, contract or otherwise. A subsidiary is assessed with its group. Counsel has not yet confirmed the published wording.
The licence includes a 60-day cure period. Its section 6 names the trigger days: for growth past the threshold, the end of the tax year in which the organisation first grew past it, or the day it knew or should reasonably have known that reliable figures showed the threshold exceeded; otherwise the day a credential's term ended or a Waiver was revoked, the day a change of control happened, or the day the use began. At most 60 such days count in any twelve months. Checkout records the organisation's own band declaration; the licence grants no audit or inspection right.
This explains sections 2, 5 and 6 of Purpose Source License 1.0. This page does not create permissions or change the licence text.
Entitlements are annual, and every lane behaves the same way. The rule that matters for procurement is the vesting formula, and it is one sentence:
A version is vested to you if and only if its publication date falls on or before the end of your paid term.
At activation that means the entire back catalogue plus everything published during the term. Renewal extends the term end, which vests the next term's releases. Vesting is permanent: nothing — project exit, delisting, steward failure, or a waiver revocation — can strip a vested version from a payer mid-deployment. If you stop renewing, you keep everything you vested and simply stop accruing new releases. Waivers vest by the same formula, with "term end" meaning the revocation or expiry date.
Terms renew automatically each year unless you turn renewal off, which you can do at any time before the renewal date. The refund policy says how, and what each renewal reminder tells you.
A lapsed entitlement has a 30-day grace window during which coverage answers
lapsed-in-grace rather than no, so a late invoice is not an
instant compliance incident. A chargeback is not a grace period: it suspends the
entitlement, and coverage answers no immediately.
The founding cohort is not a discount and not a sale. It is every payer that buys while the schedule's figures are still illustrative, and it has no price term of its own: an early payer pays the schedule in force at each purchase and each renewal, like every other payer. A schedule changes only by a new version. A price rise, a re-cut of the revenue bands or a withdrawn product is announced 90 days before it takes effect; any other change, 30 days before.
The end condition is a fact, not a date: the founding cohort closes when the schedule is ratified and its figures stop being illustrative. That is why there is no countdown here — we do not know the date, and inventing one to create pressure is exactly the behaviour this movement exists to be an alternative to.
100% of net Purpose Fees go to the listed charities within 30 days of each payout, after published, capped costs: running costs at most 15% of a year's net fees, and the reserve at most 5% of each payout until it holds six months of costs, so at least 80% every year. Listed supporters lower the costs, never what is passed on. No cap is ever raised for a purchase already made. Every cost and transfer is published monthly. The methodology and the fee stack above are the whole of it, and the Trust Center carries the documents as they come into existence. Every allocation lands in the append-only ledger. How a buyer's share is attributed to repositories is set out under How your share is attributed.
From launch, every version stays published at a permanent URL with its effective-date
range, and a schedule change never rewrites the version a payer bought under; until
launch, version 1 is edited in place. The current version is always at
/pricing/schedule; its machine copy is
/schedule/v1.json,
also reachable as /schedule.json.
An ordering rule, and a constitutional one for the schedule: no plausible stack of à-la-carte lanes may beat the Pass at scale. The single-lane options exist because "this one thing we use" is an easier procurement conversation in some rooms than "everything" — and the money routes to public benefit either way. If a future schedule version ever broke that ordering, the ordering wins and the numbers change.