Software Engineer & Code Owner - AI Code Licensing Program
Posted Updated
Description
About the opportunity
Gramian is participating in an exclusive, invite-only code licensing program with a leading AI lab. The program allows software developers, engineers, and organizations to earn compensation by licensing existing software repositories for AI training and research purposes.
This is a non-exclusive licensing opportunity, meaning code owners retain their intellectual property and can continue using, maintaining, selling, or licensing their software elsewhere.
Priority technologies
We are looking for high-quality, complete software projects, particularly in:
- Legacy systems (highest priority): COBOL, Fortran, and JCL—ideally 10,000+ lines of production code from banking, insurance, or scientific systems. Retired systems are welcome.
- Modern development: Kotlin, OCaml, TypeScript, React, and Next.js.
- Game development: Three.js, React Three Fiber, WebGL, Godot 4, Unity C#, Unreal C++, and Phaser 3.
Compensation and timeline
- Valuation: $100 per million tokens of code and $40 per million tokens of Git history. An offline script is available so you can run evaluations without entering the program.
- No new development is required—license your existing code.
- Payments are expected before Christmas 2026, or by January 21, 2027, if quality assurance is delayed.
- Future cohorts may offer additional opportunities starting in January 2027.
Requirements
- Private codebases only: Code must never have been publicly available, including on GitHub, GitLab, npm, or PyPI.
- Human-written code: AI-generated code is not accepted. Projects developed before 2025 are preferred; newer projects require additional verification.
- Code ownership: Applicants must own the code or have full licensing rights. Client-owned projects require written authorization.
- Substantial, functional projects: Complete applications, SaaS platforms, backends, internal tools, or production systems. Basic templates, forks, WordPress projects, and code snippets are not accepted.
- Git history: Repositories should include their original commit history, ideally with multiple contributors, pull requests, code reviews, issues, and tests.
- Repository access: Code should be accessible directly through GitHub, GitLab, or Bitbucket for evaluation.
- Bonus: Supporting project documentation, tickets, and development records may provide additional licensing opportunities.
Skills
Sign in to read and join the discussion.