Households
A household can operate a local node, invite trusted users, understand status, recover safely, and participate in wider community networks.
Communities
Local communities, connected on their own terms.
RelayHub exists to help people build, sustain, and interconnect resilient communities through communication, trust, knowledge, trade, coordination, governance, recovery, and cultural continuity.
Community first
Technology is not the community. It supports the community.
RelayHub is designed for households, groups, neighbourhoods, towns, regional networks, and federations that need practical infrastructure for real human cooperation.
Groups
Clubs, events, field teams, volunteer groups, rural networks, and preparedness circles can coordinate without depending entirely on centralised platforms.
Communities
Local communities can build shared communication, directories, knowledge, marketplace, governance, memory, and recovery infrastructure over time.
What communities need
Communication is only the beginning.
A resilient community needs more than messages. It needs memory, coordination, trust, practical knowledge, economic exchange, governance, recovery, and the ability to keep functioning when normal systems are unavailable.
Communication
Local-first messaging, notices, announcements, alerts, bulletins, status updates, and community coordination.
Trust
Explicit pairing, known nodes, trusted peers, role-based access, invitations, revocation, and recoverable identity.
Knowledge
Local guides, procedures, maps, recovery instructions, training notes, community memory, and offline-first documentation.
Trade
Future local marketplace tools for offers, requests, services, goods, skills, resources, invoices, receipts, and settlement-neutral exchange.
Governance
Proposal, notice, decision, role, record, working group, and delegation tools for communities that choose to use them.
Continuity
Shared memory, cultural records, institutional knowledge, recovery paths, and handover between generations of community stewards.
Community lifecycle
Communities should be able to form, grow, recover, and endure.
RelayHub communities should not depend on one person, one device, one company, one app, one cloud account, or one internet path. The goal is continuity through change.
Create
A small group establishes local infrastructure, identity, basic roles, and a shared purpose.
Coordinate
Members communicate, publish notices, share knowledge, and organise practical work.
Federate
Communities may voluntarily connect with other communities while retaining local autonomy.
Recover
Identity, knowledge, governance, trust, and infrastructure should have realistic recovery and handover paths.
Community roles
A community needs more than administrators.
RelayHub should distinguish social authority, technical operation, governance roles, support roles, trust relationships, and ordinary participation.
Members
People participating in the community through communication, events, trade, knowledge sharing, governance, or local work.
Stewards
People responsible for culture, continuity, onboarding, knowledge, norms, and the long-term health of the community.
Operators
People responsible for running infrastructure, nodes, backups, recovery procedures, updates, support, and validation.
Moderators
People entrusted by the community to manage local spaces, notices, boards, marketplace rules, or community standards.
Builders
Developers, hardware testers, documentation writers, designers, validators, and maintainers contributing to community capability.
Recovery contacts
Trusted people or roles that help restore access or continuity without creating hidden takeover authority.
Voluntary federation
Interconnection without centralisation.
RelayHub communities should be able to cooperate without surrendering autonomy. A community may share messages, directories, marketplace listings, knowledge, events, emergency notices, or governance records only where policy, trust, consent, and capability allow.
Local authority
Each community should retain control over its own membership, roles, moderation, knowledge, marketplace, culture, and governance choices.
Selective sharing
Federation can be narrow or broad: emergency notices only, marketplace only, knowledge only, directory only, events only, or deeper cooperation.
Revocable trust
Federation relationships should be visible, voluntary, limited, reviewable, and reversible.
Community services
Future applications for real local coordination.
RelayHub begins with communications infrastructure, but the ecosystem is designed to grow into practical community tools as validation, hardware, policy, and usability allow.
Relay Chat
Future user-facing messaging and communication tools built around local-first operation and explicit trust.
Relay Boards
Community bulletin boards for announcements, notices, requests, alerts, meeting notes, and local coordination.
Relay Market
A future marketplace layer for local trade coordination without forcing a single currency, payment method, or economic model.
Relay Library
Local knowledge bases for guides, procedures, maps, training, history, practical instructions, and community memory.
Relay Events
Event notices, rosters, meetings, working bees, training sessions, field activities, and community coordination calendars.
Relay Governance
Proposal, decision, role, delegation, record, notice, and working-group tools for communities that choose to use them.
Knowledge and memory
Communities need memory to endure.
RelayHub should help communities preserve and transmit practical knowledge, local history, procedures, lessons learned, cultural records, and recovery information across time.
Local knowledge
Guides, maps, supplier notes, procedures, emergency plans, field notes, training material, and local operating knowledge.
Collective memory
Decisions, stories, achievements, failures, lessons learned, events, working history, and institutional knowledge.
Cultural continuity
Traditions, customs, local identity, shared values, language, ceremony, and community practices where communities choose to preserve them.
Community economy
Trade coordination should be local, voluntary, and settlement-neutral.
Future RelayHub marketplace tools should help communities coordinate goods, services, requests, offers, skills, invoices, receipts, and reputation without forcing one currency, payment system, or economic model.
Offers and requests
A community can list what people have, what people need, who can help, and what resources are available.
Services and skills
Local skills, repairs, transport, food, tools, training, craft, labour, and professional services can become easier to find.
Settlement choices
Communities may coordinate trade while using cash, barter, bank transfer, mutual credit, local credit, or other lawful settlement methods.
Governance and moderation
Communities should define their own rules.
RelayHub should support local governance without imposing one model. Governance, moderation, marketplace rules, directory visibility, federation scope, and knowledge access should remain community-controlled within safe and lawful boundaries.
Local governance
Proposals, notices, working groups, votes, consensus processes, role assignment, delegation, and decision records where communities choose them.
Moderation
Communities may define acceptable conduct in their own spaces while distinguishing local moderation from technical censorship.
Disputes
Future marketplace, directory, federation, and governance tools may support community-defined dispute processes.
Infrastructure
Communities need infrastructure they can understand and recover.
A RelayHub community may begin with a single household node and grow toward stronger infrastructure only when hardware, operators, documentation, recovery, support, and validation are ready.
Relay Home
Household-class local infrastructure for small groups and ordinary users.
Relay Radio
Field relay and radio-assisted communication where lawful, validated, and policy-enabled.
Relay Infrastructure
Community infrastructure for operators, DTN, bridging, gateways, observability, and larger service roles where supported.
Community readiness
A useful community can start small.
A serious RelayHub community does not need to begin with a large network. It can begin with a few trusted people, one node, shared documentation, clear expectations, and a commitment to useful local cooperation.
People
Trusted participants who want to communicate, coordinate, learn, trade, govern, and help each other.
Purpose
A practical reason to exist: household resilience, local coordination, rural support, events, training, or mutual assistance.
Node
A suitable RelayHub node or future supported product used within its validated hardware and policy limits.
Recovery
Clear recovery steps, documented ownership, trusted recovery contacts, and realistic handover planning.
Start small
The first community does not need to be large.
A useful RelayHub community can begin with one household node, a few trusted people, simple communication, shared documentation, and clear expectations. The ecosystem should grow through usefulness, not hype.
Early community interest
Register interest if you want to test RelayHub with a household, local group, rural property, event team, community project, or future federation.