Software and IT services
How your engineers build, ship and support
Tickets, pull requests and release history, with client code and customer data handled first.
Start my estimateWhy private engineering records matter
Plenty of source code is open. The story of private work is hidden: which ticket kicked off a change, which review bounced it, what got fixed after a rough release.
Those steps connect across years in your tracker, release notes and review history.
What typically counts
- Commit and repository history. How a codebase changes over years.
- Pull requests and reviews. Where reviewers ask for changes.
- Tickets and incidents. How problems get reproduced and closed.
- Architecture docs and release notes. The reasons behind your system design.
The first concern: client code
If you build for clients or run their systems, much of that work may belong to them and may need their permission. Who owns what is settled during scoping, and any client work can be fully excluded. Reading the contracts is a job for your counsel. Legal advice is not something we offer.
In the copy, customer details in tickets, logs and chat become placeholders.
What you may exclude
- Client projects. Out unless you and your counsel decide otherwise.
- Core products. Hold back any repo or period.
- Credentials. Never requested or shared.
How it works
You fill in the estimate form, and a specialist from License Your Data calls within minutes to book a 15-minute call under NDA. License Your Data then prepares a de-identified copy of what you put in scope. You approve a sample, and only after that do buyers license the copy.
Owner questions
- Do we have to grant repo access?
- No. Your originals stay in your systems. License Your Data prepares a de-identified copy.
- What should we get ready?
- No. Just know your team's tools and roughly how long you have used them. You will not be asked to export anything.
- What do we pay?
- Nothing. There is no cost to you.
- Do we stay the owner?
- Yes. Buyers license a copy, not your code.