furcateDeploy ──►
Furcate · environmentsAny deployment shape

ANY
ENVIRONMENT

Furcate is the same stack across deployment shapes. Air-gapped or cloud-burst. One site or a federation. The operator picks; the platform adapts. Sovereignty is the architecture; everything else is a choice.

Modes

Air-gapped

Fully offline. No phone-home.

Nodes operate without any outbound network. Updates land via signed bundles. Receipts and observations queue locally and stay locally. Federation is off. A supported configuration, not a degraded one.

Intermittent

Sync when you can.

Field sites and vehicles that come and go from the network. Local decisions hold while the link is down; records queue and reconcile when it returns. The model never waits on a round-trip.

On-prem

Full stack on the operator's perimeter.

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.

Cloud-burst

Sovereign cloud · by grant.

When training, federation or long-range work needs more than the local cluster can supply, the operator can open a scoped gate to a sovereign cloud they control. Never the default; always reversible.

Federated

Many operators, one model of the world.

Multiple sovereign operators each run their own local stack, sharing only what they explicitly choose. The wider model is the sum of what each side opens up. Each side keeps what it doesn't.

One stack · five environments · operator picks

Which mode for which job

Real-time control loops

On-prem or air-gapped

Latency budget shorter than any WAN path.

Field operations

Intermittent

Network is the variable. Decisions cannot wait on it.

Multi-site coordination

Federated

Each site is sovereign; the cluster layer composes what they share.

Heavy training or long-range work

Cloud-burst

Local compute is the variable. The operator decides what to open.

Pick or mix · change any time