Frequently Asked Questions
Have questions? We've got answers.
The event is open to all currently enrolled undergraduate and postgraduate students from any discipline. We encourage interdisciplinary teams!
Teams should consist of 3 to 4 members. A diverse team with varied skill sets (e.g., coding, design, subject matter expertise) is highly recommended for a competitive edge.
You need to submit an initial idea outline (max 300 words) and a problem statement (max 150 words) upon registration. However, this idea can be refined during the pre-event workshops and ideation sessions.
Information regarding registration fees, if any, will be announced on the official registration portal. Please check back closer to the registration date.
Each team will be guided by a faculty mentor. Additionally, during the event, there will be sessions with industry experts and experienced researchers who can provide technical and strategic guidance.
You are encouraged to use modern technologies, especially those related to the themes like AI, Machine Learning, AR/VR, and Digital Twins. However, there are no strict limitations, as long as the solution is innovative and addresses the problem statement effectively.
The final submission must include a working prototype (code repository link), a short video demonstration (maximum 3 minutes), and a brief documentation report summarizing your solution and its adherence to the core themes.
Teams retain full ownership of the Intellectual Property (IP) developed during the event. However, by participating, teams grant the event organizers non-exclusive rights to use the project name and images for promotional and reporting purposes.
Yes, dedicated technical mentors and support staff will be available 24/7 through a dedicated communication channel (such as Discord or Slack) to assist with any technical roadblocks or platform issues. Details will be shared upon registration.
You are allowed to use open-source libraries and public APIs. However, the core logic and unique components of the solution must be developed entirely during the hackathon period. All dependencies must be properly cited in your documentation.