ArcFlow
Company
Managed Services
Markets
  • News
  • LOG IN
  • GET STARTED

OZ brings Visual Intelligence to physical venues, a managed edge layer that lets real-world environments see, understand, and act in real time.

Talk to us

ArcFlow

  • World Models
  • Sensors

Managed Services

  • OZ VI Venue 1
  • Case Studies

Markets

  • Sports
  • Broadcasting
  • Robotics

Company

  • About
  • Technology
  • Careers
  • Contact

Ready to see it live?

Talk to the OZ team about deploying at your venues, from a single pilot match to a full regional rollout.

Schedule a deployment review

© 2026 OZ. All rights reserved.

LinkedIn
ArcFlow Cloud

ArcFlow Cloud · World Model Workspace

Spatial AI you can inspect

ArcFlow builds a continuous model of what's happening in your space. The Workspace is where that model becomes legible — entities, confidence scores, event history, and model state — to operators, engineers, and anyone else who needs to know what the engine knows.

Get started freeAll Cloud services

The model decides everything. It's been invisible.

ArcFlow builds the Venue Graph continuously — cameras, tracked entities, zones, event detections, spatial relationships. Every fact is graded by the ArcFlow Evidence Model: observation class (observed, inferred, or predicted), confidence score, and provenance chain. Every framing decision, every trigger, every stat derives from this model.

Models that run silently are models no one trusts. When a camera frames wrong, there is nowhere to ask “what does the model think is in that zone?” When you go live at a new venue, there is no structured gate that says “all entities observed, confidence above threshold, validation passed.” Without the Workspace, you find out the model was wrong by watching the output fail.

Built for every stakeholder

Operators

Validate model state before going live at a new venue. Sign off on a structured checklist — entities present, cameras calibrated, confidence above threshold — then proceed with confidence.

Engineers

Debug framing and detection decisions directly in the graph. Inspect confidence scores, entity properties, and observation history at the source — not inferred from output.

Partners & investors

See the intelligence, not just the output. The Workspace makes the Venue Graph legible to anyone who needs to understand what ArcFlow knows about a venue.

Capabilities

Three phases of observability

Phase 1 is available today. Phases 2 and 3 ship as the dependency chain completes.

Phase 1

Entity browser

Every camera, zone, and tracked object in the Venue Graph — type, label, confidence score, last-seen timestamp. Click any entity to inspect its properties and full observation history.

Phase 1

Event stream

Chronological feed of what ArcFlow has detected in the last 24 hours: entity entries, exits, state changes, anomalies. Filterable by type, entity, and time window.

Phase 1

Readiness gate

Structured validation before any operation goes live: all required entities present, cameras calibrated, no stale entries, confidence above minimum. Any operator can sign off. Any stakeholder can audit it.

Phase 1

Fleet visibility

Which ArcFlow engines are online, what venue each serves, entity count, and model confidence — all in one view. No SSH, no dashboards, no manual polling.

Phase 2

Zone definitions

Define and edit zone geometry that ArcFlow uses to structure the Venue Graph. Zones created here are consumed by ArcFlow's framing and trigger system.

Phase 2

Model version history

See how the Venue Graph has changed across sessions and deployments. Compare entity counts, confidence distributions, and zone coverage across time.

Phase 3

Per-venue model health

Each venue card shows World Model freshness and last validation status at a glance. Green means ready to operate. Red means investigate before committing.

Phase 3

Anomaly alerts

Notify when the model drifts from its last validated state — a device moved, an obstruction appeared, confidence degraded. Alerts reach operators before outputs degrade.

Phase 3

Cross-venue comparison

Compare Venue Graphs across similar stadiums — normalization, template detection, fleet-wide confidence benchmarks. Patterns visible only at fleet scale.

How it works

Client-side graph, server-authoritative deltas

The browser runs an embedded ArcFlow WASM instance with a local GraphStore. Scoped graph fragments sync from the relay via WAL deltas — only the entities and observations the operator needs for the current view, nothing more. Queries run client-side in under a millisecond. The relay never serves query results; it serves delta sequences that the browser applies locally.

1

World issues a scoped JWT

Token carries org_id, venue_id, and tier — scopes the relay connection to exactly one venue's graph fragment.

2

Browser restores from IndexedDB

Last session's snapshot loads instantly from local storage. No round-trip needed for entities the operator already viewed.

3

Relay sends WAL deltas

Only changes since the last known sequence number travel from the relay. New entities, updated confidence scores, new observations — nothing else.

4

WASM applies deltas, Live Delta Stack updates views

The local GraphStore processes each delta via the Live Delta Stack. Materialized views (entity list, event stream, validation checks) update automatically. React re-renders only what changed.

Scope budget

Entity list (81 entities)~200 KB
Event stream (24h, 500 events)~150 KB
Confidence map (IDs + scores)~4 KB
Validation issues (anomalies only)~10 KB
Total Phase 1 scope~364 KB

Well within the 50 MB OPFS budget for browser WASM. Offline-capable — restores from IndexedDB when relay is unreachable.

Design principle

Read-only by default

The Venue Graph is built by ArcFlow from sensor data. Direct human edits would corrupt the model — a manually inserted entity with wrong coordinates would propagate through framing decisions, stats, and replays.

The Workspace is read-only on the World Model by default. Configuration that affects model building lives in ArcFlow config (Phase 2: zone definitions, camera role assignment). The Workspace surfaces the effects of that configuration — it does not bypass it.

Dependency chain

Built on every initiative before it

The Workspace is the destination of the ArcFlow Cloud initiative chain. Each upstream initiative provides a capability this one depends on.

2
Auth— User authentication — who you are
4
OAuth— Third-party login — how you sign in
5
Orgs— Org and venue scoping — what you can see
6
Workspace Shell— The container this page lives in
7
Device Mgmt— Astros and ArcFlow Engines as registered entities
8
ArcFlow Identity— World-issued JWTs that scope relay access
0010
World Model Workspace— This — makes the Venue Graph inspectable

Included with ArcFlow Cloud

The World Model Workspace is available on every ArcFlow Cloud account. Engine registration and basic dashboard are free. Phase 1 is live now.

Get started freeAll Cloud services