Teams may consist of 2–4 participants.

Each participant may only be a member of one team.

Teams may submit one project to CrownHacks.

Projects may compete in one track or sponsor challenge only.

Projects may not be simultaneously submitted to another hackathon.

All work on the project must take place during the official 40-hour CrownHacks hacking period.

Previously completed projects may not be submitted. Pre-existing general-purpose code, templates, libraries, frameworks, and other components may be used but must be clearly disclosed.

AI tools and LLMs are allowed. Teams may use AI-assisted development tools or incorporate AI models and APIs into their projects. 

Projects must include a link to their source code. Repositories must be accessible to judges during the judging period.

Teams may not copy another team's project or submit work primarily created by someone outside the team.

All team members must meet CrownHacks participant eligibility requirements and be officially registered for the event.

Projects must be submitted on Devpost before the submission deadline. Late submissions may not be eligible for judging.

Judging will take place in person at UNC Charlotte. Teams must be prepared to demonstrate their project to judges.

Projects must follow the CrownHacks Code of Conduct and UNC Charlotte policies.

CrownHacks organizers reserve the right to determine project eligibility and disqualify submissions that violate these rules.