RelayHub
The ecosystem: communities, products, services, applications, trust networks, knowledge systems, marketplaces, and federations.
Ecosystem
RelayHub is the ecosystem. RelayOS is the platform. Communities are the purpose.
RelayHub is being built as a local-first ecosystem for communication, trust, knowledge, trade, coordination, governance, recovery, and cultural continuity — not merely as a device or messaging app.
Ecosystem layers
Each layer has a distinct role.
RelayHub should remain coherent as it grows. The ecosystem, platform, products, applications, communities, and federations must not be confused with one another.
RelayOS
The appliance platform that powers RelayHub nodes and provides onboarding, recovery, policy, observability, updates, and local APIs.
Products
Relay Home, Relay Infrastructure, Relay Radio, Relay Developer, and future approved product families.
Applications
Future Relay applications for chat, boards, marketplace, library, files, maps, events, voice, identity, and community coordination.
Communities
The primary social units: households, groups, neighbourhoods, towns, regions, associations, and local organising networks.
Federations
Voluntary coordination structures linking communities without replacing community autonomy.
What the ecosystem enables
RelayHub is broader than messaging.
The purpose is resilient community capability: people should be able to communicate, coordinate, preserve knowledge, exchange value, govern locally, recover from disruption, and cooperate with neighbouring groups.
Product families
Products are appliances within the ecosystem.
Product families should be capability-aware, policy-governed, validation-gated, and honest about current maturity.
Relay Home
Household appliance-class nodes focused on setup, local web UI, pairing, recovery, and ordinary home/community use.
Relay Infrastructure
Stronger nodes for community infrastructure, bridge/gateway roles, DTN, observability, and operator workflows.
Relay Radio
Radio transport and field relay concepts requiring firmware, regional policy, lawful operation, and hardware validation.
Relay Developer
Developer-oriented tooling, APIs, validation harnesses, application frameworks, and integration documentation.
Application families
Applications are future services, not current promises.
Relay applications are future ecosystem concepts. They should be labelled clearly until implemented, validated, documented, and supported.
Relay Chat
Future user communication layer where supported.
Relay Boards
Community bulletin boards, notices, requests, and announcements.
Relay Market
Local goods, services, offers, requests, skills exchange, and settlement-neutral coordination.
Relay Library
Knowledge preservation, guides, procedures, maps, memory, and training material.
Relay Events
Local events, working groups, meetings, tasks, and community coordination.
Relay Identity
Identity, membership, trust, roles, reputation context, and recovery authority.
Ecosystem rules
Growth must not undermine the mission.
RelayHub can grow into products, applications, services, communities, federations, partners, and certification, but the core principles should remain stable.
The community is the purpose.
Technology is the tool.
Local-first comes before remote dependency.
Trust is explicit, limited, and revocable.
Recovery is mandatory.
Capabilities require validation before support.
Compatibility does not imply certification.
Federation must remain voluntary.
Participation
Different participants strengthen different parts of RelayHub.
RelayHub should support individuals, households, communities, developers, vendors, and partners without confusing participation with governance authority or certification.
Individuals
Use RelayHub tools, join communities, participate in local coordination, and contribute feedback.
Households
Operate local infrastructure, pair trusted users, preserve recovery paths, and participate in nearby communities.
Communities
Define local purpose, governance, trust rules, directories, knowledge bases, marketplace rules, and federation relationships.
Developers
Build applications, services, integrations, documentation, validation tooling, local UI components, and operator tools.
Vendors
Offer compatible products or services while clearly distinguishing compatibility, certification, and official status.
Partners
Help with deployment, education, validation, hardware, support, documentation, pilots, and community onboarding.
Federation
Interconnection without centralisation.
Federation should allow communities to cooperate voluntarily without surrendering autonomy. A federation can share directories, knowledge, marketplace visibility, emergency coordination, governance notices, or other scoped services.
Federation boundary
Federation must not imply total trust, automatic authority, mandatory participation, or replacement of local community governance.
Growth path
Build carefully. Validate before expanding.
RelayHub should grow from clear public explanation into validated appliance behaviour, then community pilots, limited deployments, and eventually a supported ecosystem.
1. Website and public story
Explain RelayHub, collect interest, define trust, security, privacy, recovery, compatibility, certification, and status.
2. Architecture and validation
Define RelayOS, hardware classes, product boundaries, validation gates, recovery drills, and support expectations.
3. Prototype and lab validation
Build minimal nodes, prove setup, pairing, recovery, update, local-only operation, and support export.
4. Community pilots
Test with real communities, non-technical users, degraded states, documentation, trust workflows, and recovery.
5. Limited deployment
Deploy with clear support boundaries, hardware status, compatibility limits, and evidence-backed documentation.
6. Supported ecosystem
Grow products, applications, certification, partners, community guides, and federation pathways carefully.
Current status
The ecosystem is being defined before it is broadly deployed.
RelayHub’s public ecosystem language is active. Product builds, applications, certification, directories, marketplaces, and federations remain planned, research, or architecture-stage until validated.
Follow the ecosystem
Register interest if you want updates about RelayOS, hardware, pilots, applications, communities, partners, or future ecosystem services.