GridDown is the 🥇 1st place submission for the GDGC (Google Developer Groups on Campus) 2026 Hackathon by our team, Team Buckley.
A solar flare has impacted earth. Internet and power is still up, but server data has been corrupted, rendering them unreliable and useless.
Food, medicine, shelter, skills - they exist but aren't where they're needed. How do you match supply to demand across a city with no central coordinator? Our team chose to focus on the issue of Resources without coordination.
You can view read more of the hackathon theme and brief here.
When the grid goes down, that's where GridDown steps in. We built a de-centralised emergency co-ordination system application to remove the need for reliance on corrupted servers.
GridDown allows anyone to broadcast requests for help and set the urgency of these requests, offers to help, or announcements, and set the locations for these broadcasts. Users can set their location upon onboarding, as well as their name, age and skillset, and the closest broadcasts and their urgency will be prioritised and displayed on a live board. On the right, users can view the shortest path and distance from the locations of these broadcasts on a live, interactive map.
To implement a trust-building feature, GridDown allows users to upvote or downvote broadcasts, and a chatting feature also enables users to communicate with broadcast offers.
Initially, our project adopted a client-server model with Next.js, tRPC, Tailwind, NextAuth, Prisma and PostgreSQL.
With the transition to a serverless P2P implementation with WebRTC, NextAuth, Prisma and PostgreSQL was no longer needed. tRPC remained to serve as a signalling server for SDP and ICE candidate transmission.
You can read more about our implementation in architecture.md and how WebRTC works with our codebase in webrtc.md.
| Benjamin Kee | Tommy Duan | Wilson Mao | Gladwyn Chua | Gloria Chan |
| Team Leader Developer |
Developer | Developer | Developer | Developer |
