Maximally Vibe a thon will run from December 27 to December 29, 2025.
The event begins at 12:00 AM IST on December 27 and ends at 12:00 AM IST on December 29.
Participants have a total of 48 hours to create, experiment, submit, and explore ideas at their own pace.

You may start at any time within the 48 hour window, but all submissions must be completed before the deadline.

Vibe a thon is open to anyone who enjoys building, tinkering, experimenting, or coding for fun.
You are eligible to participate if you:

Are above the legal age of majority in your country of residence
Have access to a computer and the internet
Can work individually or within a team formed during the event
Agree to the event rules and submission requirements

Participants from all countries are welcome, subject to any applicable local laws.
Beginners, hobbyists, learners, and advanced builders are equally encouraged to join.

You may build anything you want, as long as it is meaningful to you, created during the event, and reflects genuine effort.

Your submission must include:

1. A project title and written description
   This is required. Explain what you built and why you chose to build it.

2. A functional demo or working version
   This can be a hosted link, live prototype, code repository, or any setup that allows judges to understand your idea.

3. Optional video
   You may include a short video demonstration if you want to show flow or interaction more clearly.

4. Optional screenshot
   A single screenshot can be included to highlight the appearance or design of your build.

5. Additional notes
   You may share context about your process, inspirations, experiments, or intentions.

Remix culture is fully allowed.
Participants may build on existing concepts, remix previous projects, or take inspiration from open source work, as long as the new submission clearly reflects new effort during the 48 hour window.

Pre existing libraries, frameworks, boilerplates, and utilities are permitted.
The core work submitted should be created during the event.

Judging focuses on expression, clarity, and originality rather than strict technical scoring.

Projects will be evaluated based on:

1. Creativity
   How original or expressive the idea feels.

2. Vibe and experience
   The overall mood, tone, and intention communicated by the project.

3. Execution
   How well the core idea has been brought to life within the 48 hour period.

4. Clarity
   Whether the submission clearly explains the project and demonstrates its purpose.

5. Exploration and intent
   Whether the project shows curiosity, experimentation, or personal creative direction.

Judges will review submissions independently and make final decisions based on collective evaluation.

These rules serve as suggested guidance.
You should consult a legal professional before finalizing official rules for your hackathon.

1. Originality and remix culture
Participants may create original projects or remix existing ideas.
Using open source work, templates, and prior experiments is permitted, provided the submitted project includes new work created during the event.

2. Team formation
Participants may work solo or as part of a group.
Teams may be formed before or during the event.

3. Event timeline
All core work must be completed within the 48 hour event window.
Preparation, research, scaffolding, or brainstorming may occur in advance.

4. Respectful participation
All participants must maintain a respectful and constructive environment.
Harassment, discrimination, or harmful behavior is not permitted.

5. Submission standards
All submissions must meet the listed requirements and be submitted before the final deadline.

6. Legal compliance
Participants are responsible for ensuring that their work complies with all applicable local, national, and international laws.

7. Prohibited content
Projects may not include harmful, malicious, dangerous, or intentionally harmful systems.

8. Intellectual property
Participants retain ownership of their work.
If a submission is based on or inspired by existing projects, credit must be acknowledged.

If you are hosting an in person version, a separate code of conduct is recommended. A standard template can be adapted if needed.