Eligibility and identity
Every person applies individually with accurate information. Selection and attendance confirmation are required for the physical build. Accounts, applications and team codes may not be transferred.
Last updated:
Build 2026
rules.
Operating rules for applicants and participants, covering eligibility, ownership, conduct, judging and event operations.
Your work remains yours
You keep ownership of what you build. By submitting, you give Hackyard only the limited permission needed to review your application and, with the stated visibility controls, operate and showcase Build 2026.
Teams
Build solo or in one registered team of 2–4 participants. Every teammate must submit an individual application and connect to the same team code.
Official build window
The physical event is a 24-hour hackathon. Judging focuses on work created or materially advanced during the announced onsite build window.
Pre-existing work
Pre-existing libraries, tools, designs, datasets and project foundations may be used when disclosed. Teams must clearly identify what existed before the event and what they built during the official window.
Originality
Do not present another person's work as your own. Credit collaborators and important dependencies. A reused foundation must be transformed through meaningful onsite work.
Prohibited content
Projects must not facilitate illegal activity, harassment, exploitation, deceptive impersonation, malware, credential theft, non-consensual surveillance, sexual abuse material or other serious harm.
AI, APIs, data and hardware
AI, open source, APIs and hardware are allowed when their terms permit the use. Use public, synthetic or authorized data. Do not expose secrets, personal data or restricted datasets.
Judging
Projects are assessed on Build 40%, Problem 20%, Ingenuity 20% and Potential 20%. Judges review the working build and disclosed dependencies, not only the pitch.
Disqualification
Hackyard may disqualify an application or project for false information, plagiarism, prohibited conduct, unsafe activity, rule evasion, undisclosed pre-built work or interference with judging.
Prizes and credits
Each reward follows its published eligibility. Project rewards are issued once per project unless the sponsor terms explicitly say per member. Partner verification and redemption evidence may be required.
Application privacy and publication
Application answers remain private to review and event operations. A Hackyard public profile is optional and separate. Hackyard must request separate explicit approval before publishing a project showcase; an applicant may decline or withdraw before publication.
Venue and liability
Participants must follow venue, safety, security and equipment instructions. Participation and travel are at the participant's own risk to the extent permitted by law.