Families and households
Local-first communication, family notices, shared household information, recovery access, and simple local coordination.
Use Cases
RelayHub is for communities that need to keep working.
RelayHub is being designed for families, households, community groups, regional communities, events, rural areas, educators, preparedness groups, and local economies that need practical local-first coordination.
Who is RelayHub for?
People understand RelayHub when they can see themselves in it.
RelayHub is not only about devices, protocols, or infrastructure. It is about the practical things people need to do together: communicate, organise, preserve knowledge, coordinate resources, trade, govern, and recover from disruption.
Community groups
Clubs, associations, volunteer groups, neighbourhood groups, and local organisations that need notices, discussion, and shared knowledge.
Regional communities
Towns, villages, rural regions, and local networks that need community directories, knowledge sharing, coordination, and resilience.
Events and festivals
Temporary local coordination, announcements, volunteer communication, maps, schedules, lost-and-found notes, and information sharing.
Remote and rural areas
Intermittent connectivity, local services, community information, offline knowledge, and practical local coordination.
Education and workshops
Training groups, local learning, documentation libraries, workshops, skill sharing, and community education programmes.
Preparedness groups
Local preparedness, resource directories, contact lists, continuity planning, and community coordination. RelayHub is not an emergency service.
Local economies
Marketplace concepts, service listings, skills exchange, community trade, requests, offers, and settlement-neutral coordination.
Example scenarios
Practical situations RelayHub is being designed for.
These examples describe future RelayHub use cases. Specific product features must still be implemented, validated, documented, and supported before being treated as product-ready.
A family wants local communication
A household wants a simple way to keep local information, contact notes, and recovery instructions available even when internet access is unreliable.
A club wants a local noticeboard
A club wants announcements, event information, useful documents, membership notes, and volunteer coordination without relying entirely on social media.
A regional group wants resilience
A local group wants to preserve knowledge, coordinate practical help, build trust, and prepare for intermittent connectivity or disruption.
An event needs temporary coordination
A festival, market, workshop, or community event wants local announcements, maps, volunteer updates, and useful information in one place.
Why it matters
The value is not the box. The value is community capability.
RelayHub should help people become more capable, not more dependent. The goal is practical community usefulness under ordinary and adverse conditions.
Reduce dependence on central platforms.
Keep local knowledge available.
Support local coordination.
Help people understand degraded operation.
Make trust and roles explicit.
Support recovery and continuity.
Encourage community participation.
Prepare for intermittent connectivity.
Preparedness without overclaiming
Useful for preparedness. Not an emergency service.
RelayHub can support preparedness thinking, local coordination, contact information, resource directories, community continuity, and knowledge preservation. It must not be presented as guaranteed emergency communications or a replacement for emergency services.
Preparedness examples
Local contact lists, printed recovery cards, community resource notes, volunteer coordination, local directories, offline guides, and continuity planning.
Clear boundaries
RelayHub should be useful without false promises.
Use cases must remain honest. A compelling scenario is not the same as a validated product guarantee.
RelayHub is not an emergency service.
RelayHub does not guarantee message delivery.
RelayHub does not provide perfect anonymity.
RelayHub does not automatically make every device compatible or supported.
RelayHub does not replace local governance, judgement, or trust.
Radio use must be lawful and region-aware.
Planned features are not product-supported until validated.
A pilot is not the same as a supported release.
Find your path
Start with the page that matches your need.
| Need | Start here |
|---|---|
| I want local household communication. | Products / Recovery |
| I want to organise a community group. | Communities |
| I want to test RelayHub with a group. | Pilot Program |
| I want to build or integrate with RelayHub. | Developers |
| I want to understand hardware options. | Hardware |
| I want to know what exists today. | Status |
Have a use case?
Tell us what you want RelayHub to help with.
The best use cases come from real communities, real households, real events, real rural constraints, and real coordination problems.
Useful details
Tell us who you are, where you operate, what problem you are solving, how many people are involved, what connectivity is like, and what a successful pilot would prove.