What if you could build powerful systems… without writing a single line of code?
NO//CODE: BUILD CHAOS is an intra-college hackathon organized by the Department of IT at BPIT that challenges the traditional idea that coding is the only way to create impactful solutions.
Built around the theme “The System Has Collapsed”, this hackathon pushes participants to rethink how modern digital systems are designed. Instead of relying on conventional development, participants become System Builders—leveraging AI, no-code, and low-code tools to design scalable, real-world solutions.
💡 The IdeaToday’s systems are becoming overly complex, slow, and inaccessible. We believe innovation shouldn’t be limited to those who can code.
This hackathon focuses on:
- System thinking over syntax
- Creativity over complexity
- Execution over theory
Participants build working prototypes that solve real-world problems across domains like:
- FinTech 💰
- EdTech 🎓
- Open Innovation 🌍
- Special Gemini Track 🤖
Requirements
What to Build:
Build on any problem that you think requires a solution
What to Submit:
A GITHUB REPOSITORY IS TO BE SUBMITTED
Prizes
1st Prize
2nd Prize
Best Use of Google Gemini API
Google Swag Kits
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Pradeepto Sarkar
SecOps Analyst, IHG Hotels and Resorts | Associate Program Manager, The Linux Foundation | Founder and CEO, NAMESPACE
Romanch Roshan Singh
Coach@Major League Hacking
Anamika Singh
President @ Anveshan
Judging Criteria
-
Mandatory Rule (Disqualification Clause)
No pre-built projects allowed All work must be started and developed during the hackathon (22nd April hack period) -
Innovation
We’re looking for ideas that are not obvious or overdone. Are you solving a real problem, or just building something trendy? Is your approach different from what already exists? Does your project show creative thinking? -
Implementation
Ideas are easy. Execution is what counts Does your project actually work? How much did you build vs just assemble tools? Is your solution technically solid? -
Feasibility
Can this realistically exist beyond the hackathon? Can it be developed further in the real world? Does it rely on unrealistic assumptions? Can it scale or handle real users? -
Viability
Does your project actually matter? Who will use this? Why would they use it? Does it solve a real need or pain point?
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
