Pull-based, deterministic runtime.
VCMP is built on a fundamentally different architecture. Devices pull signed bundles. Content is immutable. Playback is verified.
How VCMP works.
Architectural foundations.
Pull-Based Delivery
Devices pull content on their own schedule. No push. No drift. Full control.
Immutable Bundles
Content is published as signed, versioned bundles. No mid-flight edits.
Verified Playback
Devices verify bundle signatures before playback. Cryptographic integrity.
Multi-Tenant Isolation
Full data separation between organisations, partners, and clients.
Audit Everything
Every action logged with user, timestamp, and resource. Full trail.
API-First Design
RESTful APIs for every capability. Integrate with existing systems.
Push-based systems fail.
Traditional signage uses push-based delivery. Content is pushed to devices, which creates drift, inconsistency, and unpredictable device states.
VCMP uses pull-based delivery. Devices check for updates on their own heartbeat cycle, download signed bundles, verify integrity, and play. Simple. Predictable. Reliable.
- Devices always have a known, verified state
- Network failures don't corrupt device content
- Offline devices sync automatically when reconnected
- No race conditions or partial updates
Push-Based (Traditional)
- • Content pushed to devices
- • Devices can have inconsistent states
- • Network failures cause partial updates
- • No verification of device state
Pull-Based (VCMP)
- • Devices pull on heartbeat cycle
- • Content verified before playback
- • Offline devices sync on reconnect
- • Deterministic, predictable state