Integrate the decision, not the stack.
turms is designed to be built on. Discuss contributing signals, consuming decisions or taking measurement on their own, without replacing anything that already works.
Four layers, four integration points.
Each layer of the platform is addressable independently. A partner can contribute signals, consume decisions, deliver media or take measurement, and nothing forces adoption of the rest.
Signal interface
Contribute vehicle, device or environment signals into the context layer.
Decision output
The agreed integration returns the selected environment, timing and creative, or an instruction to hold.
Delivery integration
Stitching into existing streams and ad breaks rather than adding a new playback layer.
Measurement feed
Outcome data in the agreed reporting format, reconcilable against existing reporting.
Interoperability is the design constraint.
turms holds no proprietary lock-in over a partner's data, inventory or customer relationship.
Technical review
Scope, signal availability and latency requirements assessed against your architecture.
Proof of concept
Test the agreed integration in a controlled environment before any commercial commitment.
Certification
Integration validated on decision quality, latency and compliance handling.
Production
Live traffic, with monitoring and a documented support path.
Know what should happen next.
Movement Media, connected vehicle monetisation, or integrating the turms decision layer.
