MACHINES THAT
THINK TOGETHER
AND PROVE IT
Furcate puts agentic AI next to the sensors, machines and robots it operates — from a microcontroller to a site server, fully offline if you need it. Nodes mesh into one living world model of your site and hold a single view of it, together or cut off alone. And every decision they make leaves a signed, tamper-evident record that anyone can check with open-source tools, including a regulator who has never met you.Proof, not promises
What the model writes
| Observed by | node id · kind |
| Modality | vibration · vision · acoustic · … |
| Decision | in-spec · novel · review · refer |
| Cost | joules spent · per-inference energy receipt |
| Recorded on | operator's immutable local ledger |
OFF-CLOUD
ON-WORLD
For a decade AI lived in someone else’s data centre. The world’s answer is now to build more of them — gigafactories, gigawatt campuses, seven-year queues for a grid connection. That isn’t sovereignty; it’s the same dependency at a different address. The next decade belongs to AI that reads a sensor, watches a camera, drives a motor, balances a load in milliseconds, on-site, even when the network is gone. The model has to live in the world it’s modelling — and the infrastructure has to be the size of the problem, not the size of a city block.
Why it has to be off-cloud
| Senses near signal | A model that decides milliseconds matters can't ride a 300 ms round-trip. The eye doesn't ask the brain whether to blink — the reflex lives close to the receptor. |
| Sovereignty | An operator's perimeter is the model's perimeter. Data of regulated infrastructure can't lawfully leave the body it belongs to. Sovereignty is not a bigger building with your flag on it — it's owning the keys, the data, and the control plane. |
| Energy | Hyperscale AI is power-bound — data centres past 1,000 TWh a year, grid connections queued for the better part of a decade. A mesh of right-sized nodes spends milliwatts where milliwatts do and a rack only where a rack must. Kilowatts you already have, not gigawatts you'll wait years for. |
| Economics | A site running twelve vendor SaaS subscriptions has twelve dashboards and no body. One operator-owned brain collapses them — and pays back inside two years. |
| Continuity | When the network is gone, the world doesn't stop. The model has to keep running where it lives. |
Sovereignty is the architecture · cloud is an optional burst tier
Where it runs · any environment
| Air-gapped | Fully offline. No phone-home. A supported configuration, not a degraded one. |
| Intermittent | Field sites that sync when they can. Local decisions hold; records queue and reconcile when the link returns. |
| On-prem | Full stack on the operator’s perimeter — from a single node to a small on-site data centre. No mandatory Furcate SaaS exists. |
| Cloud-burst | Sovereign cloud (OVHcloud, Scaleway, Nebius) by operator grant — for federation, training, long-range work. Never the default. |
| Federated | Multiple sovereign operators sharing only what they choose, attested via cross-witness. |
One stack · five environments · operator picks
FIVE
TIERS
Furcate runs on five tiers of hardware — from a microcontroller taped to a bearing to a confidential-computing rack in the plant room, plus a policy-gated burst tier beyond the perimeter. Each is shaped by what it senses and what it has to decide — the modality, the latency, the power budget, the network it can rely on. No tier is single-vendor. Together they form meshes inside a site, and meshes form clusters across sites. Orchestration of the local network — devices, firmware, identity, connectivity — lives in Furcate Control, the orchestrator app.
Tiers · same software, five sizes
| Tier | Hardware · example | Deploy | What it does |
Furcate Sensor MCUs & microcontrollers | ESP32-S3 / P4 · nRF54L15 · STM32U5 · RP2350 | Flash over USB Firmware · no host OS needed | Flash firmware with a tiny embedded model directly onto microcontroller hardware. Runs intelligence at the very edge, on-device. |
Furcate Field Linux SBCs & industrial IPCs | Raspberry Pi 5 / CM5 · Radxa ROCK 5C · AMD Ryzen Embedded | CLI · desktop Linux · Windows | Deploy the CPU-compatible Furcate variant to Linux single-board computers and industrial PCs, ARM or x86. Available headless or with a desktop UI. |
Furcate Edge AI GPU & NPU edge modules | Jetson Thor / Orin · AMD Ryzen AI Max+ · Hailo-10H · RK3588 · Ascend 310P | CLI · desktop Linux · macOS · Windows | Deploy the accelerated Furcate variant to edge hardware of any vendor. Available headless or with a desktop UI. |
Furcate Site 1–8 GPU servers & small data centres | Dell PowerEdge · HPE ProLiant · NVIDIA H200 or AMD Instinct | CLI · desktop Linux · K3s 3-node HA | Deploy Furcate to confidential-computing site servers — one box in a comms cabinet or a small on-prem data centre. The site brain, attested end to end. |
Furcate Burst Peer site or sovereign region | Another operator's Site capacity · a chosen sovereign region | Not a deploy target Off-LAN · mutually-attested WAN link | Overflow beyond the perimeter, reached over a mutually-attested link. Policy-gated, never the default, and most deployments never use it. |
Five tiers inside Furcate · milliwatts to a rack · orchestration lives in Furcate Control
MESHES
AND CLUSTERS
A world model is the site’s nervous system. Nodes form meshes on a site. Sites form clusters. Models, data and work move between them by content address — fetched once, reused everywhere. Each node holds the scope it’s shaped for; it asks others when it needs more. Sensors, machines, and robots stop being isolated devices and start thinking as one body — one intelligence spread across the site rather than a fleet of separate brains, and one that stays coherent whether the nodes are meshed together or cut off alone. The operator picks how local stays local and what crosses the line.
How it composes
| Meshes | Nodes on one site form a peer fabric. They discover each other on the local network, then talk to each other directly — no central server in the middle. The operator picks the transport that suits the site. |
| Clusters | Many sites coordinate as one cluster. Each site keeps running on its own; the cluster layer is how they share what they choose to share — observations, model updates, work that one site can't absorb. |
| One view, together or apart | Every node contributes what it observes and reads back the shared picture. That picture converges no matter what order messages arrive in — and a node that loses its link keeps working on what it knows, with its confidence in ageing information visibly falling rather than quietly persisting. Isolation is a supported state, not a failure. |
| It won't average away a liar | A claim needs corroboration before the mesh adopts it, a node's own senses are never outvoted by hearsay, and a peer that asserts two different values for the same thing is quarantined rather than averaged in. Contradiction is a fault to be named, not a number to be smoothed. |
| Models ask models | When a small model needs more — a deeper read, a wider check, a richer modality — it asks a neighbour or a higher-tier node. No node has to hold the whole picture. |
| Content-addressed data | Models and large artefacts move by hash. Once a model is on one node, every other node in the mesh can pull it from there. The same content goes to many nodes, fetched once. |
| Brokered work | Work the local mesh can't absorb gets offered to the broader cluster, then — if the operator allows — to the wider network. Always priority-ordered: local first, then LAN, then off-edge, then refuse. |
Local first · LAN second · off-edge by grant · always fail-soft
EVERY
OBSERVATION
Every observation any model makes is written to an immutable local ledger — local, signed, kept on the operator’s perimeter. The record of what the meshes and clusters saw and decided is there if and when it’s needed.
Properties of an observation
| Local | Generated on the node that made the observation. No telemetry trip to a vendor cloud. |
| Signed | Under the node's own key, with proof of what it was running when it observed. The record says which node made the call. |
| Kept locally | Written to an immutable local ledger inside the operator's perimeter. The record is there if and when it's needed. |
| Yours | Stays inside the operator's perimeter unless the operator chooses to share. Federation between sites is a choice, never a default. |
On the operator's perimeter · no SaaS in the loop
THE
FURCATE PLATFORM
The nodes run at the edge, each under its own Furcate machine identity; Furcate Control orchestrates them across the local network. One architecture the operator owns end to end.
Furcate · platform
Furcate The nodes · edge to site | The nodes — Micro, Small, Base, Site — that sense and decide where the signal lives, from a milliwatt sensor to a small on-prem data centre. The substrate the rest is built on. |
Machine identity Built into every node | Every Furcate resource operates under a Furcate machine identity — a DID and a role minted on the operator's perimeter. Identity is part of the platform, not a vendor service. |
Furcate Control The orchestrator · separate app | Manages the local network, devices, firmware flashing, identity, and connectivity. CLI and desktop. |
Built on
| Local attestation & verification | Powers the immutable local ledger of what each model saw and decided — anchored on Minima, a chain light enough to run on the operator's own edge hardware. Provable on the operator's perimeter — no central server in the loop. |
| Global connectivity · gated | Reaches beyond the local network only when the operator grants it. Closed by default; opening it is an explicit, scoped delegation. Every grant carries a signed capability that names its scope and expiry. |
Local by default · global by grant
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
WORLDS
IT SERVES
One platform, many environments. The same infrastructure problem shows up in different worlds — each with its own modalities, its own protocols on the wire, its own sovereignty boundary. Furcate is the substrate underneath all of them: the nervous system that lets each site’s sensors, machines, and robots act as one.
Where it runs
Energy & grids | Substations, breakers, smart meters, balancing. |
Manufacturing | Cells, lines, weld and bead inspection, predictive maintenance. |
Agriculture | Soil, herd, irrigation, machinery telemetry. |
Transportation & mobility | Vehicle telematics, dispatch, edge perception. Fleets, depots, rail, marine, last-mile. |
Cities & public infrastructure | Streets, transit, lighting, waste, water. |
Drones & uncrewed systems | On-board perception, off-board coordination. |
Space & satellites | On-board inference where the link is the constraint. |
Automotive & SDV | Software-defined vehicles, in-cabin perception, ADAS pipelines. |
Robotics | ROS 2 / DDS fleets — AMRs, arms, humanoids. Robot vendors give the robot a brain; Furcate gives the site one. |
Defence & critical sites | Air-gapped operation, attested workloads, sovereign by default. |
Healthcare | Wards, theatres, RTLS, clinical equipment, fall-risk. |
Buildings & estate | BACnet / KNX, HVAC, lighting, occupancy, energy. |
Conservation | Wildlife, habitats, climate. Sensing where the camera trap is the operator's only ear. |
One platform · sovereign by architecture
DEPLOY
NOW
The next generation of infrastructure isn’t going to ask permission from a hyperscaler every time a sensor fires — and it isn’t going to wait seven years for a grid connection to think. It’s going to see, hear, decide and act as one living system — on the hardware you choose, on the terms you set, on power you already have. Furcate is the nervous system underneath it.
Three ways in
| Pilot | Start with one site. One small or base node, a handful of micro nodes, the local governance and ledger in place. See it run end to end. | Start a pilot ──► |
| Talk | We’ll come to your site, look at the existing fleet, and scope the shortest path to AI you can account for on your own perimeter. | Talk to the team ──► |
| Read | The whitepaper sets out the architecture, the commitments, and — in a section written to be checked rather than believed — exactly what is built and what is not. Published in full, no NDA. | Whitepaper ──► |
End of receipt · thank you