Rules & Guidelines
Read carefully before the event. Violations may lead to disqualification.
12-Hour Sprint
The hackathon runs for exactly 12 hours. All code must be committed before the final deadline at 5:00 PM.
Team Size
Teams must consist of 2-4 members. Each member must register with a valid email address.
GitHub Mandatory
All code must be pushed to a public GitHub repository. Commit frequency is tracked and scored.
Original Work Only
All code must be written during the hackathon. Pre-existing code, boilerplates, and templates are not allowed.
Problem Lock-In
Once you lock your problem statement, it cannot be changed. You can lock it anytime during the selection window.
Judging Criteria
Teams are scored on 6 criteria totaling 70 points: Git Repo, Frontend, Backend, Solutions, Monetization, and Team Leader Info.
Scoring Breakdown
Frequently Asked Questions
Can I use external libraries and frameworks?
Yes, you can use any open-source library, framework, or API. However, the core logic must be your own.
What if my team has connectivity issues?
Inform the admin immediately. An extension may be granted at the admin's discretion.
Can I change my problem statement after locking?
No. Once locked, it is permanent. You can lock it anytime during the selection window.
What happens if two teams pick the same problem?
Multiple teams can work on the same problem statement. Judging is independent.
Do we need to deploy our project?
A working demo is preferred but not mandatory. A clear README with setup instructions is required.
How is the Git Repo score calculated?
The system evaluates your GitHub repository setup, organization, and commit history. Regular, meaningful commits are considered.