Product Roadmap, one engine getting sharper.
Every product already runs on the same core: identity and balance, pricing, licences and the play record. The next steps make that core tighter, so a play, its proof and its audience become one record you can hand to a client.
Live today, the base we build on.
Ten software products in four groups, plus the two services that run on them. These are available now.
Order
Pick a point and dates in the Klik App, pay from a Plays balance, upload one clip. No minimum of hundreds of spots.
Kliktron® AppAir
The schedule runs from the player beside the screen. When the line drops, the spot keeps airing.
Vertex PlayerProve
Every airing is logged with a timestamp and a CCTV clip. The fleet grid puts failing screens on top.
Vertex MonitoringMeasure
Cameras count the people and vehicles that pass. Video stays on site, only the numbers leave.
Soca InsightTrack
Live position, trips, stops and route replay for every Mōbitron and fleet vehicle.
Kliktrack MobileActivate
A photo booth with nothing to install: guests scan a QR code and the result reaches their WhatsApp.
Photospace AutomationWhat ships next, product by product.
Now is what the team is working on. Next follows it. Later is the direction we are heading in. We do not publish dates.
- Now In progress
One definition of a play, everywhere Kliktron AOS
A Play (one 15-second airing), a Qüota and a Tier are defined once, in the core, and every product reads the same definition. The app, the CMS, the player and the audience counter can no longer disagree on price, schedule or report.
AOS Architecture - Now In progress
Proof matched with the audience of each play Vertex Player · Soca Insight
The timestamp of every proof of play is matched with the people and vehicle counts from the same moment. Each airing gets its own Opportunity To See figure, instead of a daily average.
- Advertisers see play history with OTS per play in the Klik App
- Media owners see sales, point occupancy and audience performance
- Now In progress
Klik App CMS: one calendar, schedules sent to the player Kliktron® App
A booking locks the slot on the same availability calendar the player reads, so there is no second calendar. Approved orders travel to the player as schedules, with no manual re-entry on site.
Kliktron® App - Next Planned
One identity across every product Kliktron AOS
One account, signed in with a phone number and a one-time password, opens the app, the CMS and the audience reports that your role allows. Fewer log-ins, and no user data drifting out of sync between products.
- Next Planned
The same roles mean the same rights Klik App CMS · Soca Insight
Kliktron admin, media owner, advertiser, operator and viewer carry the same meaning in every application. This is already in place in Klikplayer Mini Cloud and Vertex Player, and is being brought to Soca Insight and the Klik App CMS.
- Next Planned
Vertex Cloud coordinates the sites Vertex Cloud
Many Vertex Player sites, seen and coordinated from one place, while each machine keeps its own schedule, balance and play log so the screen never waits for the cloud.
Vertex Cloud - Later Planned
The same player and counter on a moving screen Kliktrack · Mōbitron
The player and the on-site audience counter are built to run on indoor and outdoor screens, on fixed points and on Mōbitron vehicles, with only the location settings changing. Route proof from Kliktrack joins the same campaign record as screen proof.
Kliktrack Mobile - Later Planned
Activations in the same account Photospace
Photo booth activations at events and on a Mōbibooth connect to the same branding and the same account as the screen campaign, so one brand sees its screens, routes and activations together.
Photospace Automation - Later Planned
Audience data and integrations for agencies Soca Insight Cloud
Audience counts aggregated across the network for media research, and an integration path for agency systems. Video still never leaves the site: only counts are shared.
Soca Insight Cloud
This page shows direction, not commitments. Order, scope and timing can change. What you buy today is described on each product page and in your contract.
What will not change, whatever ships next.
Five rules every new release has to keep.
- Screens keep airing when the internet drops. The cloud adds reach, it is never a condition for airing.
- Video from audience cameras is processed on site. Only the counts leave.
- The player writes the play log. Proof is made by the machine, not reconciled afterwards.
- A change to how a play, a quota or a proof record is defined stays compatible with the products already in the field.
- Adding a product never means adding a system. A new screen, camera, vehicle or booth joins the same account.
Let’s make it Broadplay,
Anyone,
Anywhere,
Anytime.
Want a direction moved up for your network? Tell us what you run and what you need first.


