®
API-first core
Every app talks to one central API for quota, schedule, tier and transactions. No product keeps its own diverging copy of that data.
The architecture behind every play.
Kliktron AOS is built in layers on one core. Access sells, Control airs and proves, Insight measures, and Mobility and Activation extend the reach. Every product reads and writes the same records through the core.
3core layers: Access, Control, Insight
2extensions: Mobility and Activation
1core shared by every product
Three layers, two extensions, one core.
Each layer answers one question. Access: who orders and pays? Control: what airs, and did it air? Insight: who saw it? The extensions take the same system onto the road and into live activation.
AccessWhere advertisers order, pay and follow their campaigns, and where media owners set products, prices and vouchers.
- Kliktron® App
- Klik App CMS
- Kliktron® Media Buying
ControlWhere screens run the schedule, keep airing offline and record proof of play.
InsightWhere cameras count people and vehicles, and the counts become reports.
MobilityExtension: tracks media vehicles, so a moving screen has a route, stops and stop times on record.
ActivationExtension: adds live touchpoints, such as photo booths and LED games, to the same brand campaign.
Kliktron AOS coreOne engine behind every product. Adding a product never means adding a system.
- Identity & balance
- Pricing engine
- Licensing
- Order queue
- Play records
One source of truth for Play, Quota and Tier.
A play, a quota and a tier are defined once, at platform level. The app that sells them, the player that airs them and the report that proves them all read the same definition.
That is why a price, a schedule and a report can never disagree, and why a new product can join without a new set of rules.
- Play: one 15-second airing
- Quota: the plays bought for a period
- Tier: the class of a point, which sets its rate, minimum quota and slot priority
Six principles that keep it consistent.
The rules every product follows, so the platform behaves as one system as it grows.
Roles mean the same everywhere
An admin, an operator, an advertiser or a read-only viewer has the same meaning, and the same limits, in every product.
Offline-first edge
Machines at the site hold the schedule, rates and balance. The cloud adds reach; it is never a condition for airing.
Privacy by design
Audience video is processed on site. Only the counts leave the machine, never the footage.
Hardware- and location-agnostic
The same player and counting software run indoors and outdoors, at fixed points and on Mōbitron vehicles. Only the site configuration changes.
A single identity
One account, signed in with a phone number and a one-time password, opens every product the user’s role allows.
From order to report, seven hand-offs.
Every transaction follows one path, and each system is responsible for exactly one step of it.
- 01
Order Access
The advertiser picks a point, tier and quota. The slot is locked on the same availability calendar the player reads. There is no second calendar.
- 02
Schedule Core
Approved orders travel as commands to the machine at that point. Nobody re-enters the schedule by hand at the player.
- 03
Air Control
The player airs the spot from local storage, resolving its schedule layers in a fixed order.
- 04
Log proof Control
At the second of airing, the player writes a timestamp, seals a CCTV clip to it and syncs the record to the cloud.
- 05
Count Insight
At the same point, Soca Insight counts the people and vehicles passing and sends only the counts.
- 06
Match Core
The play’s timestamp is matched with the count for that moment, so an airing can carry its own audience figure instead of a daily average.
- 07
Report Access
The advertiser sees play history with audience. The media owner sees sales, occupancy and audience performance per point.
Integrations, in plain terms.
How the parts talk to each other, and to the people who use them.
Cloud and machines
- Protocol
- Kliktron Protocol over NATS, between the cloud and the machines at each site
- Local API
- REST on the machine
- Media
- Prefetched from the cloud, then played from local storage
Monitoring
- Telemetry
- Heartbeat, content freshness and preview, sent over HTTP to Vertex Monitoring
- Separation
- Telemetry is kept apart from commands, so monitoring never interferes with airing
- Direction
- Devices report in; the monitoring cloud never opens a connection to a device
People and payment
- Sign-in
- One-time password on WhatsApp
- Payment
- Payment gateway in the Klik App: QRIS, e-wallets and virtual account
- Balance
- Plays balance per account, deducted per play
Locked per device, open per role.
Every machine is activated with its own key pair and a per-device licence signed with Ed25519. Without a valid licence the application does not run. Sign-in uses a one-time password, with a rate limit and lockout against guessing, and roles are enforced in the engine, not only on the screen.
- Per-device licences, with a grace period when a machine is offline
- OTP sign-in with rate limit and lockout
- Each advertiser sees only its own campaigns and finances
- Alerts for licences that expire within 30 days
AOS
- Identity & balance
- Pricing engine
- Licensing
- Order queue
- Play records
Questions, answered.
No. The AOS core comes with the products. You license products per screen, camera or vehicle, and each one runs on the same core.
Schedule, rates and balance live on the machine at the site, and play records sync to the cloud. Video used for audience counting stays on site; only the counts leave.
Vertex Monitoring flags licences that expire within 30 days, so they can be renewed in time. A machine that is temporarily offline keeps working within its grace period.
Yes. The same software runs on Mōbitron vehicles, and Kliktrack adds the route, stops and stop times to the record.
The core is API-first, and integration with an existing system is scoped per project with the team.
Keep exploring, related pages.
How it WorksThe Advertising Operating System (AOS) behind every play, stage by stage.TechnologyPlayers, cameras, tracking and the AOS core, explained for technical teams, integrators and investors.
Advertising PlatformSoftware that runs, proves and measures a screen network, from one screen to a fleet across cities.
LicensingHow software licences work: units, billing, activation, transfers, trials and expiry.
Let’s make it Broadplay,
Anyone,
Anywhere,
Anytime.
Walk through the architecture with the team, for your network or as a partner.