UNBOUND '26
First Edition Online Hackathon
A two-week digital sanctuary for developers, designers, and open-source visionaries. Break free from constraints, build with integrity, and shape the future under the banner of Open Innovation.
COUNTDOWN TO KICKOFF
KICKOFF DATE: JUNE 12, 2026
THE CORE STATS
Important parameters of the competition
TRACK
Open Innovation
Build anything that solves a real problem using open technology.
FORMAT
100% Online
Collaborate from anywhere. Submissions and judging are virtual.
DURATION
2 Weeks
A marathon, not a sprint. Plenty of time to refine your codebase.
ELIGIBILITY
All College Students
Undergraduates & postgraduates from any stream or institution.
THE TIMELINE
Hackathon Kickoff
June 12, 2026 — Prompt announcements and repository activation. Official coding starts!
Mid-way Milestone Check
June 19, 2026 — Self-check your commits and ensure license parameters are in place.
Submissions Close
June 26, 2026 (11:59 PM IST) — Final project push, video submission, and README finalization.
Results Announcement
July 2026 — Final placements, compliance audits, and certificates distribution.
PRIZES & CERTIFICATES
Exciting Prizes + Certificates
All teams that submit a valid, compliant, and license-approved FOSS project will receive official participation certificates from FOSS CLUB PU.
Certificates will be provided + exciting prizes!
Specific prize details and categories will be announced soon.
THE CONSTITUTION OF UNBOUND
Rules governing the hackathon. Strict compliance is required.
Eligibility & Teams
Strictly open to current college students (UG/PG). Teams of 1 to 4 members. Cross-college teams are permitted. A participant can only join one team.
Open Source Mandate
Every project repository must contain an OSI-approved license (e.g. MIT, Apache 2.0, GPL v3) in a root LICENSE file. No license means no evaluation.
No Proprietary Lock-in
The core functionality must not depend heavily on paid, closed-source third-party software or proprietary APIs. Open-source libraries and APIs are highly encouraged.
Timeline & Integrity
All core development must happen exclusively between June 12 and June 26, 2026. Pre-built projects are strictly prohibited. Extensions must only evaluate commits in this window.
Commit History
Teams must maintain a clear, active Git history showing progression. Last-minute "ghost pushes" of massive codeblocks without history are grounds for disqualification.
Plagiarism & Attribution
Code duplication without proper attribution will result in an immediate ban. If utilizing LLMs to generate sections of code, you must include clear attributions.
THE FINISH LINE
To successfully qualify for evaluation, you must submit the following before June 26:
Public Repository
A public Git repository hosted on GitHub, GitLab, or Codeberg, showing active development history.
Production README
A comprehensive README.md explaining the problem, the solution, the tech stack, setup instructions, and local testing guidelines for the jury.
5-Minute Demo Video
A focused video demonstrating working features (no theoretical slide decks). Uploaded to YouTube (public/unlisted) or Google Drive (public access).
PROJECT READINESS CHECKLIST
Use this interactive tool to track your team's compliance with the UNBOUND '26 statutes before submit day.
0 of 7 tasks complete (0% ready)
SPONSORSHIP OPPORTUNITIES
Partner with FOSS CLUB PU to support UNBOUND '26 and empower the student developer community
Support Open Innovation
Enable student developers to build high-impact, open-source software free from proprietary vendor lock-in.
Connect with Top Talent
Get direct exposure to passionate and skilled programmers, designers, and builders across diverse institutions.
Prominent Placement
Feature your organization's logo and mission on our event portal, certificates, publications, and future club events.
Interested in supporting the first edition online hackathon?
Partner With Us fossclubpu@protonmail.comJUDGING & CONDUCT
Read how submissions will be scrutinized and how we maintain academic rigor
Our judging panel reviews codebases carefully using the following parameters:
- Meaningful Problem: How well defined is the problem you chose to solve? We look for a clear description of the problem statement and its significance in your README.
- Codebase Understanding: During our evaluation, you will be expected to demonstrate a deep understanding of your codebase. Be ready to explain architecture, data flows, and code snippets.
- License Integrity: Immediate disqualification for missing root LICENSE files or non-OSI approved licenses.
- Open Source Best Practices: Clean Git logs showing collaborative history, structured files, and zero lock-in to proprietary, closed technologies.
- LLM Attributions: Using tools to assist coding is fine, but clear attributions pointing to what code was AI-assisted must be included.
FOSS Club Pondicherry University stands for inclusivity, collaboration, and ethical engineering:
- Respect & Inclusivity: All interactions on official communication channels must remain professional, helpful, and friendly. Harassment, derogatory remarks, or hate speech will trigger immediate expulsion from the competition.
- Academic Integrity: Plagiarism will result in an immediate, unappealing ban from all future FOSS Club PU hackathons. Do not copy repositories without attribution.
- Absolute Authority: The decisions made by the FOSS CLUB PU organizing committee and the external judging panel regarding evaluations, compliance audits, disqualifications, and final placements are absolute and final.
Common queries about the hackathon:
- Is there a registration fee? No, UNBOUND '26 is completely free and open to all college students.
- Can we form cross-college teams? Yes, members of a team can be from different departments, streams, or different colleges entirely.
- What counts as a "Proprietary Dependency"? For example, using paid APIs (like OpenAI paid tiers without a local fallback, Google Maps paid SDKs) as a core function without open alternatives. Try to use open models (Hugging Face, self-hosted LLMs) or open-source database libraries (SQLite, PostgreSQL).
- Are we allowed to use frameworks? Absolutely. You can use React, Vue, Next.js, Django, Flutter, Rust, etc., as long as your code is open-sourced under an OSI license and written during the hackathon window.
For further queries and support, join our official WhatsApp Group.