Community partners
Community groups, clubs, associations, local resilience groups, regional organisers, and pilot communities.
Partners
RelayHub will need builders, operators, educators, and communities.
RelayHub is an ecosystem direction, not just a product page. Partners may eventually help with hardware, education, community pilots, validation, deployment, documentation, support, and integrations — without confusing partnership with certification or official endorsement.
Partner types
Different partners strengthen different parts of the ecosystem.
RelayHub may eventually involve communities, hardware builders, educators, developers, installers, validation partners, and support providers. Each role needs clear boundaries and honest status language.
Hardware partners
Node builders, kit suppliers, enclosure makers, electronics suppliers, installers, and hardware validation contributors.
Technical partners
NixOS specialists, Reticulum specialists, integrators, application developers, security reviewers, and validation tool builders.
Education partners
Workshop operators, documentation contributors, trainers, community onboarding leaders, and local support educators.
Deployment partners
People or organisations helping households, communities, and regions deploy local-first infrastructure safely.
Validation partners
Field testers, hardware reviewers, accessibility testers, recovery testers, and documentation reviewers.
Partnership principles
Partnership should strengthen the RelayHub mission.
Partners should support local-first, recovery-aware, validation-gated, community-centred infrastructure rather than creating dependency, confusion, or exaggerated claims.
Local-first operation before remote dependency.
Open standards and interoperability where practical.
Honest claims over marketing exaggeration.
Recovery-first design before convenience.
Validation before product support.
Respect for community autonomy.
Clear separation between compatibility, certification, and official status.
Plain-language support for non-technical users.
Important boundaries
Partnership is not automatic authority.
RelayHub should remain open to cooperation while preventing confusion about endorsement, certification, employment, governance, and official status.
Partnership ≠ Endorsement
Being in conversation with RelayHub does not automatically mean RelayHub endorses a product, service, organisation, or claim.
Partnership ≠ Certification
Certification requires defined scope, validation evidence, documentation, support boundaries, and governance approval.
Partnership ≠ Employment
Partners are independent unless a separate formal agreement says otherwise.
Partnership ≠ Governance authority
Partners do not gain authority over RelayHub governance, terminology, certification, communities, or product direction by default.
Partner directory
A future partner directory is planned, not implemented.
A future partner directory could help people find builders, educators, installers, technical specialists, community operators, and validation partners by region, service type, and status.
partners.relayhub.tech
This registry concept is not yet implemented. It should appear only after partnership rules, certification relationships, and status labels are clearly defined.
Partner name
Partner type
Region
Certification status
Compatibility status
Services offered
Hardware classes supported
Community focus
Support boundary
Current lifecycle status
Who builds the ecosystem?
RelayHub should grow through responsible participation.
The ecosystem may eventually include community organisers, regional pilots, home builders, professional installers, educators, developers, technical reviewers, and hardware suppliers.
Builders
People who build nodes, kits, enclosures, software, services, documentation, and validation tools.
Operators
People who operate household, community, infrastructure, and field deployments responsibly.
Educators
People who teach setup, recovery, community coordination, safety, privacy reality, and practical operation.
Becoming a partner
Tell us what you can responsibly help with.
RelayHub partnership should begin with clarity: who you are, where you operate, what you build, what communities you serve, and what claims you want to make.
- Who you are
- Where you operate
- What you build or provide
- Which communities you serve
- Which hardware, software, or services you understand
- Whether you are interested in pilots, validation, education, hardware, or deployment
- What evidence, experience, or documentation you already have
- What claims you want to make publicly
Status
No formal partner programme is open yet.
RelayHub is still in public website, architecture, documentation, and validation planning. Partnership conversations are welcome, but formal partner status, certification, and directory listing are future governance steps.
Current status
Partnership enquiries are open. Formal partner registry, certification, and public listings are planned but not yet implemented.