Teams

Teams can have 1–4 members. Solo projects are welcome. Each participant may compete on only one team. Make sure to list every teammate on the Devpost submission.

Project Work

Projects that are submitted for judging must be started during the official hacking period. You may form teams, discuss ideas, and plan your project beforehand, but you cannot start writing project code before hacking officially starts. We will use tools and measures to make sure all teams follow this rule. If we detect that your project code was written before the official hacking period, your team will be disqualified.

Previously started projects are not eligible. Your project also cannot have been submitted to another event.

Stop development when the hacking period ends. You may prepare your presentation afterward, but you may not add features or fix code.

AI Tools

AI tools are allowed only where their use complies with the resource requirements above and any rules for the prize category you enter.

In your submission disclose which tools you used and how you used them.

Submission Requirements

Your project must be publicly available and maintained in a version-controlled repository. GitHub, GitLab, Bitbucket, or another code hosting service is acceptable.

In your submission include:

  • Every team member.
  • A description of what you built and how it works.
  • A link to your public code repository.
  • Instructions needed to run or test the project.
  • Credits for resources and tools used.
  • The prize categories you’re entering.
  • Be honest about what works and what doesn’t. Clearly showing mock data, simulations, and unfinished features.

Judging and Prizes

Teams must attend in-person judging to be considered for prizes.

You will have 3 minutes to pitch and demo your project, followed by 2 minutes for judges to ask questions about your project.

Review the requirements for each prize category you enter. Sponsor categories may have additional requirements.

Judges will evaluate work completed during the hackathon. Judging decisions are final.

Code of Conduct

All participants must follow the MLH Code of Conduct, UB Hacking’s event policies, and venue rules.

Harassment, discrimination, plagiarism, sabotage, and unauthorized access to devices, accounts, networks, or data are prohibited.

Report misconduct or safety concerns to an organizer. Rule violations may result in disqualification or complete removal from the event.