Early Access Registration
Status
Clear status beats exaggerated claims.
RelayHub separates what is live today, what is in design, what is planned, what is research, and what is not yet product-supported.
Current website status
What is live now.
The public website is active and includes working forms, storage, anti-spam protection, admin tools, documentation pages, and public concept pages.
Contact Forms
D1 Signup Storage
D1 Contact Storage
Newsletter Admin
Contact Admin
FAQ
Documentation Hub
Media Kit
Public Roadmap
Community Directory Concept
Marketplace Concept
Privacy-Preserving Analytics
Product status
Product maturity is not the same across the ecosystem.
RelayHub website work is active. RelayOS and product hardware pathways remain in architecture, research, and validation planning until real builds and evidence exist.
RelayHub Website
The public website is live and actively expanding.
RelayOS
RelayOS is a platform direction, not yet a supported product release.
Relay Home
Home Node product work is currently architectural and validation-oriented.
Relay Infrastructure
Infrastructure roles require hardware validation, recovery testing, and operator documentation.
Relay Radio
Radio operation requires firmware, regional policy, validation, and lawful transmit boundaries.
Certification Program
Certification language exists conceptually, but no formal registry is implemented yet.
Platform status
The ecosystem foundation is being assembled.
| Area | Status |
|---|---|
| Branding | Active |
| Governance | Active |
| Documentation | Active |
| Validation Planning | Active |
| Hardware Validation | Planned |
| RelayOS Builds | Planned |
| Community Pilots | Research |
| Certification Registry | Planned |
Development stages
Status labels should mean something.
RelayHub uses maturity language to avoid confusing concepts, prototypes, validated behaviour, field trials, and supported releases.
Concept
The idea is being described and scoped.
Research
The problem, options, risks, and unknowns are being investigated.
Architecture
The system shape, boundaries, roles, and policies are being defined.
Prototype
A limited implementation exists to test feasibility.
Validation
The behaviour is tested, observed, reproduced, and documented.
Field Trial
Real users test the system in realistic conditions.
Limited Release
The system is available in a constrained, support-aware deployment.
Supported Release
The system has documented support, recovery, validation, and compatibility boundaries.
Service status
Website services are live. Product services are not yet released.
Website
Early Access
Contact
Documentation
Community Directory
Marketplace
Certification Registry
RelayOS Downloads
Now, next, future
Status shows where things actually stand.
Roadmap shows direction. Status shows current maturity.
Now
Public website, contact flows, early access, documentation, trust pages, concept pages, admin tools, and clear public positioning.
Next
Deeper product pages, partner pages, community guides, hardware validation planning, practical documentation, and clearer pilot pathways.
Future
RelayOS builds, local APIs, hardware validation, field trials, community pilots, certification registry, and supported product pathways.
Transparency statement
RelayHub prefers clear status over marketing certainty.
Features are described according to their current maturity, validation status, and support level. Planned features are not presented as product-supported behaviour.
Ask about status
If you are unsure whether something is active, planned, experimental, validated, compatible, certified, or supported, ask before relying on it.