Operating company
Additional revenue, without giving up any of your business or your content.
Technical documentation · Licence of use · Training data
Your teams have produced years of documentation. It can still generate revenue.
Opus Archives pays digital companies to use some of their internal content (technical documentation, tickets, code and code reviews) to train and evaluate AI models.
You keep ownership of your content and your software. Scope, permitted uses and payment are set out in a contract.
- Fixed payment, made at signature
- Non-exclusive licence: you keep your content
- Company name removed from the data
- Messaging and customer data excluded
Why this content has value
What has value is the path from a problem to its resolution.
On its own, an internal document is worth little. Linked together, your tools show how a team actually worked on real situations.
-
The ticket
describes a problem or a request, with its context.
-
The specification
sets out the intended solution and its constraints.
-
The code
shows the change that was actually made.
-
The review
shows the corrections, trade-offs and sign-off.
These sequences are used to train and test AI models on software development tasks: understanding a request, finding the relevant context, proposing a change and checking the result. That is why the links between tickets, documents and code matter as much as the content itself.
Payment
How we assess your content
There is no price list: each body of documentation is assessed case by case.
- What we look for
- Real software projects, several years of history, and above all links between tools: tickets connected to specifications, code and reviews.
- What drives value
- Usable volume, the technical depth of the exchanges, continuity of the history and the rights you hold over the content.
- How you are paid
- A fixed amount, written into the licence agreement and paid at signature.
- If the archive is not a fit
- We do not make an offer on every case. The assessment may conclude that a licence is not relevant; we will tell you plainly.
Who it is for
Four situations, one approach
Documentation can be given value at several points in the life of a digital company.
Voluntary wind-down
Dissolution or solvent liquidation: plan it before online accounts are closed.
Divestment or product shutdown
The documentation of a discontinued product can be valued separately.
Judicial liquidation
With the liquidator and on authorization of the supervising judge.
What the licence covers, and what it excludes
The exact scope is agreed in writing before anything is signed. Depending on what is agreed, it can include:
Included
Included depending on scope
- Wikis and Notion or Confluence spaces
- Tickets: Jira, Linear, GitHub Issues
- Specifications, runbooks and postmortems
- Repository source code, with its history: commits, pull requests and reviews
Excluded
Always excluded
- Messaging: Slack, Teams, email
- Customer files and production databases
- HR and legal spaces
- Personal data of customers and employees
- Code written for clients or under a third-party licence
Source code can therefore be part of the scope. The licence does not transfer its ownership: it only permits its use to train and evaluate AI models. It grants no right to run, distribute or commercialize your software. Your brand and domain names are not affected, and you remain free to sell the software.
Process
How it works
The steps depend on the company's situation. Choose your case.
Companies
- 01
First conversation
You tell us about your business, the tools you use and the period your archives cover.
- 02
Inventory under NDA
Review of tools, volume and age of the content, under a non-disclosure agreement.
- 03
Assessment and proposal
A written proposal setting out scope, exclusions and amount, or a note that a licence is not relevant.
- 04
Agreement and payment
Signature of the non-exclusive licence of use; the fixed amount is paid at signature.
- 05
Export and preparation
Export of the content, removal of identifying elements, then deletion of the raw exports.
Insolvency practitioners
Before closing the Notion, Jira or GitHub accounts, check whether their content can be given value.
- 01
Case referral
You tell us the company and which online tools are still active; we quickly assess the archive's potential.
- 02
Protective export if needed
If unpaid subscriptions put the accounts at risk, we can run a protective export before they are closed.
- 03
Inventory under NDA
Review of tools, volume and age of the content.
- 04
Firm offer
Offer in the usual format for asset sales, with no conditions precedent.
Offer details
10% deposit by bank cheque, bank certificate of funds, declaration of independence (art. L642-3 of the French Commercial Code).
- 05
Authorization, deed and preparation
Authorization by the supervising judge, signature of the deed, then export, preparation and deletion of raw exports.
Confidentiality
Who will see what of your company?
Prepared content is passed, under licence, to teams that train and evaluate AI models. Here is what they receive, and what they do not.
Your company name is removed
Your company name and brands are removed from the content: recipients do not know which company it comes from.
Authors are pseudonymized
Staff names, usernames and addresses are replaced with consistent pseudonyms, keeping who replied to whom without revealing who they are.
Customers and personal data removed
Customer names and personal data found in the text are removed.
Technical secrets removed
Keys, tokens and technical credentials are detected and removed.
What cannot be cleaned is left out
Content that cannot be sufficiently stripped of identifying elements is not passed on.
Raw exports deleted, access limited
Original exports are deleted after delivery. Only the people who need them have access, and every access is logged.
Recipients receive a licence limited to training and evaluating models. They obtain no right to run, distribute or commercialize your software.
Buyers
For teams that train and evaluate AI models
Real software development histories, with rights cleared by a written licence.
- Linked sequences: ticket, specification, code change and review, in their real order
- Executable environments where the history allows: the agent starts from the repository state before a change, receives the original request, and its proposal is checked against the project's tests
- Traceable provenance: each dataset is tied to its licence, with the agreed scope and exclusions
- Content prepared under one protocol: company not identified, authors pseudonymized, secrets and personal data removed
Questions
Frequently asked questions
Do you take our source code?
It can be part of the scope, if you agree. The licence does not take away your ownership and only permits its use to train and evaluate AI models, with no right to run, distribute or commercialize the software.
What rights do we need to hold?
You must hold the rights to the licensed content. That is why code written for clients or under a third-party licence is excluded. This is checked during the inventory.
How is payment calculated?
It depends on usable volume, technical depth, continuity of the history and the rights available. It is a fixed amount, written into the agreement and paid at signature.
Who receives the content?
Teams that train and evaluate AI models, under licence. They receive content from which your company name, authors' identities, personal data and technical secrets have been removed.
Do you collect employees' messaging?
No. Slack, Teams and email are always excluded, as are HR and legal spaces, customer files and production databases.
Is the licence exclusive?
No. You keep your content and can continue to use it as you wish.
About
About us
Opus Archives is led by Maxime Pfrimmer, a former project leader at Boston Consulting Group and founder of a software development company. That experience gave him first-hand knowledge of what technical teams produce: specifications, tickets, documentation and code reviews.
Graduate of École polytechnique and HEC.
Opus Archives is operated by Opus MP, a French SASU registered under SIREN 991 303 975, 35 rue Vital, 75016 Paris.
Contact
Could your documentation interest Opus Archives?
Tell us about your business, the tools you use and the period your archives cover. This first information lets us tell you whether an assessment makes sense.
Information you send us by email is used only to answer your request. See our privacy policy.