top of page

InfiniHacks Rules

To keep our event fun and fair for everyone, we impose a couple of simple rules that all hackers have to follow.

General Rules

No matter what the reason you’re at a hackathon, make sure you’re upholding the spirit of the hackathon by collaborating with other teams, helping beginners, and having fun.


  • To ensure everyone has a smooth experience, we recommend a maximum of 4 members per team

    • Special conditions can be made if a team is larger than 5 members. Contact us and we will review these on a case-by-base basis.

  • All prizes are to be shared between all team members

  • Teams should be made up of exclusively high school or university level students

  • Everyone in the team must respect other teams, mentors, judges, and organizers. All members must agree to the InfiniHacks Code of Conduct!

  • Committee members may not participate in the hackathon, but are allowed to mentor and help other teams.


  • All projects must be created within the duration of the hackathon.

    • If there is a very good reason why you would like to continue an old project, contact us and we can make exceptions on a case-by-case basis.​

    • Teams may come up with ideas outside of the hackathon date, but all code must be written within the given time frame.

  • Cross-Submitting projects is allowed if it is clearly mentioned in the description.

  • ​Teams can use libraries, frameworks, or open-source code in their projects.

    • Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.​

    • Also remember to remove and disable any API keys used in the project after the hackathon is over.

  • All intellectual property developed during the hackathon will belong to the team that developed it. ​

  • Teams may work on projects that have already been done. Not all projects have to be "innovative"

  • All projects must follow the InfiniHacks Code of Conduct!


  • All teams should have a team name, and be registered with Devpost.

  • To be eligible for a prize, all fields on the Devpost submission are recommended to be filled out

  • Projects with code must also be posted on Github and be set to public!

    • This ensures that all projects were completed within the competition.​

    • Projects may be randomly code-reviewed to make sure all code is original work.

  • Teams must stop hacking once the time is up.

    • However, teams are allowed to debug and make small fixes to their programs after time is up.

    • e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that.

    • Making large changes or adding new features is not allowed.​

NOTE: More Submission Guidelines Will Be Released Closer To The Hackathon Date!


  • Prizes are listed as USD. Conversion fees may apply.

  • Although InfiniHacks is based in North America, we will try to accommodate shipping for teams all across the world.

  • Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, behaving in a way that violates the InfiniHacks Code of Conduct or other unsporting behaviour.

    • Disqualified teams are not eligible for a prize.​

  • Sponsor prizes may also be revoked at the discretion of the sponsor in question.​

  • The verdicts of the judges regarding prizes and awards are final.

Judging Criteria

Teams will be judged on these four criteria. Judges will weigh the criteria equally. During judging, participants should try to describe what they did for each criterion in their project.


  • How technically impressive was the hack?

  • What technologies were incorporated into the project?

  • Was the technical problem the team tackled difficult?

  • Did it use a particularly clever technique or did it use many different components?


  • Did the team put thought into the user experience?

  • How well designed is the interface?

  • Is the project easy to use and understand?

Project Goal

  • Did the project try to solve a greater goal?

  • How well did the project fit into its selected track?

  • How can the project be used in a real life situation?

  • How feasible is the project in the real world?

  • How creative or innovative was the solution?

Completion and Learning

  • Does the hack work?

  • Was there a live demo?

  • Did the team achieve everything they wanted?

  • Did the team stretch themselves?

  • Did they try to learn something new?

  • What kind of projects have they worked on before?


The competition is just a part of the hackathon. To make the most out of the event, try something new, teach other people, and make new friends!

bottom of page