Infrastructure that orchestrates
the moving parts of physical operations.
Cirquit is a distributed operations platform for organisations where data, devices, workflows, payments, inventory, and identity exist together as one system.
Cirquit models physical operations as a set of shared layers — a single operational state that different systems and experiences can build on.
That shared state is exposed through multiple surfaces — point-of-sale, kiosks, handhelds, dashboards, loyalty, screens, and experience systems — each drawing from the same underlying truth.
Platform v Point of Sale
Our Point of Sale for SME and day to day businesses is Pos.Work by Cirquit,
built on top of this infrastructure.
This website describes the Cirquit Platform.
The failure of fragmentation
Operational reality is noisy. Systems were built to ship features, not to model the physical world.
Separate tills, independent payment rails, bolt-on loyalty and isolated inventory create operational drift. Work that should be a single event becomes a reconciled story told after the fact. Policy leaks, responsibilities blur, and day-end becomes an investigation.
- POS tightly coupled to a single payment provider
- Inventory reconciled after the fact, not as a primary event
- Hardware integrations repeated per site and per vendor
- Identity split across cards, apps and paper lists
- Offline incidents resolved by duct tape and spreadsheets
This is not an implementation problem; it is an architectural one. The question is not which app does “X” — it is how state is recorded, addressed and governed across the operation.
The POS demonstration is one operational surface of our platform — a visible example of how the system expresses its model in the shop. It’s an illustration, not the whole proposition: Cirquit is the underlying operating layer that powers many surfaces, from kiosks to handhelds to fleet controls.
POS surface
The point-of-sale interface is one expression of the infrastructure.
Open the POS surface →Cirquit model
Not a suite of apps — an operating layer.
Cirquit makes a single source of truth the primary object. Events are first-class: every sale, inventory move, tap, print, and internal requisition is an identity-bound transaction that feeds the event ledger. Devices are endpoints of that ledger, not authoritative islands.
- single source of truth
- identity-bound transactions
- event ledger as system of record
- control plane for device & policy orchestration
The transaction spine
At the heart of Cirquit is an event ledger: a sequenced, identity-linked record of every state change. Not just payments — everything that changes state becomes a structured transaction bound to an identity, a location, and a device.
Because the ledger is the primary source, reconciliation is deterministic. State is replayable, auditable, and portable. This makes operational questions tractable — who did what, where, and when — without stitching together CSV exports after the fact.
The control plane
Cirquit provides the operational control plane: device provisioning, policy enforcement, terminal assignment, fleet governance, and permission models live here. It’s how you assert operational intent and ensure devices behave as your business requires.
When policy changes, you change it once — and the control plane converges the fleet. When a device joins, it is assigned a role, a permission set, and a sync policy; its behaviour is a product of that configuration, not custom code on each device.
Hardware abstraction & device orchestration
Payment terminals, scanners, printers, NFC readers, kiosks, and scales are interchangeable surfaces. Cirquit abstracts hardware through capability descriptors and policy adapters: one ledger, many surfaces.
The practical outcome: swap a supplier, not an architecture. Integrations are mapped to capabilities (scan, print, tap, weigh), not vendor classes — lowering vendor lock-in and simplifying rollout at scale.
Offline resilience
Cirquit Edge (local mirror) ensures operations continue when networks do not. Orders queue locally, the ledger accepts events, and reconciliation occurs automatically when the control plane is reachable again. Deterministic replay prevents duplication and keeps your financials and inventory honest.
Resilience is architectural: it is planned, tested, and auditable — not a reactive afterthought.
Surfaces of the same layer
POS, kiosks, handhelds, loyalty, internal ordering, fleet controls, dashboards — these are not separate products. They are different manifestations of the same infrastructure, each drawing from the ledger and the control plane.
This makes UX decisions simple: choose the surface that best serves an interaction; the truth remains the same.
Cirquit does not connect systems. It lets systems share reality.
A light turns on — a state changes.
An action occurs — an identity records it.
A device observes it — the ledger stores it.
The light turns off — the ledger updates.
Every surface simply reacts to the same fact.
event_value = duration × rateCirquit build
Infrastucture certainty
End-of-day reconciliation becomes a query.
Device onboarding becomes assignment.
Inventory correction becomes an event, not a spreadsheet.
Offline incidents become deterministic replays.
Policy changes become a single publish, not hundreds of pushes.
Identity becomes a resolved reference, not a set of silos.
Operations teams stop inventing local workarounds; they follow a single recorded state. Tools are chosen for interaction, not for state-keeping.
Platform and ops move from firefighting to governance: changes are authored, reviewed, and published from the control plane rather than patched on devices.
Planning horizons lengthen because the same state model can be reused across stores, counters, and fleets — the unit of change becomes policy and model, not per-site code.
You will not run parallel spreadsheets to reconcile sales.
Instead, you query the ledger and trace every event to its origin.
You will not perform manual device reconfiguration across sites.
Instead, you assign roles and policies; devices converge automatically.
You will not stage a migration to “move data” between systems.
Instead, you operate the same state model while migrating interfaces incrementally.
You will not accept unclear audit trails after an incident.
Instead, you replay and reconstruct state deterministically for post-mortems.
Engagement and Go-Live
Cirquit becomes accurate by observing and stabilising real activity. Engagement follows a short operational sequence:
| Stage | What happens | Outcome |
|---|---|---|
| Phase 0 | We observe the environment and connect to real activity — devices, stock movement, payments and reporting. | A shared picture of how the organisation actually operates. |
| First Loop | Cirquit runs alongside existing routines and records transactions without replacing behaviour. | The model aligns with reality. |
| Go-Live | Cirquit becomes the primary operational surface. | Daily work runs through the system. |
| Stewardship | Adjustments and new capabilities are introduced as part of normal operation. | The system evolves with the organisation. |
There is no “handover”. Cirquit remains part of operations as conditions change.