Beacon
When Infrastructure Fails, Community Shouldn’t
What Inspired Me
In the United States, severe weather causes nearly 70% of major power outages. North Carolina ranks 5th in the country for outage frequency. During major disasters, up to 40% of cell towers can fail or become overloaded.
Those aren’t rare events. They’re increasing. And when the power goes out, something else disappears with it: digital communication.
Routers shut down. Cell signals degrade. Safety apps stop updating.
We’ve built our sense of security on invisible infrastructure — cloud servers, fiber cables, cellular towers — and we assume it will always be there when we need it most. That assumption is broken all the time.
That is what led to Beacon.
The Problem We Don’t Talk About
When something dangerous happens, people don’t just need information. They need confirmation.
Is this real? Is anyone else seeing this?
Today’s safety platforms depend on internet connectivity and centralized servers. If those fail, the system fails. And even when they stay online, they struggle with false alarms. Research shows repeated low-value alerts can reduce response compliance by up to 50%. Over time, people stop taking warnings seriously.
It’s the “boy who cried wolf” problem in a modern format.
What I Built
Beacon is an offline-first, peer-to-peer emergency alert system that allows devices to communicate directly over Wi-Fi Direct.
No internet. No router. No cloud server.
If someone witnesses a threat, they press one button. The alert spreads outward from device to device, forming a living mesh. As nearby devices independently confirm the same event, the alert strengthens. Trust isn’t assigned by a distant authority. Instead, it emerges locally. With this, we have now achieved the following:
Infrastructure independence. Verification without centralization. Resilience by design.
Let’s look at an Example
A hurricane has just passed through a North Carolina neighborhood. Power is out across the entire block. Cell service barely works. Wi-Fi is gone. It’s humid, dark, and uncertain.
Then someone smells gas.
No one knows if it’s isolated or widespread. Calls won’t connect. Apps won’t load. There’s no official update coming.
One neighbor opens Beacon and sends a gas leak alert.
Nearby homes receive it instantly, device to device. As others confirm the same smell, the alert spreads outward, gaining strength with each independent witness. What began as uncertainty becomes shared awareness. People shut off breakers. They check on elderly neighbors. They move away from danger.
No internet was involved. No central server approved it.
The community protected itself.
What I Learned
I learned that centralized systems are efficient but fragile. When they fail, they fail completely and the lack of in built redundancy in today’s world is a danger many of us fail to take into consideration.
A mesh behaves differently. It adapts. It shrinks instead of collapsing. Even partial connectivity still allows communication.
I also learned that trust is harder to build than technology. Sending a message is easy. Designing a system that filters noise without slowing urgency requires understanding human behavior as much as networking.
Why Beacon
Climate events are intensifying. Power outages are increasing. Large gatherings overwhelm networks in seconds despite all the technological advancements we have achieved.
We need systems that assume failure and work anyway.
Beacon turns every nearby device into part of a digital safety net. Not dependent on distant infrastructure, but powered by proximity and collective awareness.
When the lights go out, communication shouldn’t disappear with them.
How we built it
Locally hosted app with flask endpoints, node js, ollama model for clustering similar events.
Challenges we ran into
Never used any of these technologies or dealt with networking before and as someone working solo, it was really tough to get this all in.
Accomplishments that we're proud of
Completing the project, never thought it would actually be possible to have everything done and working.
What's next for Beacon
Making it scalable.
Log in or sign up for Devpost to join the conversation.