Kiroween 2026 (the “Hackathon”) Official Rules
Rules translations: Bahasa Indonesia
NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR WIN. A PURCHASE OR PAYMENT WILL NOT INCREASE YOUR CHANCES OF WINNING.
SUBMISSION OF ANY ENTRY CONSTITUTES AGREEMENT TO THESE OFFICIAL RULES AS A CONTRACT BETWEEN ENTRANT (AND EACH INDIVIDUAL MEMBER OF ENTRANT), THE HACKATHON SPONSOR, AND DEVPOST.
1. Dates and Timing
Registration Period: October 13, 2026 (8:30 am Pacific Time) – December 4, 2026 (2:00 pm Pacific Time) (“Registration Period”).
Submission Period: October 30, 2026 (9:00 am Pacific Time) – December 4, 2026 (2:00 pm Pacific Time) (“Submission Period”).
No extensions will be granted. Late Submissions will not be accepted.
Judging Period: December 16, 2026 (1:00 pm Pacific Time) – January 29, 2027 (1:00 pm Pacific Time) (“Judging Period”).
Winners Announced: On or around February 3, 2027 (9:00 am Pacific Time).
2. Sponsor and Administrator (“Promotional Entities”)
Sponsor: Amazon Web Services, 2121 7th Ave, Seattle, Washington 98121, United States
Administrator: Devpost, Inc. (“Devpost”), 250 Broadway, Floor 24, New York, NY 10007
3. 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”);
- Teams of Eligible Individuals, maximum 3 participants per team (“Teams”); and
- Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry.
(the above are collectively, “Entrants”)
An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis. If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.
The Hackathon IS NOT open to:
- Individuals who are residents of, or Organizations domiciled in, 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 the province of Quebec, Argentina, Australia, Brazil, Italy, Philippines, Russia, Cuba, Iran, North Korea, Syria, Belarus, the region of Crimea, the so-called Donetsk People’s Republic region (DNR), the so-called Luhansk People’s Republic region (LNR), the United Arab Emirates and any other country which is comprehensively sanctioned by the U.S. Treasury’s Office of Foreign Assets Control)
- Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotional Entities”).
- Employees, representatives and agents** of such Promotion Entities, and all members of their immediate family or household*
- Any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*
- Any Judge (defined below), or company or individual that employs a Judge
- Any parent company, subsidiary, or other affiliate*** of any organization described above
- Any other individual or organization 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.
4. How To Enter
Entrants may enter by visiting kiroween.devpost.com (“Hackathon Website”) and following the below steps:
- Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to create your Submission.
- Entrants will obtain access to the required developer tools/platform and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the license agreement related thereto. Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon. AWS handles your information in accordance with AWS Privacy Notice.
- Entrants acknowledge and agree that the availability of certain features, AI models, and functionalities within Kiro may vary by geographic region. Entrants are solely responsible for reviewing and complying with all applicable regional restrictions, including without limitation any restrictions on AI model availability and usage, as published on the official Kiro website (https://kiro.dev) or such other URL as may be designated by the Sponsor from time to time (collectively, the "Regional Restrictions"). The Sponsor makes no representation or warranty that all Kiro features, AI models, or functionalities will be available to Entrants in all jurisdictions. Entrants' use of Kiro in connection with this Hackathon is subject to, and conditioned upon compliance with, all such Regional Restrictions. Any Hackathon submission that relies on features or models not available in the Entrant's region shall be the sole responsibility of the Entrant, and the Sponsor shall have no liability arising from or related to any such regional limitations.
- Entrants (Eligible Individuals, including each member of a Team) may be provided with a one-time allotment of 4,000 Kiro credits for the duration of their participation throughout the Hackathon submission period. No additional usage benefits will be provided. To receive Kiro credits, Entrants must request through the Credit Request Form and fill out all information accurately, including Kiro user ID or AWS account ID with Entrant’s associated Kiro account and relevant project details. Incorrect Kiro user IDs or AWS account IDs may not be approved to receive credits. Credit requests must be submitted by Tuesday, December 1, 2026 at 12:00 pm Pacific Time. Credits must be redeemed by Friday, December 4, 2026, after which all unredeemed credit codes expire. Expired credit codes will not be replaced. Redeemed credits expire on Thursday, December 31, 2026 at 11:59 pm Pacific Time. Credit request form submissions will be reviewed before credit distribution and may be rejected if suspicious or fraudulent activity is suspected, at the Promotional Entities’ sole discretion. Please allow 48 business hours for credit request form review and credit distribution. Disputes must be escalated through the Hackathon Manager listed on the Hackathon Website.
- To be considered for the Best Startup Project Bonus Prize, confirm that you are a founder of the startup, and include your LinkedIn profile and startup website. Sponsor will review submissions and reserves the right to determine eligibility based on submitted details at their sole discretion.
- To be considered for any of the Hackathon category Best Student Project Bonus Prize, indicate which category you are submitting your student project for and confirm that you and, if a team, your team members are attending classes in a recognised academic institution by providing your LinkedIn profiles, student emails, year and degree, and school name. All members of a submitting team must be students to qualify. Sponsor or Administrator may request proof of current enrollment before awarding the prize. If requested proof is not received in a timely manner, your project may be disqualified for Best Student Project consideration.
- To be considered for the Social Blitz Bonus Prize, post on any social platform starting your post with required hashtag #KiroweenHackathon26 (such as X, LinkedIn, IG, or TikTok). The post must start with the hashtag before the rest of the post content to be eligible. Include your favorite thing about Kiro with a description of how it changed the way you approached development. To be considered, you must post during the submission period, use the required #KiroweenHackathon26 hashtag at the start of the post, and provide a link to your social post in the Submission Form. This Hackathon is in no way sponsored, endorsed, administered by, or associated with any social media platform, including but not limited to X, LinkedIn, Instagram, or TikTok.
- To be considered for the Bonus Blog Prize, write and publish a public blog post about Kiro and your project build on any third-party blog platform during the Submission Period, and provide the URL to your post. The blog post must mention it is being written as part of the Kiroween 2026 hackathon to be eligible.
- To be considered for the Best Ghost of Kiroween Past Bonus Prize, confirm that you registered for Kiroween 2025 in the Submission Form. Sponsor and Devpost will verify eligibility against Kiroween 2025 records. Your 2026 Project must be newly created during the Submission Period.
- To be considered for the Best Kiro Crew App Bonus Prize, provide a writeup describing the features and functionality of your Kiro Crew app with a public URL to the code repository for the app on GitHub. Your Kiro Crew app must be newly created during the Submission Period.
- Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Submission Period and follow the requirements below.
Project Requirements
What to Create: Entrants must build a working software application using Kiro (IDE, CLI, Web, and/or Kiro Crew) and submit it into one of the following categories (each a “Project”). Insufficient use of Kiro will result in disqualification at the Judges’ sole discretion.
- Resurrection: Bring your favorite dead technology back to life. Reimagine obsolete tech with today’s innovations or solving tomorrow's problems.
- Frankenstein: Stitch together a chimera of technologies into one app. Bring together seemingly incompatible elements to build something unexpectedly powerful.
- Skeleton Crew: Build a skeleton code template lean enough to be clear but flexible enough to support various use cases. Show us its versatility with two distinct applications from your foundation.
- Costume Contest: Build any app but show us a haunting user interface that’s polished and unforgettable. Bring in spooky design elements that enhance your app’s function.
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.
Platforms: A submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements.
New Projects Only: Projects must be newly created by the Entrant after the start of the Hackathon Submission Period. Participants may use standard development resources, including frameworks, libraries, starter templates, but must disclose any other pre-existing code or work incorporated into the Project. The work described and submitted must have been built during the Submission Period.
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 using Kiro and meets the above Project Requirements.
- Provide a URL to your functional application(s). If login credentials are needed for judges to test the project, add any necessary login credentials and instructions within the Devpost Submission Form.
- Include a text description that explains the features and functionality of your Project.
- Include a demonstration video of your Project. The video portion of the Submission:
- should be less than three (3) minutes. Judges are not required to watch beyond three minutes
- should include footage that shows the Project functioning on the device for which it was built
- must be uploaded to and made publicly visible on YouTube 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 public URL to your code repository on GitHub (NOT GitLab or BitBucket) 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).
- Your repo must contain the /.kiro directory at the root of the project to show usage of Kiro such as specs, hooks, and steering. Do NOT add the /.kiro directory or sub-folders to your .gitignore, as this could disqualify your submission.
- Identify which category and bonus category you are submitting into.
- For Skeleton Crew projects only: Your repo must contain 2 separate repo folders for the 2 separate applications.
- For the Startup Project Bonus Prizes only: Confirm that you are a founder of the startup, and include your LinkedIn profile and startup website.
- For the Best Student Project Bonus Prize only: Confirm that you and, if a team, your team members are attending classes in a recognised academic institution by providing your LinkedIn profiles, student emails, year and degree, and school name.
- For the Best Kiro Crew App Bonus Prize only: Provide the URL to your GitHub repo with the Kiro Crew app and a description of its features and functionality.
- For the Social Blitz Bonus Prize only: Provide the URL to your post on any social platform and use the hashtag #KiroweenHackathon26 (such as X, LI, IG, or TikTok) that shares your favorite thing about Kiro with a description of how it changed the way you approached development. To be considered, you must post during the submission period and use the required hashtag at the beginning of the post.
- For the Bonus Blog Prize only: Provide the URL to your public blog post about Kiro. The blog must mention it is being written as part of the Kiroween 2026 hackathon and be published during the submission period.
- 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.:
- Kiro IDE, CLI, Web, Crew? How did they differ, if you tried multiple?
- Custom agents: Did you create or use any custom agents? Which Kiro app did you try them in? How did they impact your build?
- 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?
- Property-based testing (PBT): Did PBT help catch any issues you might have missed with unit tests? What kind of requirements did you enable PBT for?
- 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?
Multiple Submissions
An Entrant may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and Devpost in their sole discretion.
Submission ownership
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.
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 and testing instructions in the designated field of the Submission Form, which is visible only to the Sponsor, Administrator, and Judges. 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.
Failure to provide access to the Project for testing when requested may result in disqualification.
Language Requirements
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.
Team Representation
If a team or organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a team or organization you represent and warrant that you are the Representative authorized to act on behalf of your team or organization.
Intellectual Property
Your Submission must: (a) be your (or your Team, or Organization’s) original work product; (b) be solely owned by you, your Team, your Organization 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.
5. Submission Modifications
Draft Submissions
Prior to the end of the Submission Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the Submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the Project in your Devpost portfolio.
Modifications
After the Submission Period, the Sponsor and Devpost 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 Devpost permits.
6. Judges & Criteria
Sponsor and Administrator reserve the sole right to determine the eligibility and judging methodologies for all submissions. This process may utilize expert panels, peer review, automated AI-driven analysis, or any combination thereof to ensure efficient, fair, and objective evaluation. Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the Sponsor or third parties, may or may not be listed individually 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 Sponsor.
Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the Project reasonably fits the theme and reasonably applies the required tools featured in the Hackathon.
Stage Two) All Submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):
-
Potential Impact (20% - 10 points)
Does the project make a credible case for solving a real problem for a real audience? Does the solution address that problem based on what’s demonstrated? How useful, intuitive, and accessible is it? Would someone actually use this? -
Technological Implementation (20% - 10 points)
How thoroughly and skillfully does the project use Kiro? Was there a thoughtful strategy to AI development? Was a variety of Kiro tools used impactfully? Does the project show a deep understanding of Kiro features? Was there experimentation? -
Design (20% - 10 points)
Does the project deliver a complete, coherent product experience, not just a technical proof of concept? Is the design intuitive, polished, and intentional? -
Innovation/Idea (20% - 10 points)
How creative and novel is the concept, and does the project differ from existing concepts? Are any unusual technologies or public resources (like datasets) leveraged or combined in a unique way? -
Presentation (20% - 10 points)
Does the video clearly demonstrate the project working end-to-end? Does the pitch communicate what problem is solved, who it’s for, and why it matters? Is the overall presentation easy to follow? Is the presentation creative and memorable?
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.
- Overall Prizes will be awarded to the highest-scoring eligible Submissions across all categories.
- Category Prizes will be awarded to the highest-scoring eligible Submission in each category indicated in the Project Submission based on the same Judging Criteria.
- Best Startup Project Bonus Prize will be awarded to the highest-scoring eligible Submission with an eligible Startup profile and required details shared in the Project Submission.
- Best Ghost of Kiroween Past Bonus Prize will be awarded to the highest-scoring eligible Submission that indicates 2025 Kiroween participation and is verified by Devpost.
- Best Kiro Crew App Bonus Prizes will be evaluated by the Kiro team from among the top 50 eligible Submissions that include a Kiro Crew app GitHub repo link. The top Kiro Crew app will be evaluated at the sole discretion of the Kiro team based on the value/usefulness and technical innovation/idea.
- Best Student Project for each category will be awarded to the highest-scoring eligible Submission in the category indicated in the Project Submission and also includes eligible student details in the Submission.
- Best Demo Bonus Prize will be awarded to the highest-scoring eligible Submission in the Presentation criterion that is also in the top 10% of overall eligible Submission scores. Any ties will be reviewed according to the Tie Breaking rules for the Presentation criterion alone.
- Blog Post Bonus Prizes will be awarded to the top 100 highest-scoring eligible Submissions that included a public blog post about Kiro published during the hackathon submission period with the required mention of Kiroween Hackathon 2026. If fewer than 100 Submissions qualify, leftover prizes will not be awarded.
- Social Blitz Bonus Prizes will be awarded to 5 eligible Submissions that include links to a public social post with the required #KiroweenHackathon26 hashtag at the beginning of the post. The Kiro team will evaluate based on the quality of the post content (original thoughts vs AI writing, interesting insights or learnings about Kiro), the quality of any post assets (images or videos), and select the top 5 at their sole discretion. Social profiles that do not match other submission details may be disqualified at the Promotional Entities’ sole discretion.
Tie Breaking
If two or more Submissions are tied, the Judges will re-evaluate the tied Submissions from scratch using a 20-point scoring maximum for each criterion instead of the original 10 points. If the tie persists, this process will repeat with a +10-point maximum for each criterion for each round of tie-breaking required until a winner emerges.
7. 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 Sponsor and Devpost 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 Submission Period and for three years thereafter. Some Submission components may be displayed to the public. Other Submission materials may be viewed by the Sponsor, Devpost, 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.
8. Prizes
|
Prize Name |
Prize Items |
Quantity |
Eligible Submissions |
|
Overall Prizes |
|||
|
1st Place |
$30,000 USD |
1 |
All Eligible Submissions |
|
2nd Place |
$20,000 USD |
1 |
All Eligible Submissions |
|
3rd Place |
$10,000 USD |
1 |
All Eligible Submissions |
|
Category Prizes |
|||
|
Best Resurrection |
$5,000 USD |
1 |
All Eligible Submissions submitted into the Resurrection category |
|
Best Frankenstein |
$5,000 USD |
1 |
All Eligible Submissions submitted into the Frankenstein category |
|
Best Skeleton Crew |
$5,000 USD |
1 |
All Eligible Submissions submitted into the Skeleton Crew category |
|
Best Costume Contest |
$5,000 USD |
1 |
All Eligible Submissions submitted into the Costume Contest category |
|
Bonus Prizes |
|||
|
Best Startup Project |
$10,000 USD |
1 |
All Eligible Submissions who submit with an Eligible Startup Profile |
|
Best Ghost of Kiroween Past |
$2,000 USD |
1 |
All Eligible Submissions from Entrants who registered for Kiroween 2025. Sponsor and Devpost will verify registration against Kiroween 2025 records. |
|
Best Kiro Crew App |
$1,000 USD |
1 |
All Eligible Submissions that include a separate repo submission to a Kiro Crew app (GitHub account must match overall submission) |
|
Best Student Project - 1 per category |
1-Year Kiro Pro Max subscription** $1,500 USD |
4 |
All Eligible Student Submissions |
|
Bonus: Best Demo |
$1,000 USD |
1 |
All Eligible Submissions |
|
Bonus Blog Prize |
2,000 bonus Kiro credits (not a subscription) |
100 |
All Eligible Submissions that publish a public blog post mentioning the Kiroween Hackathon 2026 on a third-party platform |
|
Social Blitz Prize |
3-month Kiro Pro+ subscription |
5 |
5 Eligible Submissions that include a link to a publicly visible social post (must start with required hashtag #KiroweenHackathon26). |
IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:
- An eligible Project can win one (1) Overall Prize OR 1 Category Prize AND any number of Bonus Prizes.
- **The Kiro subscription is provided by Sponsor and is subject to Sponsor’s applicable terms.
Substitutions & Changes: Prizes are non-transferable by the winner. Sponsor and Administrator in their sole discretion have the right to make a prize substitution of equivalent or greater value. Administrator will not award a prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Entrants or Submissions for a specific prize.
Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. No Submission or Entrant shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Administrator.
Prize Delivery: Prizes will be payable to the Entrant, if an individual; to the Entrant’s Representative, if a Team; or to the Organization, if the Entrant is an Organization. It will be the responsibility of the winning Entrant’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed to the winning Entrant’s address (if an individual) or the Representative’s address (if a Team or Organization), or sent electronically to the Entrant, Entrant’s Representative, or Organization’s bank account, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. The deadline for returning the Required Forms to the Administrator is ten (10) business days after the Required Forms are sent. Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification of the Entrant, or forfeiture of a Prize. Prizes will be delivered within 60 days of the Administrator’s receipt of the completed Required Forms.
Fees & Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees or currency exchange fees. Winners (and in the case of Team or Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents may be required to provide a completed form W-9 and residents of other countries may be required to provide a completed W-8BEN form. Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. The Sponsor, Devpost, and/or Prize provider reserves the right to withhold a portion of the prize amount to comply with the tax laws of the United States or other Sponsor jurisdiction, or those of a winner’s jurisdiction.
By accepting the prize, you confirm that your receipt is neither prohibited nor inconsistent with any applicable laws, regulations, or binding orders, including applicable ethics or procurement rules, your receipt will not create a conflict of interest for AWS or Administrator, and there are no ongoing competitive procurements for which your receipt of this benefit could conflict AWS or Administrator from participating in the competition.
The Hackathon is sponsored by AWS. AWS and its affiliates and licensors will not be liable to you under any cause of action or theory of liability relating to the Hackathon, even if a party has been advised of the possibility of such damages, for (a) indirect, incidental, special, consequential, or exemplary damages, or (b) lost profits, revenues, customers, opportunities, or goodwill. In any case, AWS and its affiliates' and licensors' aggregate liability under these Official Rules will not exceed USD $100. The limitations in this paragraph shall apply only to the maximum extent permitted by applicable law.
You will be responsible, as required under applicable law, for identifying, filing and paying all taxes and other governmental fees and charges (and any penalties, interest, and other additions thereto) that may be imposed on them with respect to the transactions under this Terms and Conditions. Administrator may deduct or withhold any taxes that the Administrator may be legally obligated to deduct or withhold from any benefits provided to you under this Terms and Conditions, and benefits provided to you as reduced by such deductions or withholdings will constitute full award of benefits to you under this Terms and Conditions. You may also be required to sign and return certain tax documentation. Where applicable, Administrator may require winners to provide additional tax information, as required by law to Administrator before receiving their prize and tax reporting may be required. Tax identity information may be collected by completion of IRS Forms W-8/W-9 which each winner will be required to complete and sign to verify certain tax information to Administrator before receiving their Prize. Failure to return such tax documentation will result in forfeiture of the Prize.
9. Entry Conditions and Release
By entering the Hackathon, you (and, if you are entering on behalf of a Team, Organization, each participating member) agree(s) to the following:
The relationship between you, the Entrant, and the Sponsor and Administrator, is not a confidential, fiduciary, or other special relationship.
You will be bound by and comply with these Official Rules and the decisions of the Sponsor, Administrator, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.
You release, indemnify, defend and hold harmless the Promotional Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to an Entrant’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules.
Without limiting the foregoing, the Released Parties shall have no liability in connection with:
Any incorrect or inaccurate information, whether caused by the Sponsor or Administrator’s electronic or printing error, or by any of the equipment or programming associated with or utilized in the Hackathon;
Technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;
Unauthorized human intervention in any part of the entry process or the Hackathon;
Technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or
Any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Entrant’s participation in the Hackathon or receipt or use or misuse of any Prize.
The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Entrants. Proof of sending or submitting the aforementioned will not be deemed to be proof of receipt by the Sponsor or Administrator. If for any reason any Entrant’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Entrant’s sole remedy is to request the opportunity to resubmit its Submission. Such a request must be made promptly after the Entrant knows or should have known there was a problem and will be determined at the sole discretion of the Sponsor.
10. Publicity
By participating in the Hackathon, Entrant consents to the promotion and display of the Entrant’s Submission, and to the use of personal information about themselves for promotional purposes, by the Sponsor, Administrator, and third parties acting on their behalf. Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes but is not limited to advertising and promotional purposes.
11. General Conditions
Once the Submission Period has begun, no material changes to the judging criteria, eligibility requirements, or prize structure will be made without notification to all registered participants.
Sponsor and Administrator reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control.
Sponsor and Administrator reserve the right in their sole discretion to disqualify any individual or Entrant if it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.
Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should the Sponsor or Administrator suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to requiring an Entrant to cooperate with an investigation and referral to criminal and civil law enforcement authorities.
If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to the Hackathon Submission form, Hackathon Website, or advertising, the terms and conditions of the Official Rules shall prevail.
The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Entrant, the Sponsor and Administrator. The Sponsor and Administrator will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting.
If at any time prior to the deadline, an Entrant or prospective Entrant believes that any term in the Official Rules is or may be ambiguous, they must submit a written request for clarification.
The Sponsor or Administrator’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to an Entrant, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the Sponsor’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.
Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, trade-names, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Sponsor and/or Administrator. All rights are reserved. Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Sponsor or Administrator’s intellectual property shall be solely to the extent provided for in these Official Rules.
12. Limitations of Liability
By entering, all Entrants (including, in the case of a Team or Organization, all participating members) agree to release the Released Parties from any and all liability in connection with the Prizes or Entrant’s participation in the Hackathon. Provided, however, that any liability limitation regarding gross negligence or intentional acts, or events of death or body injury shall not be applicable in jurisdictions where such limitation is not legal.
13. Disputes
Except where prohibited by law, as a condition of participating in this Hackathon, Entrant agrees that:
Any and all disputes and causes of action arising out of or connected with this Hackathon, or any Prizes awarded, shall be resolved individually, without resort to any form of class action lawsuit, and exclusively by final and binding arbitration under the rules of the American Arbitration Association and held at the AAA regional office nearest the contestant;
The Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and
Judgment upon such arbitration award may be entered in any court having jurisdiction.
Under no circumstances will Entrant be permitted to obtain awards for, and Entrant hereby waives all rights to claim, punitive, incidental or consequential damages, or any other damages, including attorneys’ fees, other than contestant’s actual out-of-pocket expenses (i.e., costs associated with entering this Hackathon), and Entrant further waives all rights to have damages multiplied or increased.
All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, or the rights and obligations of the Entrant and Sponsor in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of New York, USA without regard to New York choice of law rules.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATIONS OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OF LIABILITY MAY NOT APPLY TO YOU.
14. Additional Terms
Please review the Devpost Terms of Service at https://info.devpost.com/terms for additional rules that apply to your participation in the Hackathon and more generally your use of the Hackathon Website. Such Terms of Service are incorporated by reference into these Official Rules, including that the term "Poster" in the Terms of Service shall mean the same as "Sponsor" in these Official Rules. If there is a conflict between the Terms of Service and these Official Rules, these Official Rules shall control with respect to this Hackathon only.
15. Entrant’s Personal Information
Information collected from Entrants is subject to Devpost’s Privacy Policy, which is available at https://info.devpost.com/privacy.
For questions, send an email to [email protected].
