Architecture
Reticulum-Level Infrastructure with Appliance-Level Usability.
Published 3 June 2026. RelayHub is built around a simple belief: powerful infrastructure only matters if ordinary people can actually use it.
Reticulum is one of the most interesting communication systems in existence.
It provides a foundation for resilient communication across diverse transports, intermittent connectivity, local networks, radio links, delay-tolerant paths, and future transport combinations that are difficult to achieve with conventional internet-centric thinking.
Yet despite its technical strengths, Reticulum remains largely the domain of enthusiasts, experimenters, radio operators, developers, and highly technical users.
That is not a criticism of Reticulum. It is a recognition of reality.
Most people do not want to become network engineers.
Most people do not want to learn Linux administration.
Most people do not want to read protocol documentation.
Most people simply want communication that works.
The Gap
This creates a significant gap.
We have extraordinary infrastructure capabilities on one side and ordinary human needs on the other.
Technical capability alone does not create adoption.
A system can be elegant, secure, resilient, decentralised, censorship resistant, and technically brilliant while remaining inaccessible to the vast majority of people.
History repeatedly demonstrates this pattern.
Technologies that survive and spread are rarely the most technically sophisticated.
They are the technologies that become understandable.
The RelayHub Goal
RelayHub exists to bridge that gap.
The goal is not to replace Reticulum.
The goal is not to compete with Reticulum.
The goal is not to abstract Reticulum into irrelevance.
The goal is to make Reticulum-level infrastructure accessible to ordinary households, community groups, local organisations, educators, and non-technical users.
In simple terms:
Reticulum-level infrastructure with appliance-level usability.
What Appliance-Level Usability Means
Appliance-level usability does not mean removing power.
It means removing unnecessary complexity from the user experience.
A household should not need to understand routing tables.
A community organiser should not need to learn Linux internals.
A volunteer should not need to understand transport profiles.
A user should not need to understand packet propagation before sending a message.
Instead, the system should guide people toward successful outcomes.
The intended experience is:
- Plug in node.
- Open app or local web interface.
- Scan QR code.
- Communicate.
The complexity remains inside the system where it belongs.
The Importance of Recovery
Appliance-level usability is impossible without recovery.
Many technically sophisticated systems assume users will repair problems through command-line tools, documentation searches, or advanced debugging.
Most people do not operate this way.
If recovery requires specialist knowledge, the system is not truly usable.
This is why RelayHub treats recovery as mandatory architecture rather than an optional feature.
Users should be able to understand:
- What is working.
- What is degraded.
- What has failed.
- What can be recovered.
- What should not be reset.
- What actions are safe.
The Importance of Honest Status
Complex systems often hide important information.
RelayHub aims to do the opposite.
Users should be able to understand the state of their node using plain language.
Instead of forcing users to interpret technical logs, RelayHub aims to communicate states such as:
- Ready
- Local Only
- No Peers Found
- Degraded
- Recovery Available
- Update Available
These concepts are meaningful to ordinary people.
Capability Before Claims
RelayHub is intentionally designed around capability-aware operation.
Not every node can perform every role.
A small radio relay node is different from a household node.
A household node is different from an infrastructure node.
An infrastructure node is different from a mini-PC deployment.
Hardware capability matters.
Software capability matters.
Policy permissions matter.
Legal constraints matter.
Runtime conditions matter.
RelayHub aims to expose these realities honestly rather than pretending every node can do everything.
Why This Matters for Communities
Technology is not the purpose.
Community is the purpose.
Communication is valuable because communities communicate.
Knowledge matters because communities remember.
Recovery matters because communities experience disruption.
Trust matters because communities coordinate.
Infrastructure matters because communities depend on it.
If the infrastructure is too difficult for ordinary people to use, its community value remains limited regardless of technical excellence.
The Long-Term Vision
The long-term vision is not merely to build another communication tool.
The vision is to help communities build local capability.
Households should be able to participate.
Community groups should be able to participate.
Educators should be able to participate.
Rural communities should be able to participate.
Technical experts should be able to participate.
Non-technical users should be able to participate.
Achieving that requires both infrastructure and usability.
Neither is sufficient on its own.
Reticulum provides the infrastructure.
RelayHub aims to provide the usability.
Communities provide the purpose.