Rules

Eligibility

• CodeBox Hacks is open to currently enrolled Cal Poly students.

• Teams may have 3–5 members.

• Current CodeBox board members and advisors may not compete because they are judging.

• At least one representative from each team must attend Saturday’s required kickoff and Sunday’s opening at ATL.

• A team that misses check-in may be ineligible for awards.

• Hacking and Devpost submissions close at 2:00 PM Sunday sharp.
• A team may win both a track and best overall.

Project rules

• Teams may begin with an existing idea, but all work submitted to CodeBox Hacks must be completed during the hackathon period.

• Projects must be primarily software. Hardware-only projects and mockup-only submissions are not eligible.

• Projects may also be used for a class, internship, or another competition, as long as the work submitted to this hackathon is completed during the event.

• You may use any tools, APIs, datasets, open-source libraries, and AI assistants.

• Meaningful third-party work must be credited in your Devpost submission.

• Every project must have a public GitHub repository with hackathon-weekend commit history.

• Web applications must be publicly deployed and usable by judges.

• Each team may submit to one track only. The final track selection is made at submission.

• Submissions must include a demo video no longer than 90 seconds.

• Do not include passwords, API keys, or other secrets in your public repository.

Code of Conduct

CodeBox Hacks is a respectful, inclusive, and collaborative event. Harassment, discrimination, intimidation, or disruptive behavior will not be tolerated.

CodeBox organizers may remove participants or disqualify projects that violate these expectations or these rules. Please help make this a welcoming weekend for students of every background and experience level.