Software and IT services
The way your team ships and supports software
Pull requests, tickets and release history, after client code and customer data are dealt with.
See my rangeWhy the records count
Public code is everywhere. What surrounds private work is not, like the ticket behind a change, the review that rejected it and the fix after a bad release.
Your tracker, review history and release notes tie those steps together over years.
What usually counts
- Commit and repository history. The long arc of a codebase.
- Pull requests and reviews. What reviewers push back on.
- Tickets and incidents. How problems get reproduced and closed.
- Architecture docs and release notes. The reasons behind your system design.
The worry owners raise first: code that is not ours
If you build for clients or run their systems, much of that work may belong to them and may need their permission. Ownership is covered when the scope is set, and client work can stay out entirely. Reading the contracts is a job for your counsel. Legal advice is not something we offer.
Customer details inside tickets, chat and logs are replaced with placeholders in the copy.
Things you keep back
- Client projects. Excluded unless you and your counsel choose to include them.
- Core products. Any repo or period can stay out.
- Credentials. Never requested or shared.
After the form
Submit the estimate form and a License Your Data specialist calls within minutes to schedule a 15-minute call under NDA. Then License Your Data produces a de-identified copy of your in-scope records. Buyers license the copy only after you approve a sample.
Owner questions
- Is the code still ours?
- Yes. Buyers license a copy, not your code.
- Will anyone get into our repos?
- No. The originals remain in your systems, and License Your Data works from a de-identified copy.
- Do we need to prep anything?
- 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. It is free for you.