Players, cameras, tracking and one core.

What runs under every solution, in plain words: desktop apps at the screen, cloud web apps for the team, one protocol between them, and one core that keeps identity, prices, licences and play records.

14products on one engine
5groups: App, Control, Insight, Support, Activation
1core for identity, prices, licences and play records
AOS
  • Identity & balance
  • Pricing engine
  • Licensing
  • Order queue
  • Play records

Every product, one core underneath.

One group sells, one runs the screens, one measures, and two support the rest, all on the same engine. Adding a product never means adding a system.

AppWhere the market buys airtime and campaigns are planned
ControlRuns the screens, keeps the schedule and records the proof
InsightCounts people and vehicles and turns them into reports
SupportTracks the vehicles that carry media
Kliktron AOSAdvertising Operating System: the records every product shares
  • Identity & balance
  • Pricing engine
  • Licensing
  • Order queue
  • Play records

The stack, in plain words.

Five ideas explain how the system behaves in the field.

  1. Desktop apps at the screen

    Vertex Player and Klikplayer Mini Site are desktop applications built in Rust on Tauri, with a React interface. They run on the computer that drives the screen and talk to the operating system directly, so video decoding stays hardware-accelerated.

    • One Vertex instance per videotron
    • Each display window renders in its own isolated player
    Vertex Player Window Control on the computer beside a videotron
  2. Offline-first local databases

    Schedule, customers, rates, balance and play logs live in a database on the machine: SurrealDB in Vertex Player, SQLite in Klikplayer Mini Site. The cloud adds reach; it is never a condition for airing. Logs wait on disk and sync when the line returns, without duplicates.

    NetworkLine down
    ScreenStill airing

    Schedule, rates and balance live on the machine at the site.

  3. Cloud web apps for the team

    The team works in the browser: Vertex Monitoring for the fleet, Klikplayer Mini Cloud for indoor networks, Soca Insight Cloud for audience reports, Kliktrack Cloud for vehicles, Photospace for activations, and the Kliktron® App as a web app for advertisers.

    • Sign-in by one-time password, with rate limits and lockout
    • Roles and tenant masking enforced in the data layer
    Klikplayer Mini Cloud device list in a browser
  4. Kliktron Protocol and telemetry

    Commands from the cloud, such as a slot check from the Klik App, travel over NATS as the Kliktron Protocol. Telemetry runs on a separate path: heartbeat, content freshness and a preview go to Vertex Monitoring, so monitoring never interferes with playback. The cloud receives; it never opens a connection to a device in the field.

    • Mutual TLS at the ingestion gateway
    • Stale or out-of-order reports are discarded
    Vertex MonitoringFleet
    Online64/66
    Attention2
    Plays today14,820
  5. Video processed on site

    Soca Insight On-Premise runs person and vehicle detection on a Mac at the location. The video never leaves that machine; only the counts sync to Soca Insight Cloud. For heavier work, Soca Insight Cloud spreads detection jobs over a network of partner GPU machines.

    Soca Insight Cloud worker terminals with their status

Locked to the device, open to the right people.

Per-device licences

Each machine is activated with its own key pair and an Ed25519-signed licence, with a grace period when it is offline.

One-time password sign-in

No passwords to leak: a code arrives on WhatsApp or SMS, with rate limits and lockout against guessing.

Roles that mean the same

Who may approve, price or only operate is decided by role and checked on every request.

Tenant data kept apart

On a shared screen each advertiser sees its own campaigns and money; other tenants’ details are masked at the database.

Hardware the customer supplies.

Kliktron supplies the software and the licences. The equipment below stays yours.

At a videotron

Player computer
The machine that drives the videotron, running Vertex Player
Proof camera
RTSP-capable CCTV that sees the screen

Indoor screens

Player computer
Windows 10 or 11 (64-bit) or macOS, one video output per screen
Media
MP4 · H.264 · AAC

Audience counting

Computer
Mac with Apple Silicon, macOS 13 or later
Camera
USB (UVC) or RTSP camera, 720p minimum, 1080p recommended

Vehicles

Kliktrack Desktop
USB GPS receiver recognised by macOS or Windows
Kliktrack Mobile
Android or iOS phone with background location allowed

Activation

Photospace booth
Laptop, camera and printer, with Chrome or Edge
Guests
Their own phones, nothing to install

Questions technical teams ask.

No. Players air from their local database. The internet is needed for activation, sync, remote control and the dashboards.

On the machine at the site. Audience counting sends numbers, not video. A proof-of-play clip is sealed to the play log on the player.

Devices push telemetry to the cloud; the cloud never connects to them. The dashboard is passive: it shows status and does not send alert messages.

Klikplayer Mini Site runs on Windows 10 or 11 and macOS; Soca Insight On-Premise on macOS with Apple Silicon; Kliktrack Desktop on macOS and Windows; Kliktrack Mobile on Android and iOS. The cloud apps run in a current browser.

Read the AOS architecture page, then ask for a session with the team through investor relations on the contact page.

Let’s make it Broadplay,
Anyone,
Anywhere,
Anytime.

Walk through the stack with our technical team, or talk to us about partnership and investment.