Local-first
Setup, status, recovery, documentation, and local operation should remain useful without continuous internet access.
Local-first communication infrastructure
Build resilient communities.
RelayHub helps homes, groups, and communities communicate, coordinate, recover, and remain connected through simple local-first infrastructure powered by RelayOS and Reticulum.
Why RelayHub
Communication should not depend entirely on fragile central systems.
RelayHub is being built for practical local-first communication, community coordination, knowledge sharing, recovery, and future federation — without turning ordinary users into system administrators.
Appliance-simple
RelayHub is designed around QR onboarding, plain-language states, visible recovery, and browser-first local management.
Reality-based
No magic anonymity, no guaranteed delivery, no universal emergency promise. Capabilities must be validated before they are claimed.
RelayOS
The appliance platform behind RelayHub nodes.
RelayOS turns NixOS, Reticulum, policy governance, hardware profiles, local APIs, observability, updates, and recovery into a simple node experience.
NixOS foundation
Reproducible builds, declarative configuration, rollback-safe updates, and hardware-specific profiles.
Reticulum substrate
Local-first communication across supported transports and intermittent connectivity.
RelayOS appliance layer
QR setup, pairing, trust, dashboard, policy gates, recovery, support, and plain-language state.
Products
A family of nodes, not one universal box.
RelayHub products are capability-aware. A household appliance, a field radio node, and an infrastructure node should not pretend to do the same job.
Relay Home
A household communication appliance for local setup, QR pairing, status, updates, support export, and guided recovery.
Relay Radio
A radio-assisted field relay class for validated transport use where lawful, supported, and policy-enabled.
Relay Infrastructure
A stronger node for community infrastructure, DTN, bridge, gateway, observability, and operator roles.
Hardware
Hardware capability comes before product claims.
RelayHub nodes are built around hardware classes. A small radio relay, household appliance, and infrastructure node have different ceilings, recovery expectations, and support boundaries.
Hardware classes
Radio Micro Node, Nano Linux Node, Home Node, Strong Home Node, Infrastructure Node, and Mini PC Node each have different roles.
Compatibility status
Hardware may be Candidate, Boots, Reticulum Works, Stable, Product-Supported, Deprecated, Unsupported, or Unknown.
Radio reality
Radio transmit is never assumed. Region, legal limits, policy, hardware, firmware, user enablement, and runtime state all matter.
Communities
Technology is the tool. Communities are the purpose.
RelayHub exists to help people build, sustain, and interconnect resilient communities through communication, trust, knowledge, trade, coordination, governance, and cultural continuity.
Households
Simple local infrastructure for families, homes, rural properties, and small trusted groups.
Groups
Practical coordination for clubs, events, field teams, volunteer groups, and preparedness circles.
Communities
Future local directories, bulletin boards, markets, libraries, governance tools, and voluntary federation.
Future applications
Communications are only the beginning.
RelayHub can grow into a local-first ecosystem of community applications once the platform, validation, policy, and usability foundations are ready.
Relay Chat
Future user-facing messaging and trusted communication tools.
Relay Boards
Notices, requests, announcements, alerts, and local coordination.
Relay Market
Settlement-neutral trade coordination for goods, services, skills, offers, and requests.
Relay Library
Local knowledge, guides, maps, procedures, community memory, and cultural continuity.
Relay Events
Community calendars, rosters, working bees, training, and meetings.
Relay Governance
Future proposal, decision, role, delegation, and record tools.
Developer pathway
Build useful infrastructure without breaking the appliance.
RelayHub needs developers, hardware testers, documentation writers, validators, designers, and community operators who respect local-first, recovery-first, capability-aware design.
Build
RelayOS services, local APIs, web UI, hardware profiles, and future applications.
Validate
Boot, setup, pairing, recovery, rollback, degraded operation, documentation, and field usability.
Document
Quick starts, status meanings, privacy reality, recovery guides, operator notes, and support boundaries.
Honest limits
Resilient does not mean invincible.
What RelayHub is designed for
Local-first operation, QR onboarding, explicit trust, graceful degradation, visible recovery, and reduced dependence on centralised communication paths.
What RelayHub does not promise
Perfect anonymity, invisible metadata, guaranteed message delivery, universal emergency coverage, or lawful radio transmit in every region.
Documentation and support
Documentation is part of the product.
RelayHub documentation should help ordinary people set up, understand, operate, recover, and safely evaluate the limits of their node.
Docs
Quick starts, status meanings, recovery guides, hardware notes, and operator documentation.
Support
User-controlled support export, redaction by default, and no hidden remote control.
Accessibility
Plain language, readable layout, mobile usability, non-colour-only status, and recovery usability.
Early access
Follow RelayHub as it becomes real.
Register interest for product updates, RelayOS progress, documentation releases, developer resources, Etsy availability, and future community pilot programs.
Current status
RelayHub is in design and validation planning. Supported product claims, final pricing, hardware support, fulfilment details, and availability will be published only when they are ready.