2 Fast 2 MCP

The Racing Rulebook

  1. This event is part of the Hack All February series. You can participate solo or with a team of up to 4 members. Teams can change per hackathon - you don't need to have the same team members for all hackathons in February. You can even participate solo in some hackathons and with a team in others.
  2. The more Archestra features you use, the faster you'll cross the finish line. Using Archestra's MCP-based agent orchestration, centralized runtime, security guardrails, observability, and deployment capabilities is recommended to maximize your chances of winning prizes, including cash rewards and exclusive swag. Check out the resources section.
  3. You must build a new project during the hackathon. Simply modifying an existing codebase or app is not allowed - your engine should be cold before the green light drops.
  4. All design elements, code, and assets for your project must be created during the event. You may use third-party tools, frameworks, open-source libraries, public APIs, and publicly available assets (e.g., Creative Commons images, fonts, or music).
  5. Teams can plan and discuss ideas in advance, but coding and design work should start only after the hackathon begins. Written notes, sketches, and diagrams are allowed before kickoff - just like studying the track before race day.
  6. Projects must involve building software (hardware components are optional).
  7. Teams may consist of 1–4 members.
  8. Prize distribution: All prizes will be distributed equally among winning team members, with a maximum team size of four. The total prize amount will be divided by the number of team members to ensure fairness. If a project wins as a solo submission, the participant will receive 50% of the listed prize amount, which will still be higher than the amount an individual would receive in a team setting. This policy ensures fair payouts while encouraging collaborative participation.
  9. While interviews don't guarantee a job, they provide a genuine chance to showcase your skills and access potential roles.
  10. Any intellectual property developed during the hackathon belongs to the team that created it. Teams are encouraged to agree internally on IP ownership, though this is not mandatory.
  11. Please treat all participants with respect. Act kindly and professionally - in this family, we ride together. Harassment, discrimination, or exclusionary behavior of any kind will not be tolerated. If you see something concerning, notify an organizer immediately.
  12. Failure to follow these rules or the Code of Conduct may result in disqualification and a permanent pit stop from future events.