📅 Dates & Location

  • Event Date: February 14–15, 2026 (Example)

  • Registration Deadline: February 10, 2026

  • Mode: Hybrid / Online / In-Person at [Venue Name, e.g., Agra College]

✅ Eligibility

  • Participants: Open to all undergraduate and postgraduate students from any university or college.

  • Team Size: You can participate individually or in a team of up to 4 members.

  • Background: No specific major is required. We welcome developers, designers, and problem solvers of all kinds!

  • Residency: Open to participants from [Your Region/Global].

📝 Project and Submission Requirements

  • Fresh Code Rule: All code must be written during the hackathon. You may use open-source libraries and frameworks, but the core logic must be developed within the 24-hour timeframe.

  • Submission Platform: All projects must be submitted via Devfolio/GitHub [or your chosen platform] by the deadline.

  • Deliverables:

    1. Source Code: A link to a public GitHub repository.

    2. Demo Video: A 2-minute video walkthrough of your project.

    3. Presentation: A short slide deck explaining the problem, solution, and tech stack.

  • Tech Stack: You are free to use any programming language, framework, or technology (Web, App, Blockchain, AI/ML, AR/VR, etc.).

🏆 Prizes

  • 🥇 1st Place: 2 Domain  + Certificate of Excellence

  • Participate: Certificate

  • 🎨 Best UI/UX Design: Special recognition for the team with the best "Vibe" and aesthetics.

  • 💡 Most Innovative Idea: For the project that thinks strictly outside the box.

  • All Participants: Participation Certificates & Digital Badges.

⚖️ Judging Criteria and Winner Selection

Our panel of industry experts will evaluate projects based on the following metrics:

  1. Innovation (30%): How unique and original is the idea? Does it solve a real-world problem in a new way?

  2. Functionality (25%): Does the code actually work? Is the demo smooth, or is it buggy?

  3. The "Vibe" / Design (25%): Since this is Vibe Code, UI/UX is critical. Is the interface intuitive, aesthetically pleasing, and user-friendly?

  4. Technical Complexity (10%): How difficult was the technical challenge? Did the team use advanced tech stacks effectively?

  5. Presentation (10%): How well did the team pitch their idea? Was the problem and solution clearly communicated?