Meshfire Recovery Node — Reference Architecture, Draft v0.1
This document is a working draft published for partner and customer comment. The recovery node is built on open interfaces, designed to interoperate seamlessly with partner-supplied capabilities across all infrastructure layers.
Layer Model & Interface Expectations
| Layer | Purpose | Interface Expectation | Status |
|---|---|---|---|
| Core Node | Provide directory, core services, and offline AI | Standard x86 compute environment presenting containerized microservices | Draft — open for comment |
| Connectivity | Link the node to remote teams or upstream networks | Any transport (Private 5G, Satellite, LTE) that presents standard IP uplink to the node | Draft — open for comment |
| Power | Sustain node operations in grid-down scenarios | Common 12V-48V DC input or 110V/220V AC with seamless failover | Draft — open for comment |
| Transport | Protect the node during field deployment | Universal 19-inch rack mounting points with shock isolation | Draft — open for comment |
| Security | Enforce zero-trust boundaries at the edge | SAML/OIDC integration with the node's local directory | Draft — open for comment |
Planned program — not yet operating
What certification will mean
Once finalized, partners whose hardware or software layers meet these interface expectations will be formally interoperability-tested against the recovery node.
- Successfully tested solutions will be explicitly listed in the reference architecture.
- Certified partners will gain eligibility for co-marketing and bundled pilot deployments.
Have feedback on these interfaces?
We want to hear from vendors and operators on these draft specifications.
Submit architecture comment