ORA-2.2
An individual developer deploying it for a paying client, under ORA 2.2
One person, no company, releasing or consuming work in their own name. Installing or operating the Work on infrastructure the customer owns and controls. This resolves to the Root tier.
Tier
Owed
Nothing. No fee, no report, no filing.
Sections in play
1.7, 1.9, 2.1, 2.2
Who and what
The situation being resolved.
Actor
An individual developer
One person, no company, releasing or consuming work in their own name.
none
Situation
Deploying it for a paying client
Installing or operating the Work on infrastructure the customer owns and controls.
Rulings
3 questions resolved against the text.
Which tier applies?
Root. One person, no company, releasing or consuming work in their own name. Below $20,000,000 in trailing revenue, or within an exempt category, no Canopy royalty applies. Sections 4, 6, 8, and 10 still bind every Licensee.
Sections 1.7, 2.1, 2.2
Is anything owed?
Nothing. No fee, no report, no filing.
Sections 2.1
Does this count as Production Use?
Yes. Installing or operating the Work on infrastructure the customer owns and controls. Section 1.9 covers internal operation at operating scope and systems made available externally to customers or the public. Development, testing, evaluation, research, and personal non-revenue use remain outside it.
Sections 1.9
Cautions
What this situation gets wrong most often.
Revenue is measured across entities under common control, per Section 1.4. A parent company above the threshold makes its subsidiary a Canopy Licensee regardless of that subsidiary's own turnover.
Attribution lives in the package manifest under ORA 8.1, not only in documentation, because an agent package is installed by a machine that never reads a directory listing.
Same actor
Other situations for this party.
Non-normative. Where this and the licence text disagree, the licence text applies.