1. The Event
The data never stops flowing, and neither do the innovators connecting the digital dots. As part of the grand return of the ultimate tech celebration of the year, the IUT Computer Society presents one of its most dynamic and creative events: the Agentic AI Hackathon. Keep your endpoints ready, assemble your team, and get ready to build under pressure as raw data transforms into real-world solutions. Let the requests route and your innovations speak!
2. Competition Structure
The campus will transform into an electrifying battleground where you will race against the clock to design powerful applications. The competition is divided into two distinct phases:
Phase 1: Preliminary Round
A fast-paced online screening round lasting 4 hours.
Phase 2: Main Development Sprint
An intense, on-site development sprint lasting 8 hours, where qualifying teams will build their solutions under pressure.
3. Rules & Guidelines
3.1 Team Composition
- Team Size: Each team must consist of 1 to 3 members.
- Eligibility: All participants must be currently pursuing an undergraduate degree.
- Team Formation: Cross-university teams are allowed; students from different institutions may form a team together.
- Participation Limit: No participant may be a member of more than one team.
3.2 Project Rules
- Participants must create a new GitHub repository on-site immediately after the Opening Ceremony and submit it at the end of the competition.
- The project must be developed entirely on the day of the hackathon.
- Any project developed fully or partially before the event will not be accepted.
- Teams may use publicly available open-source libraries, frameworks, APIs, and SDKs.
- All open-source tools must be mentioned in the project README.
- No pre-written source code may be brought into the venue.
4. Technical Guidelines
What is Allowed
- Any publicly available APIs, SDKs, or your own trained AI/ML models.
- Pre-trained models accessed via API, such as OpenAI, Hugging Face, Azure Cognitive Services, Google Cloud AI, and Anthropic Claude API.
- Any programming language, web framework, or mobile development toolkit.
- Cloud services including AWS, Google Cloud, Azure, and similar platforms.
What is NOT Allowed
- Pre-written source code of any kind brought into the venue.
- Projects developed, even partially, before the hackathon began.
5. Facilities
What We Provide
- Internet: Wi-Fi connectivity will be provided throughout the venue for the duration of the hackathon.
- Food: Meals and refreshments will be provided for all participants for the duration of the overnight stay.
- Security: The venue will be secured throughout the event by the organizing team and campus security.
What Participants Should Bring
- Laptop(s): Each team member should bring a personal laptop.
- Chargers: Laptop chargers and any device-specific chargers.
- Multiplugs / Power Strips: To manage multiple devices at a single workstation.
- Mobile Data (Backup): Strongly recommended due to potential infrastructural constraints.
- Other Devices: Any other necessary personal or development devices, such as external keyboards or mouse.
6. Submission Requirements
Every team must submit all required deliverables within the allotted time. Submissions after the deadline will not be considered under any circumstances.
| Deliverable | Details |
|---|---|
| GitHub Repository | Public repo with all code written during the hackathon. Include a README.md with setup, run instructions, and tech stack. |
| Demonstration | Teams must demonstrate a working prototype of their developed application before the judges. |
7. Code of Conduct
The IUT Computer Society is committed to providing a safe, inclusive, and respectful environment.
Expected Behaviour
Treat all individuals with respect and professionalism at all times. Foster a collaborative spirit, share knowledge, and support fellow participants.
Prohibited Conduct
Harassment, intimidation, bullying, or discrimination of any kind against any person is strictly forbidden. Any form of plagiarism, academic dishonesty, or misrepresentation of work will lead to disqualification.
Enforcement
If a violation is suspected, the concerned team will be formally notified and given a reasonable opportunity to respond. Disqualified teams forfeit all prizes and recognition.
8. Contact Information
For any queries, please contact: