SolutionsAdvertising NetworkAd Agency
ProductsAdveles Mirror KitAdveles OSAdveles ControlAdveles VenueAdveles Ads
EconomicsFAQContact
Device Layer · Layer 2 of 5

An OS designed
for one task

Run your network 24/7 without manual intervention. AOSP-based, closed ecosystem, zero Google dependencies. Updates over the air, works offline.

Adveles OS interface
<10 seconds
Boot time
99.9%
Uptime guarantee
0
Manual restarts
OTA
Updates
Architecture

Three principles the OS stands on

Security
  • Closed ecosystem — no Google Play, no third-party apps
  • Signed OTA — updates verified by signature
  • Read-only root — system files can't be modified
  • VPN tunnel to Control — all traffic encrypted
Reliability
  • Watchdog service: restarts player on hang in <3 seconds
  • Offline cache: up to 72 hours of content without internet
  • Auto-recovery: self-recovers after power failure
  • Health check every 30 seconds with report to Control
Manageability
  • Silent OTA: updates during off-hours without show interruption
  • Remote config: change settings without physical access
  • Batch deploy: update thousands of devices simultaneously
  • Impression tracking: every show counted at OS level
Why AOSP without Google

Zero external dependencies — this is strategy, not limitation

Google services mean: mandatory device registration, account deactivation risk, Google Play policy dependency, analytics leakage to third parties.

Adveles OS — it's our complete control. We decide when and what to update. No forced restarts, no telemetry we didn't order.

0
Not a single third-party service in the critical path
100%
Firmware, updates, analytics — all ours
AOSP
Open foundation + closed Adveles layer
SLA
Documented uptime in contract with operator
Adveles OS technical architecture
Adveles Control integration diagram
Integration

OS → Control: unified data stream

Every impression fixed at OS level goes to Control in real-time. Operator sees what's happening with each device — online, offline, temperature, last ping, player status.

Content updates go the opposite direction: Control → OS → screen. Latency — seconds.

Data Flow
OS records every show with timestampControl receives data, updates analyticsPartner Venue shows income
Next platform component
SaaS
Control

Need technical documentation?