DATA TYPES

License your private source code for AI

Private software you have already built could generate additional revenue through paid licensing, including for agreed AI training or evaluation. BRIDGERS acts as an intermediary for a possible introduction to a specialist partner. Whether a project is accepted and licensed depends on its origin, rights, review and an actual deal. Start with a description of the projects and their development history. The first conversation helps define the collection and the questions before a possible next step. Keep code, repository links and credentials in your systems during this initial enquiry.

Discuss your company data

A possible return from software you have already built

A shelved SaaS product, an internal tool replaced by a newer system or an older backend can contain years of engineering work. Its source, tests and changes show how a real application developed. That context can be useful when training or evaluating coding models.

For an agency, the starting point is delivered work the agency still has the right to license. For a company or founder, it may be a discontinued product or an internal application. An insolvency practitioner can enquire about a software asset too, subject to the relevant rights and authority.

Licensing is a possible additional return. A specific codebase still needs eligibility, rights and buyer review before there can be a deal.

What makes a codebase worth discussing

The current programme seeks original software written by people, kept private throughout its history and supported by sufficient licensing rights.

Team-built projects and specialised systems can provide richer context. Smaller projects and software written by one person can also be discussed. Contributor counts, lines of code and a quality grade do not guarantee a licence, and they are not minimum thresholds for this enquiry.

  • A complete application: source with the available configuration, documentation and tests, rather than an isolated script.
  • A genuine development record: the original Git history, with commits, fixes and reviews where available.
  • A clear origin: who built the software, what it was used for and who can authorise its licensing.

Which projects this route excludes

This licensing route does not accept code that is public or has ever been public, including source distributed as a public package. Making a repository private later does not change that history.

It also excludes AI-written code, other people's forks or renamed open-source projects, duplicate submissions, lightly modified public templates, and WordPress sites, themes and plugins. Repositories containing only generated output or data dumps have no licensable application source. Single-file scripts are outside this route.

Open-source dependencies need a separate assessment. A private application using third-party libraries is a different case from a copy of somebody else's public project. Its components and licence obligations must still be disclosed.

Keep the original history

Human-written projects started before 2025 are the strongest fit under the current criteria. A first commit in 2025 or later triggers a closer look at how the software was developed; it is not an automatic rejection. Mixed or uncertain AI involvement also needs clarification.

Keep the original Git repository intact. Copying its files into a fresh repository or squashing its history can remove evidence of earlier development. If it lives locally, retain that history for a later agreed submission. Please do not send repository links, invoices or other supporting documents in this first enquiry.

Establish who can license the work

Repository access alone does not establish licensing rights. Check the position of employees, contractors and clients who contributed to or commissioned the software. Client-owned code requires the client's written permission before submission to the programme.

Where several group companies share a system, identify the entity with the relevant rights. Existing licences, customer agreements and confidentiality obligations may affect what it can authorise. Disclose third-party components, particularly copyleft obligations such as GPL, AGPL or LGPL.

You can mark unanswered questions as unclear. BRIDGERS will keep them open for discussion; a complete questionnaire does not resolve them.

How an enquiry progresses

Keep source files, snippets, credentials and customer details out of the BRIDGERS enquiry. A later connection to GitHub, GitLab or Bitbucket happens through the separately agreed partner process.

BRIDGERS may receive a referral payment for an introduction. Any external website change and relevant terms will be explained before you proceed. Read about BRIDGERS and its role.

  • Describe the projects. Tell us their broad purpose, approximate period, development history and what you know about rights. An estimated or unknown repository count is acceptable.
  • Discuss the next step. BRIDGERS reviews the description with you and identifies questions to resolve before a possible introduction. We do not buy or prepare the code ourselves.
  • Choose whether to enter the partner process. Any introduction is separately agreed. In that process, the owner reviews the contract and chooses which repositories to submit for analysis and possible buyer consideration.

Understand the licence before authorising it

Under a standard non-exclusive licence, ownership and continued use of the software remain with you. The programme's agreement authorises individual standard licences without asking you to sign each deal. Buyer rights already granted generally continue after withdrawal.

The agreement also lets the platform partner take a paid, permanent non-exclusive licence for its own use without further approval. The partner can use that licence in its own products and derived data without further payment for those uses. Permitted uses extend beyond AI training alone. An exclusive deal or outright acquisition requires separate written agreement. The sample agreement includes an uncapped owner indemnity for specified claims, while limiting the platform partner's liability. Review the applicable contract with your advisers before signing.

Will I receive a price from this check?

The enquiry helps establish what you have and whether a further discussion makes sense. It is not a valuation or purchase offer. A repository's size, age or quality grade cannot establish its licensing value on its own.

Can the same software be licensed more than once?

Non-exclusive licensing can allow separate deals with several buyers. Each licence is a separate potential payment; neither repeated licensing nor a continuing royalty is promised. Eligibility also does not mean a buyer will choose the code.

Must we clean or rebuild it first?

The partner's process works on a separate copy, uses read-only repository access and describes checks for secrets and personal data. Contributor identities are pseudonymised before buyer delivery. Grading reads the cleaned copy without running the application. Known sensitive content must still be disclosed through the agreed process. Cleaning does not replace the owner's contractual responsibilities.

Can we withdraw later?

Withdrawal has contractual notice periods and exceptions for deals already in progress. Existing licences and the platform partner's acquired own-use rights can survive. Revoking Git access stops future access; it does not recall copies or rights already granted.

What about tickets, documentation and chats?

Work records linked to a repository may be considered through an experimental operational-data feature. There is currently no promised quote, valuation or payment for them. Please keep these exports out of the initial enquiry.

Where is the code handled, and how long can a deal take?

The programme describes storage in eastern North America and the involvement of service providers. Confidential handling does not mean the code stays within the EU. Processing arrangements need review before submission. Buyer assessment and payment can take months; an enquiry does not start a guaranteed payment deadline.

Are there location restrictions?

The current route cannot serve code owners resident in Russia. Other cases remain subject to the applicable programme, export and sanctions requirements; a country selection alone does not confirm acceptance.

Begin with the project overview

Describe what the software does, when it was developed and what you know about its ownership and history. Mark anything uncertain for follow-up.

For a mixed archive, the company-record categories help you separate software from the surrounding business records.

THE FIRST STEP IS A DESCRIPTION.

What records would you like to discuss?

Start with what you know. No files, exports or confidential material are needed for your first enquiry. Open questions can stay open.

Discuss your company data