Codebases & software
Source code, tests, issue histories and developer documentation.
Why it may be usefulHow software is built, tested and fixed, with the task and outcome kept together.
AI developers license codebases, documents, databases, communications and media to train their models. You keep ownership, approve every introduction and sign directly with the buyer. Witbur charges you nothing.
Describe your dataData lives throughout a company—in its software, files, systems and everyday work. A collection can span several of these categories.
Source code, tests, issue histories and developer documentation.
Why it may be usefulHow software is built, tested and fixed, with the task and outcome kept together.
Internal documents, technical manuals, research, presentations and knowledge bases.
Why it may be usefulSpecialist explanations, methods and domain knowledge, with the supporting context intact.
Tables, spreadsheets, catalogs, historical datasets and linked metadata.
Why it may be usefulRelationships, patterns and measurements with a consistent structure and clear meaning.
Project histories, support tickets, internal communications and documented processes.
Why it may be usefulHow people work through a problem, reach a decision and respond to an outcome.
Photo libraries, recordings, footage, diagrams and other visual or spoken material.
Why it may be usefulDomain-specific examples of what a model needs to recognize, understand or generate.
CAD files, simulations, engineering models, scientific measurements and specialist datasets.
Why it may be usefulThe geometry, constraints and technical reasoning behind work in a particular field.
We assess the collection, its context and your authority to license it. Code dependencies, third-party content, confidentiality and personal information may need separate review.
Five stages. Nothing moves forward without your approval.
Describe what you hold. We tell you whether it is likely to interest buyers, and what would need checking.
We prepare a short, non-confidential summary buyers can review without seeing any data. NDAs come before anything specific is shared.
With your approval, we introduce you to buyers whose requirements fit. A buyer may ask to evaluate a sample under NDA.
You negotiate and sign directly with the buyer, with your own advisors. The license sets scope, use, handling and price.
You deliver as agreed and the buyer pays you directly. Witbur’s fee is paid by the buyer, not deducted from your payment.
Timings are estimates, not commitments. They depend on the collection, the buyer’s evaluation and, for a company in bankruptcy or receivership, the trustee’s or receiver’s process.
The buyer pays you under the license. Witbur takes nothing from that payment; our referral fee is paid separately by the buyer.
Payment terms are set in the license—for example a fixed fee, a price per unit of data, or staged payments tied to delivery.
Before an introduction, we explain how the buyer pays us. This gives Witbur a commercial interest in the introduction, which we disclose to you.
You choose whether to proceed. Any costs for your own legal advice or data preparation are yours to cover; Witbur charges you nothing.
Ownership, confidentiality, contracts, privilege and privacy obligations may affect which material can be used. Your own legal and privacy advisors review those questions and the proposed agreement.
The license should address who can use the material, for what purpose, for how long, and under which access, retention and onward-use arrangements. Removing names alone does not establish that data is anonymous.
A license is not automatically exclusive, limited to one use or reversible. Its terms need to reflect what you are willing and able to approve. Licensed data moves directly between the holder and buyer under their agreed arrangements.
No. Start with a description. This website has no file or dataset upload facility. Source files and datasets are shared only after the purpose, permissions and handling arrangements have been agreed.
Yes. Founders, bankruptcy trustees, receivers and administrators can discuss a collection. The person authorizing a license needs the relevant authority, and the material and proposed use still need review.
No. Interest depends on the data, its quality, context, permissions and the buyer’s requirements. We assess fit before recommending an introduction.
Yes. You choose whether to approve an introduction and whether to enter a license. Once a license is signed, its duration, permitted uses and any termination rights depend on that agreement.
A short outline is enough for the first conversation.