Fleet Command

One control plane. Every environment.

The unit of isolation is the business, not the location. One environment runs all of a business's locations, channels, and devices; anything that requires separation receives its own. The estate is declared once, converged continuously, and governed by one authority.

01 / STATE

The fleet converges on what you declare.

The fleet is described in a declarative manifest: environments, versions, tracks, policies. The control plane continuously compares declared state against observed state and converges the difference — planned, applied, verified, and recorded.

declared statemanifest · versionedobserved statetelemetry · healthdriftconvergence planconstraint-awareapply · verify · recordthe fleet converges on what is declared
Manifest

Single source of truth

What runs where, on which track, under which policy — declared and versioned. The manifest is the fleet.

Drift

Corrected, not reported

Divergence between declared and observed state is detected and converged without operator intervention.

Constraints

Windows and guards

Maintenance windows, restart guards, and placement constraints bound when and where change applies.

controlplaneHOST-Aone env per businessHOST-Bone env per businessreconcile →screenterminalsensorLOCATIONS · EDGE · pull← pull
02 / TOPOLOGY

Hosts, environments, devices. One registry.

Hosts join the fleet and offer capacity. Each business receives one environment; every location it operates runs through it. Separate businesses — or anything requiring hard separation — receive separate environments. Devices enroll once and pull configuration for life.

Capacity

Pooled, not pinned

Warm capacity provisions new environments in under sixty seconds and evacuates a failing host without ceremony.

Isolation

One business, one environment

All of a business's locations share its environment. Separate businesses run in separate environments, placed by declared constraint — never by hand.

Edge

Enrolled for life

Screens, terminals, and sensors receive releases by track, tolerate disconnection, and reconcile on return.

03 / OPERATIONS

The operations team is an agent fleet.

Every fleet operation — rollout, migration, backup, placement — is a typed operation. Agents execute them at machine tempo. People see decisions, evidence, and nothing else.

TYPED CONTROL

Operations agents can drive

The control surface is typed end to end: declared parameters, scoped credentials, required confirmation for destructive actions. Built for agents to operate; legible to the people who review them.

BUDGETS

Hard stops, continuous heartbeat

Every operating agent carries a budget with a hard stop and reports heartbeats with work evidence. An idle agent is an incident. An overspending agent is stopped, then reported — in that order.

EVIDENCE

One record for the entire estate

The ledger aggregates across the fleet: every deployment on every environment, every gate outcome, every reversion, every approval. One queryable record answers for the estate.

AUTHORITY

One person governs a hundred locations

Fleet-wide changes pass the same approval gates as everything else. The platform brings decisions to the person who holds authority — never operations. That is what makes the ratio possible.

Command the fleet.

Turbine onboards a limited number of organizations each quarter. Selection favors operations prepared to run under agents.