Furcate · on-premThe full stack, on the perimeter
ON
PREM
Every piece — nodes, orchestrator, identity, ledger — runs inside the operator's network. No mandatory Furcate SaaS exists. The binaries are ours; the keys are yours. Outbound connectivity is an explicit choice, never a default.
What on-prem covers
| Operator owns | Keys, data, control plane. No mandatory Furcate SaaS. The binaries are ours; the keys are yours. |
| Orchestrator on-prem | Furcate Control runs inside the operator's network. The orchestrator manages devices, firmware, identity, connectivity. |
| Local identity | Every resource is issued a Furcate machine identity in a local governance framework. Identities live on the perimeter, not in a vendor cloud. |
| Local ledger | Every observation is recorded on the immutable local ledger. The record is yours, kept locally. |
| Outbound, opt-in | Cloud burst, federation, and global coordination exist only when the operator grants them. The default is local. |
Sovereignty is the architecture · cloud is an optional burst tier