Foundation
Public website, forms, storage, messaging, analytics, and core product positioning.
Roadmap
Where RelayHub is heading.
A public view of current work, near-term priorities, future capabilities, and research areas. This roadmap shows direction, not guaranteed release dates or supported product claims.
Public roadmap
Direction without false certainty.
RelayHub is being developed around local-first operation, practical resilience, simple onboarding, recovery-first architecture, capability awareness, and community usefulness. Items below may change as validation, hardware testing, policy work, and real user feedback shape the product.
Public clarity
Better explanations, stronger pages, clearer product boundaries, and deeper documentation.
Ecosystem services
Product pathways, community services, marketplace coordination, and RelayOS capabilities.
Validation areas
Hard problems that must be tested before being treated as supported product behaviour.
Now
What is being established now.
This phase is about making RelayHub publicly understandable, measurable, contactable, and ready for deeper documentation and product explanation.
- Public website foundation
- Early access registration
- Contact form
- D1 signup storage
- Cloudflare Email Routing
- Privacy-preserving analytics
- FAQ and concept pages
- Core RelayHub positioning
Next
The next public-facing priorities.
The next layer should help visitors, communities, and developers understand what RelayHub is, what it is not, and how the ecosystem could operate in practice.
- Roadmap and public documentation expansion
- Community directory concept refinement
- Marketplace concept refinement
- Product page deepening
- Hardware class pages
- RelayOS interface concept pages
- Developer documentation outline
- Validation and recovery explanations
Future
Where the ecosystem can grow.
Future capabilities should only become product-supported after architecture, recovery, validation, support, and documentation have caught up with the promise.
- Relay Home product pathway
- Relay Infrastructure product pathway
- Relay Radio product pathway
- RelayOS local web UI
- Community directory service
- Marketplace coordination service
- Knowledge and bulletin-board services
- Voluntary federation tools
Research
The hard problems are named openly.
RelayHub must not treat experimental ideas as finished capability. Research items identify areas that need testing, evidence, governance, and careful explanation.
- Reticulum appliance usability
- NixOS-based reproducible node builds
- Offline-first onboarding
- Trust and reachability workflows
- DTN and store-and-forward behaviour
- Radio legality and regional policy
- Recovery-first product design
- Community governance and federation models
Roadmap principle
Product support comes after validation.
RelayHub will grow carefully. A feature should not be marketed as supported merely because it is technically imaginable, prototyped, or attractive. It must be testable, observable, reproducible, recoverable, and documented.
Help shape the roadmap
Practical questions from households, developers, operators, and communities will help decide what should be built, validated, explained, simplified, or deferred.