Skip to content

For companies · Software project data

License your software project history.

Bug reports, code changes, reviews and tests record how your team builds and repairs software. SnowRock helps companies explore licensing the project history they have rights to share.

Discuss software data

Start with a description of your records.

The records you create

Your code and the history of how it was built.

  • Issues and bug reports

    Reported problems, developer discussions and the decisions about what to fix.

  • Code changes and reviews

    Code revisions, review comments and the changes your team approved.

  • Tests and release history

    Test results, build records and the versions your company released.

Why a buyer may license it

Help AI learn from real software development.

A project history can connect a reported problem to the fix, the review and the test result. AI developers may license that history to:

  • Train systems to diagnose bugs and propose code changes.
  • Test proposed repairs against recorded fixes and tests.

Market example

Turing seeks software histories for AI training.

Turing’s Project Lazarus seeks source code, reviews, tickets and development history for frontier AI training. Its process starts with a description, followed by a sample review and a contract.

Turing sets an offer after reviewing a sample.

The requested records connect code with the discussions and changes that produced it.

Before preparing files

What to discuss with SnowRock.

You do not need to send raw records to begin. Tell us what your company has and which licensing options you would consider.

Projects and linked records
Name your repositories and issue, review and test systems. Give the years covered and explain whether an issue can be followed through code changes, review comments and test results.
Versions and test setup
Describe available code versions, setup instructions, dependency versions and saved test logs. Identify missing files or services that would prevent a buyer from running a saved test.
Authority and exclusions
Name who can approve a license. Have your company’s reviewer identify restrictions involving code ownership, dependencies, customer agreements and credentials.

Your company agrees the terms

Discuss licensing your software history.

Your company and the buyer agree which records may be licensed, permitted uses, preparation, delivery and price. Your company delivers the agreed data directly to the buyer. The buyer pays your company for the data license. SnowRock’s buyer-paid fee is agreed separately.

Discuss software data