Who owns your hackathon code?
When you enter a hackathon, you accept its rules. Some rules let the sponsor use your project only to judge it. Others let the sponsor use it in marketing, require you to open-source it, or let the sponsor build products from it.
We read the rules of each hand-checked event and give it one of four levels. The level is shown on the homepage and on the event page.
The four levels
Level 1: You keep it
The sponsor uses your project only to judge it. Example: Postman API Hack.
Level 2: Promotion
The sponsor may also use your name, photo and voice in its marketing, sometimes for years. Example: Nebius x NVIDIA.
Level 3: Open source
You must release your code under an open-source license. Example: SANS AI Cybersecurity.
Level 4: Commercial rights
The sponsor may build and sell products from your project, forever and worldwide. Example: GitLab AI Hackathon.
How to find these terms in the rules
The terms are usually in a section called Intellectual property, Ownership, License, Publicity or Submission rights. These words point to the higher levels:
- "perpetual", "irrevocable", "worldwide", "royalty-free": the rights the sponsor takes do not end, and you cannot take them back.
- "assign" or "transfer": ownership itself moves to the sponsor, not just permission to use the project.
- "name, likeness, voice" or "publicity": the sponsor can use you in its marketing.
- "open-source license" together with a named license such as MIT or Apache 2.0: you must publish your code under that license.
Before you enter
- Read the rules yourself. Rules change after we check them. The level we show is our reading on the date shown on the event.
- Check your job contract. If it covers side projects or inventions, your employer may have a claim on what you build.
- Know what you bring in. Code, data and models you did not write have their own licenses. The event's rules do not change them.
What "Not checked yet" means
Events imported from listing sites have not had their rules read by hand. They show Not checked yet instead of a level. Read the rules on the event page before you enter. See How we check AI hackathons.
Questions
Is this legal advice?
No. It is a guide to help you notice which rules matter. For a legal question about a specific event, ask a lawyer.
Can a hackathon take my code without saying so?
The rights a sponsor gets are the ones in the rules you accept when you enter. That is why the rules are worth reading before you sign up.
Which level is best?
It depends on what you want from the project. If you plan to keep building it or sell it, Level 1 leaves you the most freedom.