Execution depends on operator memory
Campaigns move because experienced people remember the exceptions, not because the operating model is explicit. That makes pilots fragile and rollouts expensive to trust.
How it works
How governed execution works when a serious screen estate is live.
EnfinitOS aligns execution control, proof, metering, recovery, and commercial accountability as one operating model. The goal is not a nicer dashboard. The goal is a more dependable way to prepare, run, review, and scale screen operations.
Where operators get hurt today
The core problem is usually operating discipline, not media presentation.
Serious estates rarely struggle because they lack a publishing interface. They struggle when execution, approval, proof, recovery, and finance review are spread across people, point tools, and informal workarounds.
Promotion decisions lack governed state
Teams often know a deployment is not ready, but they do not have a disciplined way to express approval posture, readiness, rollback expectations, and production guardrails.
Commercial review drifts from runtime truth
When proof, metering, invoice posture, and settlement context are detached from execution, customer conversations become harder to defend and easier to dispute.
Recovery becomes manual rescue work
When queues stall, ingestion slips, or surfaces misbehave, operators need health, replay, and recovery controls. Without them, incidents become improvisation.
Six layers
Designed as one operating system.
EnfinitOS is strongest when control, runtime, spatial, proof, metering, and settlement are designed together — not stitched together after the fact.
Control
Define who runs what, under which rules, with explicit rollout and promotion permissions.
Runtime
Operate execution across screen estates on a disciplined runtime instead of ad hoc orchestration.
Spatial
Extend governed execution beyond DOOH — spatial and wearable, streaming and audio, vehicle and home, mobile and aerial, and broadcast substrates are first-class in the type system, on the multi-year roadmap.
Proof
Make delivery, activity, and critical actions inspectable instead of inferential.
Metering
Track usage and operational signals required for accountable commercial decisions.
Settlement
Path from verified activity into finance, invoicing, and settlement discipline.
What makes it distinctive
Five things serious operators will not find elsewhere.
The six layers are the operating model. These are the capabilities that make the model real on day one — the deterministic rights gate, the Governance Copilot that explains every decision, the open-source verifier, substrate-ready architecture, and the integration adapter suite.
Rights registry
Every placement is checked against a first-class authority model — civic, property, trademark, contractual. Target p99 under 20 ms on the resolve hot path (engineering budget, not a contractual SLA). Conflicts surface before they reach the screen rather than in a post-incident dispute.
Governance Copilot
The deterministic engine still decides; the Copilot explains. Every refusal, suspension, or upheld challenge gets a plain-English explanation grounded in the underlying audit log, signed and reconcilable byte-for-byte. NIST AI Risk Management Framework and EU AI Act human-in-the-loop posture by construction — not retrofit.
Open-source verifier
The auditor / verifier trio is published under MIT. Regulators, auditors, courts, and third-party compliance tools verify the proof we issue without trusting EnfinitOS as a vendor — reproducible by anyone with the public key and the canonical-JSON re-projection rules.
Substrate-ready
DOOH today; visual screens, spatial and wearable, streaming and audio, vehicle and home, mobile and aerial, and broadcast on the multi-year roadmap. The control spine is substrate-agnostic — every category is first-class in the type system, so the next substrate is configuration, not a rewrite.
Integration adapters
Plug in Broadsign, VIOOH, Hivestack, PlaceExchange, Vistar, or a custom CSV / JSON feed through a shared conformance suite. Same proof, metering, and settlement discipline regardless of the vendor behind the screen.
Daily operating moments
What EnfinitOS is doing underneath the visible workflow.
Here is what the platform is actually controlling when the estate is being prepared, executed, reviewed, and recovered.
How the pilot works
Four stages, explicit before activation.
The first engagement is always a bounded pilot. Scope, commercials, and success conditions are explicit from the qualification call — not back-loaded into a contract reveal.
01
Qualification
Thirty-minute call. We assess fit, urgency, operational reality, and whether the first deployment should be bounded around real screens and a credible operating scope.
02
Operator review
Pilot approval is explicit. Scope, controls, success conditions, and rollout guardrails are agreed before activation rather than improvised later.
03
Bounded pilot
Ninety days. The pilot runs with policy, proof, operational review, and accountable metering so performance can be judged credibly rather than theatrically.
04
Governed rollout
Rollout is a deliberate promotion decision with entitlement, audit, and operating posture — not a silent unlock triggered by optimism.
Commercial model
Bounded pilot. Tiered production. Optional bundles.
Every customer starts with a £15,000 pilot fee for a 90-day bounded engagement. Production is tiered by estate size; annual and two-year commitments earn 15% and 25% discounts respectively.
Tier
Estate size
Monthly platform
Per-screen
Starter
up to 2,000 screens
£2,500 / month
£1.50 / screen
Growth
2,001 – 10,000 screens
£8,000 / month
£1.20 / screen
Scale
10,001 – 30,000 screens
£20,000 / month
£0.95 / screen
Enterprise
30,001+ screens
Custom
Custom
Rollout fee £25,000 one-off on promotion from pilot to production (waived if the pilot doesn't progress). Dedicated topology cell, priority / enterprise support, and custom vendor integrations available as add-ons. Full pricing sheet with worked examples available on request.
Technical readiness
Authored. Reviewed. Reproducible.
The platform is code-complete to pilot-tenant standard. Numbers traceable to specific files in the repository; a CTO-facing diligence pack is available under NDA.
13
Terraform modules
Authored infrastructure spanning VPC, RDS, ECS, KMS, WAF, and Backup.
87+
Commits landed
Rights registry, integration adapters, GDPR endpoints, drill harnesses, CMK sweep.
< 20 ms
p99 resolve budget
Engineering target on the hot path per ADR-0005. Not a contractual SLA — an honest budget.
6
Integration adapters
Broadsign, VIOOH, Hivestack, PlaceExchange, Vistar, plus a generic CSV / JSON feed.
By environment
How the operating value changes by estate
The control spine is shared, but the practical business value should sound specific to the environment being operated.
DOOH networks
Pain point
Multi-site execution becomes brittle when pilots, approvals, and rollout decisions depend on informal operator memory and inconsistent promotion logic.
What EnfinitOS improves
EnfinitOS can give the network a governed route from pilot to rollout, with explicit readiness, traceable proof, and a runtime posture that does not rely on hidden coordination.
Retail media operators
Pain point
Store estates, partner surfaces, local exceptions, and commercial commitments create pressure to move quickly without losing control over what is actually allowed to run where.
What EnfinitOS improves
EnfinitOS can keep estate-level execution tied to governed permissions, store-aware runtime control, and commercial accountability that still traces back to live operating activity.
Venue, cinema, and exhibition groups
Pain point
Time-sensitive deployments across many locations become risky when delivery, approvals, and fallback handling all happen too close to the event window.
What EnfinitOS improves
EnfinitOS can structure readiness, delivery, and recovery so launch windows are less dependent on heroic intervention and more anchored in explicit operating state.
Transit and mobility estates
Pain point
Long-lived public deployments need stronger entitlement, operational review, and recovery posture than lightweight publishing flows are designed to support.
What EnfinitOS improves
EnfinitOS can support a more durable runtime and control posture where health, replay, governed execution, and incident handling matter as much as the content itself.
CTV and streaming networks
Pain point
Territory licensing, age-gating, and rights provenance get reconciled by spreadsheets and post-incident audit instead of being enforced at runtime.
What EnfinitOS improves
EnfinitOS resolves territory, audience predicates, and rights provenance on the hot path before any frame ships, with the streaming player SDK enforcing the same gates the operator-side runtime does.
Spatial, AR, glasses, HUD
Pain point
Spatial placement discipline — anchor stability, occlusion, real-world safety zones — has no governed substrate and ends up enforced by reviewer instinct.
What EnfinitOS improves
EnfinitOS makes spatial anchors, occlusion contracts, and behavioural constraints first-class, so AR / glasses / HUD / volumetric / hologram operators get the same proof posture DOOH already has.
Robotics and drone fleets
Pain point
Geofencing, kinematic envelopes, Remote ID compliance, and BVLOS waivers live in fleet-management tools that don't share an audit surface with brand-side execution.
What EnfinitOS improves
EnfinitOS attaches behavioural and territorial constraints to the same rights / proof spine, so an autonomous fleet's safety posture and a brand campaign's accountability sit in one ledger.
Satellite, aviation, and maritime
Pain point
Ground-segment, IFE, and shipboard IPTV vocabularies sit in vendor silos with no shared evidence model — and safety channels (GMDSS, distress frequencies) need refusal-list discipline that vendor APIs don't enforce.
What EnfinitOS improves
EnfinitOS speaks the substrate-agnostic vocabulary; the satellite / aviation / maritime adapters translate carrier, MODCOD, ARINC, and IALA VTS terms in and out — with GMDSS-style refusal lists enforced before any inventory ships.
Timeline
Now → April 2027 launch → first pilots live.
Why we're talking in 2026 about a 2027 launch: the platform is code-complete; the legal entity forms in early 2027 and the pilot cohort activates in April. Transparent framing so you can make an informed decision.
Q2 2026
Today
Code complete. Staging plan ready. Pre-launch pilot conversations underway.
Q4 2026
LOIs
Pilot LOIs signed with the initial cohort of ten tenants.
Feb 2027
Discharge
Founder discharges. Entity formation begins. Bank + Stripe KYC in flight.
Apr 2027
Launch
First pilot cohort activated. Governed rollout begins.
Cohort
Ten pilot slots. First-come-first-served against a signed LOI.
The first cohort is capped at ten tenants — matching the current certified cell capacity. Slots are allocated against non-binding Letters of Intent, with formal contracting on the April 2027 launch.
- Thirty-minute qualification call.
- Non-binding LOI on fit confirmation — no fee, no commitment.
- MSA signs within the first four weeks of April 2027.
Reserve your slot
A bounded pilot designed to become a rollout.
The commercial path is explicit from the first conversation — pilot fee, rollout fee, per-screen fee, and usage posture aligned to controlled execution rather than a demo-only exercise.