Software Developers & Agencies - License Your Git Repositories

About Gramian

Gramian Consultancy is a boutique consultancy specializing in IT professional services and engineering talent solutions. With a strong background in software engineering and leadership, we help companies build high-performing teams by matching them with professionals who truly fit their needs.

About the Opportunity

We are looking to connect with software development agencies, IT companies, and independent software engineers who own valuable code repositories and are interested in licensing them for AI training.

How It Works

• Connect your existing Git repositories to the platform.
• Choose which repositories you want evaluated for potential licensing.
• Receive a repository-level breakdown of source-code and Git-history token volume.
• Review an estimated licensing value for each repository.
• Receive quality feedback if the codebase does not yet meet licensing requirements.
• Improve repositories based on the recommendations and resubmit them for evaluation.
• Select which qualifying repositories you want to make available for AI training.
• Earn compensation when your code is used under an approved licensing arrangement.

Compensation

For standard non-exclusive licensing, codebases are currently valued at:

• $100 per 1 million tokens of source code
• $40 per 1 million tokens of Git history

Each repository displays its own token breakdown and estimated licensing value before you decide whether to proceed.

• Software development agencies, IT/product companies, or independent software engineers that own or control the licensing rights to original code repositories and are authorized to license them for AI training. §

• You must own the repository or have the legal authority to license its contents.
• The repository should contain meaningful original software-development work.
• You must have the authority to connect and submit the repository for analysis.
• The code must not contain third-party material that you are not permitted to sublicense.
• Repositories must meet the platform's quality and technical requirements before licensing.
• You must be able to verify repository ownership and relevant licensing rights if requested.