Selection: Only the 30 teams officially confirmed via email are eligible to compete.
Team Size: Teams must consist of 2 to 5 members. Single-person entries are not permitted for the main event to ensure multidisciplinary collaboration.
Communication & Presence:
Email availability and quick replies are required for all participants to receive official documentation and high-level updates.
Joining the Discord server is heavily recommended, as it serves as the main platform for real-time announcements, Q&A, networking, and support tickets.
All members must be registered on the participant confirmation form and the devpost submission.
Attendance: Participation in the Kickoff, Keynotes, and Mentoring sessions is heavily recommended to ensure your team is aligned with the challenge goals and technical requirements.
2. Project Requirements & "Fresh Code"
Alignment: Projects must address one of the four Challenge Tracks (Public Health, Mental Health, Media for Health, or Obesity) and align with UN SDG 3 and 10.
New Solutions: Must be designed and built entirely during the 48-hour hackathon window.
Early-Stage Projects: Teams with pre-existing work must submit a detailed log of the project's state before the weekend. The jury will only grade the "Delta"—the significant new features or pivots developed during the hackathon.
Originality: Open-source libraries are allowed but must be credited. Misrepresenting existing code as your own is grounds for disqualification.
3. Technical Rules & AI Usage
AI Tools: Use of AI is highly encouraged for code generation or as core features.
Credits: Access codes (Lovable, n8n, ElevenLabs) are generous but finite.
Redemption: Codes should be redeemed online as soon as possible. We cannot guarantee validity if you wait until later days.
Maximizing Credits: In Lovable, you may transfer project ownership to another team member to utilize the individual credits of the entire team.
Security:DO NOT SHARE ACCESS CODES ONLINE or in public channels.
Failsafes: Connect your code to GitHub immediately so you don't lose your work when the hackathon credits expire.
4. Submission & The "Happy Path"
Deadline: Final submission to Devpost is 16:30 CET on Sunday, March 29.
Owner: The team leader should be the owner of the Devpost project. They must add all members as "Collaborators" using the email address they regularly read (ideally the same one from the registration form).
Backup Recommendation:Save your current state on devpost and create a final backup a few hours before the deadline (e.g., 14:00 CET) to avoid last-minute technical outages.
Prototypes: You must demonstrate a "Happy Path"—a functional Proof of Concept showing the core mechanism of impact.
5. Pitching & Live Presentation
Requirement: Presentation during your assigned pitching time slot is strictly required. Failure to appear during your slot may result in disqualification.
Format: 3 minutes for the presentation/demo + 2 minutes for Jury Q&A via Zoom.
Punctuality & Prep: Be punctual and fully prepared beforehand. You must clearly designate:
Who is responsible for screen sharing?
What specific features/slides will be shown?
Who is speaking and the specific points they will cover.
Language: All pitches and materials must be in English.
The "Co-Pilot": Designate a co-presenter to take over screen sharing immediately if the primary speaker’s internet fails.
Backup: We strongly recommend having a pre-recorded video of your demo ready in case of live API failure.
6. Intellectual Property & Ethics
Ownership: Participants retain 100% ownership of their code and Intellectual Property.
Marketing: You grant organizers a non-exclusive license to use your project name and demo visuals for marketing and event recaps.
Medical Disclaimer: Any project providing health-related advice must display the following: "This is a hackathon prototype for educational purposes and is not a substitute for professional medical advice."
7. Code of Conduct
Professionalism: Respect all participants, mentors, and judges at all times.
Honesty: Do not overpromise. If a feature is simulated or hardcoded, be transparent with the jury.
