WHITE
PAPER
Furcate is an edge-AI platform that runs on hardware ranging from microcontrollers to confidential-computing site servers, speaks the open protocols of the modern physical environment, and operates without dependence on any vendor cloud. The operator owns the keys, owns the data, and owns the control plane. This whitepaper sets out the problem, the architectural premise, the technical shape, and the model under which Furcate is delivered to OEMs, system integrators and operators.
Contents
| §1 | The problem Cloud-architected platforms cannot serve sovereign physical infrastructure. Three pressures — sovereignty, latency, economics — have made the cloud-first default untenable for hospitals, banks, utilities, transportation, government estate and defence. |
| §2 | The premise Furcate is built on four commitments that are not commercially negotiable. Operator owns the keys, data and control plane. Open standards on the wire. Attestation is non-negotiable. No mandatory phone-home. |
| §3 | The three positions Furcate is delivered in three shapes — Embedded inside an OEM's product, Standalone as a finished compute device, or as The compute brain for a whole site. The same software stack supports all three. |
| §4 | The technical shape Three classes of node — Micro (microcontrollers), Small (single-board computers), Base (accelerated edge AI). Same agent across all. Open protocols on the wire — Matter, ONVIF, OPC UA + TSN, BACnet, IEC 61850, ISOBUS, ROS 2 / DDS, MQTT 5 + Sparkplug B. Operator picks the transport that suits the site. |
| §5 | The sovereignty chain Measured boot, signed images, workload signing, transparency log, attestation evidence in RFC 9334 EAT format, confidential computing at the orchestrator tier. Every link in the chain runs inside the operator's perimeter. |
| §6 | Meshes and clusters Nodes form meshes inside a site, meshes form clusters across sites. Models and data move by content address. Models ask other models when they need more. Local first, LAN second, off-edge by grant — always fail-soft. |
| §7 | The delivery model Open-source core with commercial support, OEM licensing for the Embedded position, hardware partnerships for Standalone. Pilots run in weeks, not quarters. |
Full document on request · ~20 pages · technical detail
The full whitepaper covers the dependency baseline, the five-tier hardware sweep, the three concurrent execution substrates, the peripheral-discovery layer, the sovereignty chain end-to-end, the three delivery positions, and the commercial model. Available to OEMs, system integrators and operators under NDA.