Guardian began as software, and software remains the platform. But one scenario kept surfacing in every design review: the phone is in a handbag, and the emergency is now. The answer is a trigger you are already wearing — the Guardian Ring.
What the ring actually does
The ring is deliberately simple: a discreet trigger that speaks Bluetooth Low Energy to the Guardian app. A triple-press fires the same full dispatch as the in-app SOS — live location streaming, evidence capture, trusted-contact SMS, and responder alerting. The intelligence stays in the platform; the ring's job is to be reachable when the phone is not.
The breadboard phase, honestly
Today's prototype is a working BLE breadboard build: trigger, pairing, dispatch integration, and disconnect-safety logic — the app knows when the ring goes out of range. It is not yet a manufactured ring, and we say so plainly on our product-status page. Hardware credibility is earned by shipping, not renders.
Three tiers on the roadmap
Our hardware specification work defines three tiers: a BLE companion ring (phone-dependent, lowest cost), a GPS + LoRa zone-autonomous tier for campus and community deployments, and a cellular tier that operates independently of a phone. Each tier trades cost against autonomy; each is specified with parts lists and an ODM checklist so we can move from prototype to production partner without hand-waving.
Software first was the right call
Every dispatch improvement — expanding rings, the moving 4-zone cluster, Voice Guard — ships to every user instantly because the platform is software. The ring inherits all of it the day it arrives. That is the point of building the brain before the button.