Router edge
OpenWrt x86 manages WAN, LAN, voice VLAN, DHCP, DNS, QoS, firewall, and local recovery access.
FabricAir Local Node
One small router box can become the local safe space.
The hosted portal should manage the settings. The local node should run headless: router, protected phone network, WireGuard overlay, Asterisk extensions, and a secure check-in path back to the Fabric spine.
Product shape
Hosted portal, local runtime.
Customers should not have to configure SIP ports, NAT, firewall rules, or PBX files. They choose desired settings in the portal; the node checks in and safely applies them.
Local PBX
Asterisk keeps family, church, clinic, or business extensions working locally even when the internet is unstable.
Encrypted overlay
WireGuard protects node-to-spine and node-to-node traffic, preferring direct IPv6 when available.
Customer portal
Claim the box, then manage everything from FabricAir.
The first UI we need is not a firewall console. It is a customer-friendly claim and node-status surface that tells the spine where the customer wants calls, extensions, phones, and protections to live.
Claim code: AIR-HOME-7K2Q-19Node preview
Box 1
OpenWrt x86 candidate
online
WAN
IPv6 preferred, IPv4 fallback
direct
Voice LAN
Protected phone network and DHCP options
ready
PBX
Asterisk config staged by spine bundle
staged
Portal controls
Assign phones, choose extension ranges, enable scam blocking, publish trusted helper groups, and decide whether a line is local-only, hosted, or hybrid.
Base build image
The node should boot into check-in, not configuration.
The first appliance image should be intentionally small: enough router/PBX/overlay tools to call home, receive a signed desired-state bundle, and recover if the new bundle fails.
Flash image
OpenWrt x86 image with FabricAir packages preloaded for the six-port mini-PC hardware.
Boot safely
WAN comes up, local recovery UI is available, and a factory claim identity is generated.
Check in
Node opens an outbound tunnel/control session to the Fabric spine without inbound port requirements.
Apply bundle
Signed config stages Asterisk, WireGuard, DHCP, DNS, QoS, and local extension routing.
Four box lab
Use the hardware we already have.
Main candidate: router, WireGuard, Asterisk, phone DHCP, and node agent on one image.
Control build to prove whether OpenWrt packaging is helping or slowing us down.
Router UI and stability comparison, not the default Asterisk packaging path.
Acts like a church, clinic, or family node checking into the spine over real WAN conditions.
Next build decision: the backend should create and claim FabricAir nodes before it pushes live
Asterisk changes. Asterisk management becomes one service inside a node lifecycle, not the whole product.