Hacklanta

Hacklanta is open to current college and university students who can provide a valid .edu email address.

Every participant must:

1. Complete the official application at hacklanta.dev
2. Receive an acceptance
3. Complete any required follow-up RSVP

Registering on Devpost alone does not register you for Hacklanta.

Anyone who has not completed the official Hacklanta registration process will not be eligible to attend, participate, be judged, or receive a prize.

Organizers may verify participant identity, student status, acceptance status, and registration information.

• Teams may have between one and four members.
• Each team member must register individually at hacklanta.dev.
• Teammate emails must correspond to the team's official applications.
• A participant may only compete as a member of one submitted team.

Substantial work on the submitted project must take place during the official hacking period.

Teams may use open-source software, APIs, frameworks, AI systems, hardware platforms, templates, and previously built general-purpose tools when they are properly disclosed.

Teams may not submit a previously completed project or misrepresent work created before Hacklanta.

Submissions must include:

• A working prototype
• An accessible source-code repository
• A complete project description
• A demo video
• All other items listed in the Submission Requirements

Teams are responsible for confirming that their submission was successfully received before the deadline. Late or inaccessible submissions may not be judged.

Participants retain ownership of the projects they create.

Teams must have permission to use all submitted code, datasets, media, trademarks, and other materials. Projects must comply with applicable licenses and may not use stolen, plagiarized, or unlawfully obtained material.

Hacklanta is committed to an inclusive, respectful, and harassment-free event.

The following will not be tolerated:

• Harassment or discrimination
• Threats or intimidation
• Deliberate disruption
• Unsafe behavior
• Interference with another team's project
• Violation of venue or university policies

Participants must follow Georgia State University policies, organizer instructions, and applicable laws.

Concerns should be reported immediately to a Hacklanta organizer or official@progsu.com.

Organizers may remove or disqualify participants whose conduct threatens the safety, fairness, or integrity of the event.

Final prize categories, sponsor challenges, and award details will be announced before or during Hacklanta.

Eligibility for a sponsor challenge may require the use of a particular technology, API, platform, or theme. Teams are responsible for reviewing the requirements of every category they enter.

A project may only receive an award if every listed team member satisfies the participant eligibility and registration requirements.

Projects will be evaluated using the criteria associated with their selected track or challenge.

General considerations may include:

• Clarity and importance of the problem
• Originality and creativity
• Technical execution
• Functionality and completeness
• Product design and user experience
• Practical value or potential impact
• Quality of the demonstration and presentation
• Fit with the selected track or sponsor challenge
• Appropriate use of any required sponsor technology

Judges may inspect the submission, repository, live demo, and video and may ask the team questions during judging.

Finalists and winners will be selected by the judging panel in consultation with Hacklanta organizers. Ties and unusual eligibility questions will be resolved by the organizers.

Judging decisions are final.