Capability-aware
Hardware capability, software capability, policy permission, runtime availability, trust permission, legal permission, and user enablement must remain separate.
Products
A family of nodes for resilient communities.
RelayHub is not one universal box. It is a capability-aware product family designed for homes, field use, community infrastructure, development, validation, recovery, and future local-first applications.
Product doctrine
Every product has a role, a ceiling, and a recovery path.
RelayHub products should never pretend that every node can do everything. Each product must clearly state what it is for, what it can support, what is still experimental, and what it cannot promise.
Appliance-first
Products should be understandable through status, QR setup, local web UI, clear documentation, and guided recovery.
Validation-gated
A product becomes supported through evidence: boot, setup, recovery, rollback, degraded operation, usability, and documentation.
Core node family
From household appliance to community infrastructure.
RelayHub products are designed to scale from simple home use to larger community infrastructure without collapsing every role into one device.
Relay Home
A household communication appliance focused on local-first setup, QR onboarding, owner claim, paired users, node status, updates, recovery, support export, and supported communication paths.
Relay Radio
A radio-assisted field relay class for validated radio transport, low-power operation, local relay use, and field deployment where lawful, supported, and policy-enabled.
Relay Infrastructure
A stronger community node for validated bridge, gateway, DTN, observability, federation support, operator controls, and local community services.
Relay Home
The household appliance target.
Relay Home is the first product target: a simple local-first node for households and small groups. It should behave like an appliance, not a Linux server.
Designed for
- Homes and families
- Rural properties
- Small local groups
- Preparedness circles
- People who want simple local-first infrastructure
Expected core functions
- Local web dashboard
- QR setup and pairing
- Owner claim
- Paired users and guests
- Status meanings
- Updates and rollback
- Guided recovery
- Support export
What it should do
Help ordinary users understand whether their node is Ready, Local-Only, No Peers, Degraded, Updating, Recovering, or in Error.
What it should not imply
Relay Home should not imply gateway, bridge, infrastructure, or radio transmit capability unless separately validated and enabled.
Support status
Relay Home should only be offered as product-supported after setup, recovery, updates, documentation, and field usability are validated.
Relay Radio
Field relay and radio transport, where validated and lawful.
Relay Radio is a radio-assisted product direction. It should never imply that radio transmit is automatically lawful, enabled, private, or supported everywhere.
Designed for
Field relay, local mesh experiments, portable deployments, low-power use, events, and radio-assisted community communication.
Radio reality
Radio operation must respect regional rules, frequency limits, power limits, duty cycle, encryption restrictions, and equipment constraints.
Capability limit
A small radio node is not automatically a household appliance, infrastructure node, gateway, or full community server.
Relay Infrastructure
Stronger nodes for community-level operation.
Relay Infrastructure is for larger validated deployments where bridge, gateway, DTN, observability, federation, and operator functions may be needed.
Possible roles
- Community infrastructure node
- DTN/store-and-forward node
- Bridge node
- Gateway node
- Local services host
- Operator dashboard host
Required boundaries
- Bridge disabled unless policy allows
- Gateway disabled unless policy allows
- Radio not assumed lawful
- Support export redacted by default
- Recovery and rollback preserved
- Operator controls separated from household UX
Hardware classes
Product names are not hardware classes.
RelayHub products may map onto different validated hardware classes over time. Hardware support must be declared, tested, and labelled honestly.
Radio Micro Node
Small radio transport and field relay class. Useful for radio movement, not a full platform by itself.
Nano Linux Node
Lightweight Linux relay class with constrained compute, storage, queue, and service capacity.
Home Node
Household appliance class. The first major product target for simple local-first operation.
Strong Home Node
Enhanced household node with more comfortable performance and expanded validated capacity.
Infrastructure Node
Community infrastructure class for stronger storage, queues, gateway, bridge, DTN, and operator roles.
Mini PC Node
Full infrastructure class for advanced community or regional deployments where validated.
Future applications
The product ecosystem can grow beyond nodes.
RelayHub begins with communication infrastructure, but the wider ecosystem can support applications for community coordination when product, policy, hardware, and validation are ready.
Relay Chat
Future user-facing communication application for local-first messaging and trusted community interaction.
Relay Boards
Bulletin boards for announcements, requests, notices, updates, meetings, and local coordination.
Relay Market
Marketplace coordination for goods, services, skills, offers, requests, and settlement-neutral exchange.
Relay Library
Local-first knowledge base for guides, maps, procedures, community memory, and cultural continuity.
Relay Events
Community events, rosters, working bees, meetings, training, field activities, and coordination calendars.
Relay Governance
Future tools for proposals, notices, decisions, roles, records, delegation, and community governance.
What supported means
Supported is not the same as experimental.
RelayHub should distinguish between concept, prototype, validation, release candidate, supported, legacy, deprecated, and retired products.
Idea defined
The product direction exists but is not ready for users.
Build tested
Some functions work, but recovery, usability, or support may be incomplete.
Evidence gathered
Lab, recovery, security, privacy, accessibility, and field testing occur.
Product ready
Documentation, recovery, support, compatibility, and validation gates are complete.
Etsy and direct sales
Sales should wait until support is real.
RelayHub products may eventually be offered through Etsy, direct order, local builders, certified vendors, or community supply channels. The website should explain products first and only route to purchase when each product is ready.
Etsy listings
Useful for early professionally home-built nodes once product status, support terms, documentation, and warranty boundaries are ready.
Direct orders
Possible later for controlled batches, pre-orders, community pilots, or certified product-supported releases.
Certified builders
Future builders may seek compatibility or certification, but compatibility must not imply official certification.
Early product interest
Follow the product family as it develops.
Register interest if you want updates on Relay Home, Relay Radio, Relay Infrastructure, RelayOS, future applications, Etsy availability, developer resources, or community pilot programs.
Current status
RelayHub products are in design and validation planning. Supported product claims, final prices, hardware support, fulfilment details, and availability will be published only when they are ready.