The Kalvium Hackathon
One hackathon. One weekend. We're putting Kalvium on the world's map.
The hackathon has wrapped
Registrations, check-ins and final submissions all closed on Sunday, June 14, 2026 at 5:00 PM IST. The guide below is kept as a record of how the weekend ran — winners are announced in the community within 5 days.
Results land in the community group
All updates happen in the community group on WhatsApp — the schedule, announcements, kickoff link, and help during the build. Join it and turn on notifications; we post everything there.
Why we're doing this
This isn't just another campus event. We're bringing together the best student builders from across India to show the world what this generation can do. One stage, every region, building in the open. We want everyone to be part of it — not to watch, but to build, ship, and be seen. This is the kind of thing people remember being part of years later.
What to build
Solve a real problem, in the open
- 1Build something that solves a real-world problem — something a real person would actually use, not a demo for the sake of a demo.
- 2Build it in public. Share your progress as you go so the whole community can follow along and root for you.
- 3Be clear about three things: what you're solving, why it matters, and how someone would use it.
How the weekend runs
Friday 8 PM to Sunday 10 AM
- 1Fri · Jun 128:00 PM IST
Kickoff & orientation
We open with a 30-minute orientation — the brief, the rules, the prizes, and your questions answered. Then the clock starts and everyone begins building. No gate to start — if you registered, you're in.
- Be on the call at 8:00 PM for the 30-minute orientation.
- Building begins at 8:30 PM.
- Optional: post a short idea/pitch video before kickoff — it earns bonus points.
- 2Fri nightFirst couple of hours
Lock & refine your idea
Before you write much code, sharpen it. Pick your problem, narrow the scope to something you can actually finish in the time, and get a quick gut-check in the group. A tight idea beats a big one.
- Pick one real problem and one real user.
- Cut the scope down to fit a 38-hour build.
- Share your idea in the group for fast feedback before you go heads-down.
- 3Sat · Jun 13All day · check-ins
Full build day
Heads-down building. Keep it in the open — post your progress and submit a quick check-in so we can follow your journey. Stuck or have a question? Drop it in the community group; that's where we post every update too.
- Build your project and submit your daily check-in.
- Optional: post a short progress video for bonus points.
- Ask for help anytime in the community group.
- 4Sun · Jun 1410:00 AM sharp
Submission
Submit your project before 10:00 AM Sunday — all four required items: GitHub repo, problem & solution doc, live link, and a demo video. A pitch video earns bonus points, but the demo video is required.
- Submit all four before 10:00 AM Sunday: repo · doc · live link · demo video.
- You can re-submit any time before the deadline to update a link.
- 5ResultsWithin 5 days
Winners announced
We review every submission and announce the winners within 5 days. The top 3 teams take the ₹20,000 in Codex credits, the special categories win more Codex credits, and the winning campus takes the Campus Award.
How it's judged
Evaluation criteria
Problem & solution fit
Does it solve a real, clearly-defined problem? Can a judge picture a real person using it today?
Execution
Did you actually build it, and does it work? Live link, working core flow, real commits across the weekend.
AI leverage
Is the AI doing the real work — the product itself, not a wrapper? Used well, and on real, messy input.
Originality
A fresh angle, insight, or approach — not a straight copy of something that already exists.
Build in public
An honest, consistent journey — your check-ins on Friday night and Saturday told the story.
Your check-ins are scored — that's the Build in public criterion above. A pitch video before kickoff (and a progress clip with a check-in) is an optional bonus. Your final submission needs a demo video — that one's required, not a bonus.
Prizes & rewards
₹20,000+ in Codex credits
₹20,000 in Codex credits is split across the top 3 teams. The special category winners take home more Codex credits on top — it's all credits, for everyone who wins.
1st place
₹10,000
2nd place
₹5,000
3rd place
₹5,000
More ways to win
You don't have to place top 3 to walk away with something. Special categories — each rewarded in Codex credits.
Best Build-in-Public
The team that shared the best progress story along the way.
People's Choice
Voted by the community — the build everyone loved.
Best Solo Builder
For the strongest one-person team in the room.
Breakthrough Idea
The boldest take on a real-world problem.
The Campus Award — a first
We've never given an award to an entire campus before. This is the first one ever. The Kalvium campus that registers the most teams wins it — a campus-wide recognition and certificate that belongs to every single builder there. Rally your friends, fill the leaderboard, and be the campus that puts its name in history. Be part of it.
See how it went in the community →What every team that enters gets
You don't leave empty-handed
- ✓A certificate of participation for every registered team.
- ✓Real practice pitching your idea and building in public — a skill you keep.
- ✓A spot in the Age of AGI builder community.
- ✓Top teams featured on the Age of AGI website for the world to see.
During the build
Progress, in public
During the build, post a quick check-in (Friday night and Saturday) so we can follow your progress and keep you building in the open. A short progress video is optional and earns bonus points. Stuck or have a question? Drop it in the community group — that's where we post all updates too.
Check-ins and final submissions are closed
Every required item — GitHub repo, problem & solution doc, live link and demo video — was due by the deadline. Winners are announced in the community within 5 days.
Loading the final numbers…