Saffron Solvency

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 range

Why the records count

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.

Over the years, your release notes, tracker and reviews link those steps into one record.

What usually counts

  • Commit and repository history. The long arc of a codebase.
  • Pull requests and reviews. The objections reviewers raise.
  • Tickets and incidents. The path from bug report to resolution.
  • 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. Scoping covers ownership, and client work can be left out completely. Reading the contracts is a job for your counsel. We do not give legal advice.

In the copy, customer details in tickets, logs and chat become placeholders.

Things you keep back

  • Client projects. Out unless you and your counsel decide otherwise.
  • Core products. Any repo or period can stay out.
  • Credentials. Never asked for, never passed on.

The process

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.

Questions from founders and owners

Is the code still ours?
Yes. What buyers license is a copy, never your code itself.
What does it cost?
Nothing. It is free for you.
What should we get ready?
No. It is enough to know which tools your team uses and roughly since when. Nobody asks you to export anything.
Do we have to grant repo access?
No. The originals remain in your systems, and License Your Data works from a de-identified copy.

What could your code history be worth?

It begins with your team size.

How many employees does your company have?