Praecise Furcate

Furcate for production, from Praecise

Your own infrastructure, from the rack to the sensor.

Praecise Furcate is Furcate OS made ready for production: the open operating system, Furcate edge hardware, the device and protocol catalogue industry runs on, fleet operations across sites, and support from the team that builds it. Every reading says how far it can be trusted. Every command is signed, ruled on and recorded. Nothing outside the building can stop a machine inside it.

Built on
Furcate OS · open source, Apache-2.0
Runs on
your machines, at the edge, or on Praecise Cloud
Hardware
Furcate Leaf · Furcate Node · Furcate Hub available soon
Devices
cameras, microphones, sensors, meters, actuators
Support
from Praecise, which develops Furcate

The story

Infrastructure that belongs to the people who run it, down to the last sensor on the wire.

A building, a plant or a city is not made of servers. It is made of meters, cameras, valves, drives, batteries and a great many sensors, and the smaller the device, the more likely it is to be trusted with no identity at all. A temperature probe on a shared bus can be impersonated by anything else on that bus, and most valves will open for whoever asks.

The platforms built around these devices solved collection long ago. They did not solve belief. A value from an unauthenticated meter arrives looking exactly like a value from a sensor whose firmware was measured at boot, and a cloud the operator does not own sits between them and their own machines.

Furcate started from the opposite end: identity produced by each machine's own silicon, authority as a key the operator holds, and a record of every decision, including every refusal. Praecise Furcate carries that model all the way down. A Furcate leaf, small and inexpensive, sits beside the devices that never had an identity, gives each of them an identity under its own hardware key, signs what they report and checks every order before it drives an output.

The result is one system from the rack to the sensor, at the scale of a home, a business or a city, in which every reading states how far it can be trusted and every command is ruled on before it happens. It is built to keep working when the network does not, and to answer to no one outside the building.

01

Three things every platform gets wrong(3)

And the three Praecise Furcate is built around.

Collecting readings is solved. Knowing which ones to believe is not.

Industrial, building and security platforms move enormous volumes of data, then treat a value from an unauthenticated meter on a shared bus exactly like a value from an attested sensor. They accept a write to a valve from anything that can reach it. And most of them need a cloud they own to run at all.

  1. 01

    Trust is graded

    Every reading carries its rung.

    Device-native, leaf-signed, bridged or observed: each value states how it reached you and what vouches for it. Exports, policy and agents act on the rung, not on hope.

  2. 02

    Control is enforced at the device

    A write is an order, not a packet.

    Proposed, ruled on by policy, approved by a person's passkey when policy says so, signed, and checked again by the leaf that drives the output. Interlocks hold when everything above them is gone.

  3. 03

    It is yours

    No control plane but your own.

    Identity comes from each machine's silicon, authority is a key you hold, and a site keeps running, stopping and erasing with the uplink cut.

02

From a home to a city

One system at every size.

The same identity, policy and record, whether there are three machines or thirty thousand.

A home lab runs the open base. A business adds leaves and a few nodes. An industrial site adds the field bridges and the protocol catalogue. A city runs many sites as one operator, each still standing on its own when the network does not.

ScaleTypicallyRuns on
Home and makersa server, a small board, a few sensorsFurcate OS, free, at furcate.org
Businessan office, a shop, a clinic: cameras, rooms, energyPraecise Furcate, a few nodes and leaves
Industrial sites and campusesplants, buildings, labs, private AI hallsPraecise Furcate with the industrial catalogue
Cities and infrastructurestreet lighting, utilities, transit, district energy, public buildingsPraecise Furcate across many sites, operated with Praecise

03

The stack

One operating system, from the sensor to the site.

Leaves, nodes and a site, on one local network you own.

Furcate leaves sit next to the devices and sign at the source. Furcate Nodes are the only door to the devices on their segment. The site controller holds policy, the ledger and the kill switch. Praecise Furcate operates all of it across sites, fully air-gapped or connected through Praecise Cloud, with the same keys either way.

