COBOL codebases
Codebase submission — country eligibility not specified
Special Referral gives your application an enhanced referral route, helping it stand out and potentially improving your chances of being considered.
Important note: Submitting is free and does not itself license the code. Payment occurs only if a customer licenses the codebase and pays; selection, licensing and payment are not guaranteed. The licence includes 12-month exclusivity for licensing to AI companies.
About the role
Private production COBOL codebases built by a team over time.
Submit an existing codebase for potential licensing to AI companies. This is a codebase licensing opportunity, not an employment vacancy.
Scope of Work
- Submit a codebase you own or are authorized in writing to license, with its authentic development history and supporting materials.
- Complete the platform checks and review the proposed licence terms if selected.
What you’ll bring
- Private repository you administer on GitHub
- 100,000+ lines of your own code
- 1,000+ commits
- 50+ merged pull requests
- Pull requests made over 6+ months
- 10+ people with GitHub accounts over 3 months old who opened merged pull requests
- Test coverage above 25%
- Mainly written by people
- Code you own, or code a company owns that you are authorised to license: a product, a startup (live or shut down), an internal system, or a library or tool.
- Size, history and team requirements depend on the request. Each request lists them, and we check them against GitHub before you submit.
- Written mostly by people. Some AI help is fine; tell us roughly how much.
- Code that no AI company, AI lab or AI data supplier already has, and that is not licensed exclusively to anyone.
- The full history: real commits and pull requests made over time, not one upload.
- The context around the code: tests, CI configuration, docs, issues and pull requests. These count as much as the code itself.
- You are happy for your name and the history to stay attached to it.
Benefits
- Owners retain ownership and can continue using their code.
Contract & Payment Terms
- Submission access: Install our read-only GitHub app on the repository you want to submit. It can read the code, history, pull requests, issues and CI runs of the repositories you choose, and nothing else. It cannot change anything, and you can remove it at any time.
- Organization repositories need an owner of the organization to approve the app. You can manage the app on GitHub.
- Connect GitHub and pick the repository. Our app is read-only and only sees the repositories you choose. We check the requirements against GitHub before you submit.
- Submitting is free and does not license anything yet. Every submission runs through automatic checks, then a person on our team reviews it. You see the status on this page.
- If your codebase is selected, we verify your identity with a short ID check, then offer you licence terms that state the payment. It is a licence, so you keep ownership and can keep using your code. For 12 months we are the only one who may license it to AI companies.
- You are paid only if a customer licenses the codebase and pays for it. Submitting guarantees no selection, licence or payment, and we may decline without giving a reason.
- We check every submission against GitHub and public code archives. False information, altered history or code you do not have the right to license can lead to removal from the platform.
- Automatic rejection: Code written for an employer or a client, including freelance or agency work, unless your contract gives you the rights in writing.
- Automatic rejection: Forks, copies or mirrors of someone else's project, and course, bootcamp or tutorial projects.
- Automatic rejection: A zip of files, or a history squashed into one or a few commits.
- Automatic rejection: History rewritten to look older or more gradual than it was.
- Automatic rejection: Code that is mostly AI-generated.
- Automatic rejection: Code licensed exclusively to someone, or already given to an AI company, AI lab or AI data supplier.
- Automatic rejection: Passwords, API keys, tokens, or anyone's personal data anywhere in the code or its history.
- Automatic rejection: Less code, history or team than the request lists.
- By submitting, you acknowledge the Expert and Applicant Privacy Notice. Questions can be directed to the platform support button or your RustLabs email contact.
- Alternative submission: describe the codebase if it is not on GitHub.
- RustLabs states that connecting GitHub is read-only, submissions can be withdrawn, and nothing is shared without the owner's agreement.
Where you can work
Country eligibility has not been provided. Confirm with the employer.
Remote does not always mean work from any country. Always check the employer’s location and working-hour requirements.

