Furcate · sovereigntyThe architecture, not the marketing
YOURS
END TO END
Furcate is built on commitments that are the architecture, not the marketing. Machine identity and governance are built into every node. Global access exists only when the operator chooses to open it. The default is local.
Commitments · non-negotiable
| Operator owns | Keys, data, control plane. No mandatory Furcate SaaS. The binaries are ours; the keys are yours. |
| Open on the wire | Matter, ONVIF, OPC UA + TSN, BACnet, IEC 61850, ISOBUS, ROS 2 / DDS, MQTT 5 + Sparkplug B. The protocols operators already speak. |
| Machine identity | Every node gets a Furcate machine identity — a local DID and a role. Identity lives on the operator's perimeter, not in a vendor cloud. |
| Gated global access | Nodes stay local-only by default. Global connectivity is opened only when the operator grants it — with explicit scopes, on a per-resource basis. |
| Content-addressed sharing | Models and large artefacts move by hash. The same content goes to many nodes, fetched once. Receivers verify what they're given before running it. |
| No phone-home | Every outbound connection enumerated, logged, disable-able. Air-gapped is a supported configuration, not a degraded one. |
Local by default · global by grant