How the Oavora platform works
One backend. Many players. Identical behavior across every screen environment — engineered for resilience, security, and scale.
Three layers, designed to work together
Your team works in the management layer. Oavora's backend handles content, licensing, and telemetry. Your players run the same engine on every supported platform.
Oavora cloud workspace
Where operators manage content, schedules, screens, and reports. Web-based, role-based, and multi-tenant.
Customer workspace
Each end-customer gets a scoped, branded environment with their own users, screens, content, and reports.
Reseller workspace
Partners manage all their customers and licenses centrally, with rolled-up reporting and white-label options.
Real-time MQTT control plane
Encrypted, low-bandwidth bidirectional channel between dashboard and every player.
Content delivery
Files are uploaded once, stored once, and synced incrementally to every player that needs them.
Licensing & identity
Signed device licenses, hardware fingerprints, and role-based permissions across the platform.
Same player engine, every platform
Android TV, Windows, Tizen, webOS, and web players all run the same playback engine and protocol.
Offline-first playback
Players cache content locally and keep playing during outages. Sync resumes automatically when online.
Telemetry & heartbeat
Every player sends periodic heartbeats with status, current playlist, storage, and last-played history.
Run the same Oavora experience on every screen
Five player environments, identical content management, identical behavior with the server.
The screen lifecycle, simplified
Every screen in Oavora goes through the same predictable lifecycle — register, sync, monitor, retire.
Register
Install the player app on your screen, enter the pairing code from the dashboard, and the device is registered to your workspace with a signed license.
Sync
Assign content and schedules. Files sync incrementally to the player and cache locally for offline-resilient playback.
Monitor
Players send heartbeats with status, current playlist, and storage. The dashboard shows live network health.
Retire
Decommission a screen with one click — the license is freed, content is purged, and the device is removed from inventory.
Secure, incremental, resumable
Files are deduplicated by hash and synced incrementally. If a player loses connectivity mid-sync, it resumes — never re-downloads what it already has.
Players keep working when networks don't
Each player keeps a local cache of approved content. If connectivity drops for hours or days, scheduled playlists keep playing — and the player automatically catches up when it reconnects.
Sub-second control across the network
Push commands like "refresh", "restart", or "force sync" reach every player almost instantly — over a TLS-encrypted MQTT channel that uses minimal bandwidth.
Signed, hardware-bound, transferable
Each player is paired to a signed license bound to its hardware fingerprint. Activate, deactivate, or transfer licenses at any time — all from your workspace.
Healthy devices, automatically
Storage cleanup rules remove old, expired, or unused content from devices automatically — keeping every player fast and responsive.
Pull data from the systems you already run
Native widgets for weather, exchange rates, and announcements — plus an HTTP integration layer for connecting POS, queue systems, or your own internal data sources.
Cloud-hosted or self-hosted — same product, your call
Oavora Cloud
Fully managed, regional hosting, automatic upgrades, and 99.9% uptime targets. Best path to production for most teams.
Oavora On-Premise
Run inside your datacenter or private cloud. Full data sovereignty, internal SSO/LDAP, and air-gap support available.