about 2 months ago
Final checklist — 3 days left ⏰
The Google Cloud Rapid Agent Hackathon closes on June 11th at 2:00 PM PT. If you're still building, now is the time to finalize and submit. Don't let your work go unrecognized — even a rough-but-functional project is worth submitting.
Final submission checklist
- ✅ Code repository is public with an open source license visible in the About section
- ✅ README includes clear setup and run instructions
- ✅ Demo video is under 3 minutes, uploaded to YouTube or Vimeo, and set to public
- ✅ Text description explains your project's features, tech used, and learnings
- ✅ Hosted project URL is working and accessible to judges
- ✅ Partner track selected: Arize, Dynatrace, Elastic, Fivetran, GitLab, or MongoDB
- ✅ All team members are listed on your submission
A couple of reminders
- You can update your submission right up until the deadline
- Your project must use Gemini + Google Cloud Agent Builder + your chosen partner's MCP server
There's $60,000 in prizes across six tracks and the chance to showcase your work to Google Cloud, the partners, and the broader developer community. Give it everything you've got. See you on the other side. ⚡
Most common mistakes we've seen so far
We want every project to be a success, so here's some common mistakes we have seen so far. Take a few minutes to confirm none of these apply to you before the deadline.
- Required tech isn't actually used. This is the single biggest mistake. Your project must use Gemini and Google Cloud Agent Builder and your chosen partner's MCP server — with no competing AI or cloud services. Naming them in your README isn't enough; all three have to be imported and called at runtime. Fix: open your code and confirm each one is actually invoked, and remove any competitor AI/cloud.
- The hosted project URL doesn't work. Judges need a live, running app they can open. Fix: make sure the URL in “Provide a URL to the hosted Project for judging and testing” points to the running app (not your GitHub repo), and load it from a fresh browser to confirm it isn't a 404 or a dead deploy.
- The code repository isn't accessible. A private repo, a removed repo, or a broken/placeholder link means judges can't review your work. Fix: open your repo link in an incognito window to confirm it's public and reachable.
- No open source license. Your repo needs a real OSI-approved license showing in the About section on GitHub. Fix: add a LICENSE file at the root of your repo — a copyright line in the README does not count.
- The project isn't new. Submissions must be newly created during the contest period (on or after May 5, 2026). Fix: confirm your answer to "new or existing" is correct and that your first commit falls within the window.
Questions?
If you have any questions about the hackathon, please post on the discussion forum or find us on Discord.