Local-first
Core setup, recovery, status, and local operation should not require cloud accounts or continuous internet access.
Developers
Build useful infrastructure without breaking the appliance.
RelayHub welcomes developers, builders, testers, documentation writers, hardware experimenters, and infrastructure operators who want to help create local-first tools for resilient communities.
Developer principle
Complexity belongs inside the system, not on the user.
RelayHub development must preserve the core product promise: local-first, recovery-first, policy-governed, capability-aware infrastructure that ordinary people can understand and use.
Recovery-first
A feature is not product-ready unless it can fail safely, roll back, recover, and be explained to the user.
Capability-aware
Hardware capability, software capability, policy permission, trust, legality, and runtime availability must remain separate.
What developers can build
RelayHub needs more than code.
The ecosystem needs platform work, product work, validation work, documentation, hardware testing, interface design, and careful community tooling.
RelayOS modules
Appliance services, local APIs, status models, policy enforcement, updates, recovery, onboarding, and observability.
Reticulum integration
Transport profiles, node roles, DTN behaviour, peer discovery, client guidance, and safe communication boundaries.
Local web UI
Browser-first setup, dashboard, people management, update screens, recovery flows, support export, and event history.
Hardware validation
Hardware profiles, capability manifests, boot tests, thermal checks, storage checks, radio validation, and support-state classification.
Community applications
Future apps such as Relay Chat, Relay Boards, Relay Market, Relay Library, Relay Events, and Relay Governance.
Documentation
Quick starts, recovery guides, operator notes, privacy explanations, status meanings, compatibility notes, and validation evidence.
Development stack
Built from reproducible, inspectable foundations.
RelayHub’s core direction is NixOS, Reticulum, local web interfaces, policy-controlled services, and validation-gated releases.
NixOS
Declarative system configuration, reproducible builds, rollback-safe updates, and hardware-specific profiles.
Reticulum
Local-first communication substrate for heterogeneous and intermittent connectivity.
Local API
A local-only appliance control plane for setup, pairing, state, recovery, updates, and support export.
Astro
Website and documentation publishing for clear public communication, guides, and product pages.
Contribution rules
Product-supported means validated, not merely working.
A pull request, hardware experiment, service module, or application idea should move through clear evidence: it must be testable, observable, reproducible, recoverable, and documented.
Do not overclaim
Experimental features must be labelled experimental. Compatibility is not certification. A prototype is not a supported product.
Preserve recovery
New services must not break rollback, identity preservation, recovery access, safe reset, transfer, or support export.
Respect policy
Features must obey capability, trust, privacy, security, legal, radio, resource, update, and validation policy.
Release discipline
The order matters.
Build the minimal system first. Validate operation. Validate recovery. Validate reproducibility. Validate upgrades. Validate degraded operation. Then expand features.
1. Build
Create the smallest working version that proves the appliance loop.
2. Validate
Capture evidence for boot, setup, pairing, status, recovery, and update safety.
3. Field test
Watch real users attempt setup, recovery, status interpretation, and support export.
4. Support
Only call something supported when documentation, recovery, and validation are complete.
Developer access
Early developer channels are coming later.
For now, RelayHub is still in design and validation planning. Public repositories, contribution guides, issue templates, hardware manifests, and validation harnesses should appear only when the project is ready for structured collaboration.
Register as a developer
Register interest if you want to help with NixOS, Reticulum integration, local web UI, hardware testing, documentation, validation, or community applications.