Start anywhere. Build anything. Explore ideas, scope your build, prepare and see what matters to the jury, all in one guide. Applications: 14 September–10 October 2026.
Tell us what you want to build or what you can bring. Applications are online, free to enter, and open to everyone from 14 September to 10 October 2026.
You can start anywhere.
Submit an idea, problem or skill you’d bring to a build. No finished product or polished pitch deck required. Have a prototype? Include a public link in the optional work-link field. Don’t have one? That’s fine.
Developers, designers, founders, researchers, students, operators and anyone who wants to build are welcome. Apply solo or with a team, then form or join a team before the physical build.
Bring a startup idea, solve something you have experienced, build an AI agent, make a useful tool, or try something weird. These are starting points, not limits. Build whatever you think should exist.
IDEA TO WORKING SOFTWARE.
INSPIRATION, NOT OFFICIAL COMPETITION TRACKS
Make AI do moreBuild something where AI acts, reasons, creates or operates.
How could AI solve a real problem instead of becoming another chatbot?
Start with a real task, give the system meaningful agency, and make its work visible enough to test and trust.
Reinvent how we workChange how people work, create, learn or collaborate.
Which familiar workflow should work differently?
Choose one concrete workflow, remove its biggest friction, and build an end-to-end experience people can actually use.
Solve something realStart with a problem you have actually seen.
What does your campus, city, industry or everyday life need?
Ground the build in direct experience, test it with the people who face the problem, and improve what matters.
Your idea. Your build.No theme. No assigned problem. Build what should exist.
What do you believe is worth making?
Bring a startup idea, make a useful tool or try something weird. The suggested directions are starting points, not limits.
One person. One problem. One useful flow.
Start smaller than you think.
Name the person you are helping and the task they need to finish. Make that task work end to end before adding another feature.
Show the difficult part.
Test with realistic inputs and an awkward case, not only the happy path. Make failures understandable. Be honest about assumptions and limitations.
Use data you can use.
Use synthetic, public, or authorized data. Think through privacy and accessibility as part of the product, not as a slide at the end.
Hackyard Build 2026MAKE IT WORKBUILD SOMETHING REAL
✳
Idea
Start with something worth making: an idea, a problem or a question. You do not need the whole answer.
Build
Make the smallest version that actually works. Do not spend the weekend making slides.
Test
Use it. Break it. Improve it. Find what does not work and fix what matters.
Show
Do not tell us what it could do. Show us what it does.
Make the demo easy to follow.
Show the problem, then the working flow. Say what you built, what depends on an external service, and what still needs work. Test the demo path and be ready to explain your technical decisions. When it is time to present, show what the product does, not only what it could do.
Show the work. Explain the why.
Good builds deserve a fair look. What matters is what you built, the problem, the ingenuity of your approach, and its potential.
Final judging guidance will be shared before the physical build.
Build
Did you actually make something that works?
40%
Problem
Does it solve a real or meaningful problem?
20%
Ingenuity
Is there something clever, original, or thoughtful about the approach?
20%
Potential
Is there a reason to keep building it after the event?
20%
How projects are assessed
Build
How much did you actually make? Does the core experience work?
Problem
Does it solve a real or meaningful problem?
Ingenuity
Is there something clever, original, or thoughtful about the approach?
Potential
Is there a reason to keep building it after the event?
Judge the build, not the pitch.
From preparation to presentation.
Drop your idea, get selected, find your people, then build in person at IIT Guwahati on 24–25 October 2026.
01
14 September → 10 October
Apply
Bring an idea, a problem or a skill. No finished product required.
View steps for Apply
Drop your starting point
Describe your idea, the problem you want to solve or the skills you bring. A rough starting point is enough.
02
After applications
Get selected
We review applications and invite selected builders to the physical build.
View steps for Get selected
Application review
Applying is not a guarantee of selection. Hackyard will contact selected builders with the next steps.
03
Before the build
Team up
Find your people. Form a team. Prepare your build.
View steps for Team up
Meet your teammates
Come with a team or meet other selected builders. Find complementary skills and refine what you want to make together.
04
24–25 October 2026
The build
In person at IIT Guwahati. Build. Ship. Show.
View steps for The build
Build
Make the smallest version that actually works.
Test
Use it, break it and improve what matters.
05
After the event
Keep building
Get seen. Get opportunities. Keep building.
View steps for Keep building
Get recognized
Selected builders can receive a badge, public profile and Build 2026 credential.
Stay connected
Projects can be showcased and builders can access selected future Hackyard opportunities.
Know before you go.
The physical build is at IIT Guwahati on 24–25 October 2026. Event entry, build space, and internet are free. Food and accommodation are available at a very nominal participant fee.
Need accessibility support?
Ask the organizing team about access or participation. Detailed arrival information and exact food and accommodation fees will be shared with selected builders before they travel, so you can plan your stay. Travel is not listed as an included event benefit.
A builder experience where ideas, problems, skills and ambitious people come together to make something real.
Are applications free?
Yes. Applications are free, open to everyone and run online from 14 September to 10 October 2026.
Do I need a finished product?
No. Submit an idea, problem or skill you would bring to a build. No finished product or polished pitch deck is required. If you already have a prototype, you can include a public link in the optional work-link field.
What happens after I apply?
After applications close, Hackyard reviews submissions and invites selected builders to the physical build. Before the build, you can meet other selected builders, form a team and prepare. The physical build is at IIT Guwahati on 24–25 October 2026.
Can I participate alone?
Yes. You can apply solo or with a team, then form or join a team before the final build.
Do I need to be a developer?
No. Building is not limited to code. Designers, researchers, operators, founders and people with strong problem-solving skills are welcome.
Building
Who gets the $100 AI Build Credits?
If selected, your team gets $100 in AI Build Credits. Applicants who are not selected do not receive credits. Selected teams may also get access to selected AI, API, cloud and developer tools from our partners.
What can I build?
Anything worth building. Follow one of our suggested directions or build something completely your own. AI is a powerful building layer, not a requirement.
Physical build
Where and when is the physical build?
The physical build is at IIT Guwahati on 24–25 October 2026. It will run for approximately 12–24 hours. Event entry is free; food and accommodation will be available at a very nominal participant fee, shared before travel.
When will prizes be announced?
Final prize details will be announced as they are confirmed. Final judging criteria will be announced before the physical build.