UPLINK — OPTIONALCLUSTER PLANE — SIGNED ENVELOPESLEAF LINK AND DEVICE SEGMENTDEVICES — UNCHANGED gateway · holds no key site controllerpolicy · ledger · kill switch · console Furcate Nodeadapters · bus · local AI Furcate Hubvideo · provenance · redaction field bridgeRS-485 · CAN room leafThread · Zigbee · BLE camera guardPoE directisolated segment meterssensors · lockslegacy cameraPLC · BACnet · MQTT

04

Furcate hardware

Furcate Leaf, Furcate Node, Furcate Hub.

Hardware that gives an old device an identity and a new one a root of trust.

Three tiers, one trust model. Each holds its own hardware root of trust, speaks the same signed envelope, and answers to the same policy, ledger and kill switch.

available soon

Furcate Leaf

Beside the devices: a bus, a room or a panel. Gives every attached device an identity, signs at the source, and enforces interlocks with no network.

Reaches
serial buses, radios, sensors, I/O
available soon

Furcate Node

The only door to the devices on its segment. Protocol adapters, the site bus, storage and the provenance log; parent to the leaves around it.

Reaches
IP devices, leaves
available soon

Furcate Hub

Sees and hears for the cameras and microphones a site already has: video and audio models next to them, with redaction before anything leaves.

Reaches
cameras, microphones, models

05

Devices and protocols

Direct where the network reaches, through a leaf where it cannot.

Cameras, microphones, sensors, meters and actuators, on the protocols they already speak.

Devices on IP attach directly to a node through adapters that run as attested, sandboxed workloads. Devices on serial buses and low-power radios attach through a leaf. Both arrive as the same signed reading, described by one schema the console, the bus and agents all read.

FamilyProtocolsPath
Cameras and audioONVIF Profile T/M/G, RTSP, WebRTC (WHIP/WHEP), SRT, UVC, AES67, SIPdirect · guard
BuildingsBACnet/IP and MS/TP, KNX IoT, Matter, Thread, Zigbee, DALI-2, M-Bus, Modbusdirect · room leaf · field bridge
IndustryOPC UA (incl. FX), Modbus TCP/RTU, MQTT and Sparkplug B, PROFINET, EtherNet/IP, CANdirect · field bridge
EnergyIEEE 2030.5, SunSpec, OpenADR 3.1, OCPP 2.1, IEC 61850, DNP3direct · field bridge

06

Operations

What a production fleet needs on the first day.

Fleet operations that keep the trust model intact.

Praecise Furcate adds what running many sites asks for: rollout in watched waves, device posture and quarantine, EU Cyber Resilience Act reporting, energy and tariff accounting, forecasting, provenance with redaction, and agents that can propose but never act alone.

  1. 01

    Posture and quarantine

    Firmware, credentials and exposure per device, joined to known vulnerabilities, deciding what a device may publish.

  2. 02

    Compliance evidence

    Vulnerability reports drafted for the 24-hour, 72-hour and 14-day deadlines, SBOMs per device and adapter, signed update evidence.

  3. 03

    Governed agents

    Agents read the whole site through MCP and propose. A person approves with a passkey. The ledger records both.

07

Open, and Praecise Furcate

The same system. One is supported for production.

Furcate is open source. Praecise Furcate is Furcate for production.

Everything that makes a trust claim, and everything a person needs to run their own machines, is Apache-2.0 at furcate.org. Praecise develops it and stewards it. Praecise Furcate is what production fleets need out of the box, with hardware and support behind it.

Furcate OSPraecise Furcate
Identity, attestation, policy, ledger, kill switchyesyes
Leaf firmware and reference designsyesyes, plus Furcate hardware
Adapters a home lab needsyesyes, plus the industrial catalogue
Fleet rollout, posture, compliance, energy, forecastingyes
Agents, redaction, video search, multi-siteyes
Support from the team that builds itcommunityPraecise

08

Place your first site

Tell us what you run and where.

Say what you operate today, and Praecise replies with what it takes to run it on Furcate.

Sites, machines, devices, the protocols they speak, and what has to keep working when the uplink does not. contact@praecise.com