Agency code licensing: reusable tools or client code?
Sort your agency's repositories before any code licensing conversation. Reusable tools and internal code become candidates when agreements and rights records support them; client project code and disputed components need contract review first.
On this page

Separate reusable tools from client work
An agency's reusable library and the client panel built on top of it can have different owners. Before a code licensing inquiry, separate the tools your company may license from the work it assigned to clients. Keep unresolved components off the proposed list.
Pangea's agency code licensing page sets its own boundary: submit only private code you own or have the right to license. It excludes client-owned, previously public or forked code, confidential data and conflicting third-party rights. Your contracts help you decide which repositories can meet those conditions.
Which repositories belong in the inquiry?
For each repository, record the agreement that supports your right to license it. These categories help organize that review; they do not decide ownership.
| Code you hold | Agreement to check | Decision before an inquiry |
|---|---|---|
| Reusable framework, starter kit or component library | Employment or assignment records, plus any client agreement affecting reuse | Consider it once the rights records check out and licensed third-party parts are separated |
| Internal pricing tool, build script or dashboard | Employee and contractor agreements | Consider it once those agreements confirm your right to license it |
| Client project code | What the engagement assigns and what it reserves | Leave it out unless you hold licensing rights in writing |
| Module extended by both your team and a client | The contracts covering the original work and later changes | Hold it while the rights question is unresolved |
For United States readers, the Copyright Office's work-made-for-hire circular addresses employee work created as part of regular duties, among other categories. Status depends on the work and relationship. The circular does not settle a particular repository's ownership; record what the actual agreements say.
Check the ownership warranty
Pangea says the submitter is responsible for holding rights to everything submitted and disclosing relevant third-party rights. Its page says an incorrect warranty may mean returning payments and covering resulting claims, and describes that obligation as uncapped. Read the agreement with your counsel before signing.
One client project can contain different rights
Cardinal Studio is a fictional agency. In the example below, every Include assumes the named agreement was read and verified.
| Repository | Rights basis in this fictional case | Decision |
|---|---|---|
| cardinal-platform | Employee-written reusable React library; the studio's employment agreements support ownership | Include |
| cardinal-estimate-tool | Contractor-written pricing tool with an assignment clause on file | Include, retaining the agreement |
| northline-site | Client engagement assigns the results to the client | Exclude |
| northline-dashboard | The studio retains its platform, while the client owns the panel built on it | Exclude the panel; keep the platform separate |
| vauxhall-booking | Client contract is silent on assignment | Hold |
| hud-admin-template | Fork of a public admin template | Exclude from this program's proposed package |
| cardinal-ci-scripts | Employee-written build and deploy scripts, created as part of regular duties | Include |
| fairhaven-prototype | Jointly funded work with no written terms | Hold |
The platform and client panel can sit in the same folder while requiring different decisions. A silent contract also leaves a question to resolve; it is no substitute for an assignment or permission.
Keep the program's handling promises separate from your rights review
Pangea describes read-only access limited to the repositories you select. It says scrubbing and grading take place on a separate copy, leaving the original repositories untouched. You keep ownership, and standard licences are non-exclusive, so one repository may be licensed to more than one buyer.
Those published statements do not promise acceptance, a price or a timeline for your code. Preparation on the program's copy also leaves the ownership question with you.
Put the agreement reference beside each proposed repository and name who can approve the list. Check older contractor terms, disputed modules, public forks and third-party dependencies separately. Ask a client for written confirmation where reuse rights remain unresolved.
Use the rights checklist to keep those unresolved questions together. The source-code guide covers the wider preparation task. Once you can describe your proposed list, read the Pangea profile or compare programs with the finder without uploading code.
Sources and limitations
Circular 30: Works Made for Hire Checked 2026-11-08
U.S. Copyright Office · Primary source
When it is created by an employee as part of the employee’s regular duties
U.S. copyright guidance only; work-for-hire status depends on the actual facts and applicable requirements. This does not determine rights in a visitor’s records.
Monetise Your Codebases | Pangea.ai Checked 2026-11-15
Pangea.ai · Primary source
Only submit private code that you own or have the right to license. Do not submit client-owned, previously public or forked code
Describes Pangea's own agency code-licensing program. Individual acceptance, pricing and a visitor's rights require separate confirmation.