- All work must be started and completed during the hackathon
(April 3, 9:30 PM to April 5, 10:30 AM MST) - Pre-written code beyond basic boilerplate will not be allowed
- Projects must show meaningful development during the event
- Judges may ask teams to explain or modify their code during evaluation
- You may use public frameworks and AI or LLM tools
- Tools must be disclosed in your README.md
- Core logic, system design, and problem solving must be implemented by your team
- Projects that are primarily generated, simple wrappers, or UI reskins of other projects on the internet will be disqualified
- Do not plagiarize or reuse prior projects
- Do not submit the same project to another concurrent hackathon
- Do not submit work that is not your own
- All contributors must be listed on Devpost
- We reserve the right to cross-check submissions across platforms
- Plagiarism detection tools will be used
- Violations may result in scoring penalties or disqualification and reporting to MLH
- Remove all API keys and secrets from your repository
- Only include .env templates, never real credentials
- Submissions missing required security practices may be penalized or disqualified
- Judging will take place in person on April 5
- Schedule: innovationhacks.dev/#schedule
- Format: science fair style (3 minutes per judge per team)
- Projects must function live during judging
- Be prepared to demo immediately when a judge arrives
- Updates will be shared via Discord (#announcements)
- Open to students only
- 18+ only
- Organizers, volunteers, and mentors are not eligible for prizes
- All participants must comply with the MLH Code of Conduct
All announcements will be made via Discord: