SuperAI NEXT Hackathon

Introduction 36 hours. $200K in prizes. Build something that matters. NEXT Hackathon is SuperAI's flagship hackathon — 200 builders, equipped with the right tools, mentors, and network to go from idea to working demo in a single sprint. The top 5 teams demo live on the WEKA stage at SuperAI. The Theme Build anything — but make it agentic. We don't care what problem you solve. We care how your agents solve it. This hackathon is about pushing the frontier of autonomous systems. Your project can tackle any domain — productivity, finance, healthcare, creative tools, infrastructure, whatever — as long as agents are doing real work at the core of it. Prizes Main Track — Top 5 Winners The top 5 teams will demo live on the WEKA stage in front of 10,000 SuperAI attendees. Each finalist team receives: - AWS: $25,000 in AWS credits - Vercel: $1,500 in Vercel credits - Razer: Every team member receives a gift bag (~$500 value) containing a ProClick v2 Mouse, Pro Glide XXL Mousemat, and Pro Type Ergo keyboard Stage eligibility requirement: To compete for the Top 5, your project must integrate both AWS and Vercel. Partner Prizes Open to all teams, regardless of whether you qualify for the main track. Top 5 finalists are also eligible. - Best use of Stripe — $1,000 in Stripe credits, Top 3 teams - Best use of Exa — $1,000 in Exa credits, Top 3 teams Integration with Stripe and Exa is optional. But if you use them well, you can win on top of everything else. Schedule Day 1 — 9 June - 9am: Registration + Breakfast - 10am: ⚠️ Hackathon Kickoff Briefing — Do not be late - 10:15am: AWS Workshop - 10:45am: Vercel Workshop - 11:15am: Stripe Workshop - 11:35am: Exa Workshop - 12pm: Hacking Begins - 1pm: Lunch served - 7pm: Dinner served - 11:59pm: Midnight snack served Day 2 — 10 June - All day: 💻 Hacking continues / SuperAI Day 1 begins - 7pm: Dinner - 11:59pm: ✅ Project submissions due + Supper *Breakfast, lunch and snacks are available during conference hours on Level 5.* Day 3 — 11 June - 12pm: Top 5 Finalists announced - 5:30pm: 🎤 Top 5 Finalist Demos + prize announcements on WEKA stage + group photo Teams can be 1–4 members. Solo entries are welcome, but we strongly recommend forming a team. 36 hours goes fast, and a great idea needs hands to build it. What You Get All hackers receive access to the following on day one: Credits - AWS: Temporary AWS accounts with full service access + XX Kiro credits - Vercel: $100 in credits per team - Stripe: $250 in credits per team - Exa: $XX in credits per team Hardware - Razer: Keyboard, mouse, and mousemat on every table The room: The hackathon space is built to keep you in the zone for the full 36 hours: - All meals catered — breakfast, lunch, dinner, and supper - Snacks, drinks, and hot coffee available all day - Bean bags and rest areas Judging Criteria Submissions will be evaluated across four dimensions: - Agentic Architecture — Quality and thoughtfulness of your agent design: reasoning, autonomy, tool use, and how well the architecture fits the problem - Technical Execution — Does it work? Is it well-built? Complexity and polish relative to the time constraint - Impact & Use Case — Does it solve a real problem? How compelling is the application? - Demo & Presentation — Clarity of the pitch, quality of the demo/product, and how well the team communicates what they built Submission Guidelines Deadline: 12am on 11 June (i.e. 11:59pm on 10 June). No late entries will be accepted. What to submit All teams must include: 1. GitHub repo — public, or with judge access granted 2. Project link — live URL or hosted demo 3. Presentation slides — Google Drive link to a .ppt or .keynote file (see notes below) Agentic Architecture Disclosure Every submission must also answer the following. This is how judges evaluate the core of your project: - Agent Overview — What agent(s) did you build? What is their purpose? - Autonomy & Decision-Making — How does your agent decide what to do next? What reasoning, planning, or tool-use patterns does it employ? - Actions & Tool Use — What actions can your agent take? What tools, APIs, or environments does it interact with? - Orchestration — If multi-agent: how do your agents coordinate, delegate, or communicate? - Human-in-the-Loop *(if applicable)* — Where does a human intervene, approve, or override? - Failure Handling — How does your agent recover from errors or unexpected states? A note on presentation slides: The presentation slides will be used if you're selected as a Top 5 finalist and pitch on the WEKA stage. Questions? Join the NEXT Hackathon Telegram group here.