Partners · CMS & player partners
Keep your stack. Take the demand.
Our platform is open infrastructure — our own CMS is just the first client of the same public APIs. If you operate screens today, there are two ways to plug your inventory into our demand.
The two paths
Two integrations. Pick the one that matches who owns the loop.
Your player, our platform
Keep your hardware and player software; our platform decides what plays. Four endpoints: register, heartbeat, config, proof of play. Live today in a national high-street pilot.
Your CMS, our demand
Keep your entire stack and your loop. Register your inventory, request an ad per slot, confirm the play — three calls, and unsold slots start earning. A slow response never blacks a screen: your fallback always plays.
Path 01
Your player, our platform
You keep
Your hardware and your player software.
- register
- heartbeat
- config
- proof of play
Our platform decides what plays and returns the loop your player renders.
Path 02
Your CMS, our demand
You keep
Your entire stack, including the loop.
- register unit
- request ad → decision
- confirm play
We answer per slot. If we are slow or silent, your fallback plays and the screen never blanks.
The decision rule
One question decides it.
Who owns the loop on that screen? If we do, take path 1. If you do, take path 2. We'll never sell you a blend of both.
What the decision uses
The engine targets on signals your screens already generate.
Contextual conditions, audience curves and the store's own till feed are all bookable, and every signal is documented with the screens reporting it.
Integrations
Send us your screen count and we'll size the fill.
Integration starts with a sandbox key and a test unit; nothing goes live until you accept the response.