Team Formation

 

  • Your team may consist of up to four participants. You may also work by yourself, but you will be judged at the same standards as any other team.
  • All team members must be registered participants of HackKU25, check in, and be present at the event.
  • Don’t worry if you don’t have a team yet! There will be a team formation event after the opening ceremony to find others to hack with. Additionally, there will be a teambuilding channel on Discord to find teammates.

 

Competition Rules

 

  • All code for your project MUST be written during HackKU, between the hours of 8PM on April 4th and 8AM on April 6th.
  • Your entire project must be written and created by only the participants on your team.
  • Your code must be made public on GitHub for judging purposes. We will use your GitHub to verify that all of the rules and deadlines of the competition were followed. All teams may be subject to a code review.

 

Tracks, Challenges, & Prizes

 

  • There will be two main tracks at HackKU25: the General Track, and a Theme Track. (The theme of the Theme Track will be announced during the opening ceremony) Participants must choose ONE of these tracks to submit their project on, and will compete for the prizes associated with that chosen track.

  • There will also be prizes associated with various challenges and company sponsored tracks. Teams may choose to compete for as many or as few of these as they would like, regardless of which of the two main tracks they are competing on.

  • For more specifics, see below.

    Tracks, Challenges & Prizes

 

Submission & Judging

 

  • All projects will be submitted via Devpost.
  • Teams competing for prizes will give a short (5-minute), in-person demo of their project to judges.
  • All teams are encouraged to demo, even if your project is not complete. There is no downside to demoing your project! This is a chance to show off what you accomplished and learned during HackKU.
  • Judging decisions will be confidentially handled by the judges assigned to your project and will be based on your Github code, Devpost submission, and your In-Person Demo.