Judging Criteria
Here's exactly how your project gets scored. No mysteries, no surprises.
Each submission is reviewed by our panel of judges. They score each category from 0–100, and those scores are weighted to produce your final rating. Judging is anonymous, so judges only see your Reference ID.
Scoring Categories
Technical Execution
25%Code quality, architecture, and how well it actually works. Consider using durable execution for reliable workflows. Platforms like Temporal can help with that.
Innovation & Creativity
20%Originality of the idea and creative problem-solving. Think outside the box: unique approaches, unexpected combinations of tech, or solving a problem nobody else thought of.
Theme Relevance
15%How well the project ties into the hackathon theme. Make the connection clear and intentional, not just a surface-level mention. The deeper the integration, the better.
Documentation
10%Clear README, architecture overview, setup instructions, security report, and project explanation. Document it like someone else needs to understand and run it without asking you questions.
Security
15%Secure coding practices and responsible data handling. Include an Aikido security scan report for bonus points.
UX / UI
15%User experience, design, and overall polish. Is it intuitive to use? Does it look like someone cared? Smooth interactions, clear navigation, and a cohesive visual style all count here.
How It Works
1. Multiple Judges
Your project is scored by multiple judges independently. Their scores are averaged to produce the final rating. Judges may score in one or more rounds at the organiser's discretion.
2. Anonymous Review
Judges don't see your name, team name, or identity. They only get your Reference ID and what you've submitted (description, images, video, repo link). If you want to stay fully anonymous, only include your reference number in your submissions and consider creating a separate GitHub account so judges can't identify you from your repo.
3. What Judges See
Judges are not required to run your code. They may judge based solely on the text description, screenshots, and video you provide. Your demo should showcase the project's UI/UX, walk through the architecture for technical execution, explain what the project does and why, and touch on the security measures you've taken. Make that submission count.
4. Tie-Breaking
If two submissions tie, the one with the higher Technical Execution score wins. If still tied, Innovation & Creativity is the next tiebreaker, then remaining categories in order. If everything is still level, the judges vote.
Tips to Score Well
- →Write a killer README. Documentation is 10% of your score. Don't skip it.
- →Record a demo video. Judges might not run your code, so show them what it does.
- →Think about security. Include an Aikido security scan report to show the judges you take it seriously.
- →Tie it to the theme. Theme Relevance is its own category. Make the connection obvious.
Now go read the rules and meet the judges