ElevenHacks
LeaderboardGuideSign in
ElevenHacks

A season of 11 weekly hackathons by ElevenLabs. Build, ship, and compete.

ElevenLabs

  • ElevenLabs.io
  • Documentation
  • API Reference
  • Blog

Resources

  • Leaderboard
  • Submission Guide
  • GitHub
  • Discord
  • Community

Social

  • X (Twitter)
  • LinkedIn
  • YouTube
  • Instagram

© 2026 ElevenLabs. All rights reserved.

PrivacyOfficial Rules

ElevenLabs x Kiro Hackathon Rules

Rules for Kiro-specific prizes

These rules apply toward Kiro-specific challenge tracks or criteria for Kiro related prizes. If these rules conflict in some part with the parent (“administrator”) event hackathon rules where Kiro is a sponsor, the parent event rules apply.

Eligibility

The hackathon is open to:

  • Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”)

The above are collectively “Entrants.”

The hackathon is NOT open to:

  • Individuals who are residents of a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the hackathon (including, but not limited to, Brazil, Quebec, Russia, Crimea, Cuba, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control)
  • Any individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*
  • Individuals who are currently employees, representatives, or agents of a hackathon sponsor and/or administrator
  • Any parent company, subsidiary, or other affiliate*** of any organization described above
  • Judges of the hackathon
  • Sponsor or affiliate
  • Any other individual whose participation in the hackathon would create, in the sole discretion of the Sponsor and/or Administrator, a real or apparent conflict of interest

*The members of an individual's immediate family include the individual's spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual's household include any other person that shares the same residence as the individual for at least three (3) months out of the year.

**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.

***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.

Project Requirements

Please refer to the ElevenLabs hackathon submission guide.

Functionality:

The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.

New & Existing:

Projects must be newly created by the Entrant.

Third Party Integrations:

If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them in accordance with any terms and conditions or licensing requirements of the tool.

Submission Requirements

Submissions to the Hackathon must meet the following requirements:

  • Include a Project built with Kiro, meets the above Project Requirements, and abides by the ElevenLabs submission guide and Kiro challenge.
  • Include a text description that should explain the features and functionality of your Project.
  • Include a demonstration video of your Project. The video portion of the Submission:
    • must follow the requirements of the ElevenLabs submission guide
    • must be uploaded to and made publicly visible on YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and
    • must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.
  • Provide a URL to your open source code repository for judging and testing.
    • The repository must contain all necessary source code, assets, and instructions required for the project to be functional. The repository must be public and open source by including an open source license file. This license should be detectable and visible at the top of the repository page (in the About section).
    • The code repository must be public with an approved OSI Open Source License (instructions here on how to add it)
    • Your repo must contain the /.kiro directory at the root of the project to show usage of specs, hooks, steering, etc. Do NOT add the /.kiro directory or sub-folders to your .gitignore, as this could disqualify your submission.
  • Identify which category you are submitting into.
  • Provide a write up on how Kiro was used. Judges must understand how effectively you used Kiro to develop your project. Show us your next-level understanding of Kiro features, e.g.:
    • Vibe coding: How did you structure your conversations with Kiro to build your project? What was the most impressive code generation Kiro helped you with?
    • Agent hooks: What specific workflows did you automate with Kiro hooks? How did these hooks improve your development process?
    • Spec-driven development: How did you structure your spec for Kiro to implement? How did the spec-driven approach improve your development process? How did this compare to vibe coding?
    • Steering docs: How did you leverage steering to improve Kiro's responses? Was there a particular strategy that made the biggest difference?
    • MCP: How did extending Kiro's capabilities help you build your project? What sort of features or workflow improvements did MCP enable that otherwise would have been difficult or impossible?
    • Kiro powers: Which powers did you leverage for bundled best practices and expertise in Kiro? Did you use any third-party tooling or integrations you wouldn't have otherwise?
  • Social media posts: When posting your submission on social media, tag @kirodotdev and @elevenlabsio and use the hashtags #ElevenHacks and #CodeWithKiro.

Submissions must be the original work of the Entrant, be solely owned by the Entrant, and not violate the IP rights of any other person or entity.

All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.

Modifying a project after the submission period

Once the Submission Period has ended, you may not make any changes or alterations to your Submission. The Sponsor and Administrator may permit you to modify part of your Submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Sponsor and Administrator permit.

Testing

Access must be provided to an Entrant's working Project for judging and testing by providing a link to a website, functioning demo, or a test build. If Entrant's website is private, Entrant must include login credentials in its testing instructions. The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. Judges are not required to test the Project and may choose to judge based solely on the text description, images, and video provided in the Submission.

If the Project includes software that runs on proprietary or third party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request.

Intellectual Property

Your Submission must: (a) be your original work product; (b) be solely owned by you with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. An Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant's work product and the result of the Entrant's ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Hackathon, you represent, warrant, and agree that your Submission meets these requirements.

Financial or Preferential Support

A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.

Judges and Criteria

Eligible submissions will be evaluated by a panel of judges selected by the Administrator. Judges may be employees of the sponsor or third parties, may or may not be individually listed on the hackathon website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the Administrator and Sponsor.

The ElevenLabs x Kiro hackathon follows this overall scoring rubric:

  • Social posts: +50 pts per platform (X, LinkedIn, Instagram, TikTok)
  • Placement: 1st place +400 pts, 2nd +200 pts, 3rd +150 pts
  • Most Viral: +200 pts for the post with the most engagement
  • Most Popular: +200 pts (community vote via emoji reacts)

For Social posts, see submission requirements above to ensure your post follows the rules to be eligible.

For Placement, judges will refer to both the ElevenLabs submission guide and the below general criteria for Kiro project submissions according to the sole and absolute discretion of the judges:

Potential Value

Includes the extent to which the solution can be widely useful, easy to use, accessible, etc. Examples of considerations could include:

  • How unique or saturated the market is with these kinds of applications/solutions
  • Whether the UI is intuitive and brings the app functionality to the next level
  • If there is a clear need, extensibility, or other type of scalability of the project

Implementation

Includes how well the idea is leveraging Kiro. Judges must understand how effectively Kiro was used to develop the project. Examples of effective usage include but are not limited to:

  • The variety of Kiro features/capabilities impactful in project development
  • The depth of understanding or benefit gained from a given Kiro feature/capability
  • The amount of experimentation and strategic decisions made in how Kiro features/capabilities are brought into the individual's development workflow.

Quality and Design

Includes creativity, originality, responsible design, and polished design of the project, such as:

  • Finding and using unique public resources like datasets
  • Solving a challenge in a unique way
  • Building in delightful UI experiences or other thoughtful choices

The scores from the Judges will determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.

Intellectual Property Rights

All Submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an entry, entrants agree that the Sponsor will have a fully paid, non-exclusive license to use such entry for judging the entry. Entrants agree that the sponsor and Administrator shall have the right to promote the Submission and use the name, likeness, voice and image of all individuals contributing to a Submission, in any materials promoting or publicizing the Hackathon and its results, during the Hackathon Period and for three years thereafter. Some Submission components may be displayed to the public. Other Submission materials may be viewed by the sponsor, Administrator, and judges for screening and evaluation. By submitting an entry or accepting any prize, entrants represent and warrant that (a) submitted content is not copyrighted, protected by trade secret or otherwise subject to third party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless entrant is the owner of such rights or has permission from their rightful owner to post the content; and (b) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.