Submission Requirements

Participants are expected to develop a Minimum Viable Product (MVP) that clearly demonstrates their idea, technical implementation, and potential real-world impact. The project should go beyond a conceptual proposal and include a working prototype such as a web application, mobile application, API, machine learning model, or any functional system that showcases the core functionality of the solution. While projects do not need to be fully production-ready, they should effectively communicate the problem being addressed and provide a tangible demonstration of the solution.

Teams may choose to build within one of the official challenge tracks (to be announced) or pursue a freestyle project of their own design. There are no restrictions on programming languages, frameworks, or tools, allowing participants full flexibility in selecting a tech stack that best suits their idea. Regardless of approach, projects should demonstrate originality, thoughtful design, and meaningful use of technology.

All submissions must be completed through Devpost and include the following components:

• A public GitHub repository containing the complete project code. The repository should be well-organized and include clear instructions for setup, dependencies, and usage.

• A 2–3 minute presentation video that introduces the problem, explains the solution, and includes a demonstration or walkthrough of the working prototype.

• A comprehensive README file within the repository that outlines the project overview, key features, installation steps, usage instructions, and team member contributions. Additional technical details such as system architecture or design decisions are encouraged but optional.

Submissions must represent original work developed during the hackathon period. Projects that consist solely of ideas, slide decks, or incomplete implementations will not be considered. The goal is to showcase a functional and compelling MVP that highlights both technical ability and creative problem-solving.