Platform Components

The key components of the platform

Monterosa / Interaction Cloud™, consists of a set of core components:



A dedicated space for an Organisation which hosts all its Brands under one roof, provides access to Team management, Help resources and Experiences

The event-driven control centre that drives live content, interactive elements, app extensions configuration.

Apps are web or native applications built using the platform APIs and SDKs.

Experiences are Apps that are created as templates. "Fast Track" Experiences are those that can be set up and deployed quickly. With regular Experiences being those which typically take a little more implementation.

Our applications are built on the concepts of live events and two-way interactive elements that are triggered to appear at a certain time and process both the appearance of the content, the way it behaves, and the data which is sent back from the audience.


A set of APIs, interfaces and libraries which allow developers to create front-end applications built on the power of the infrastructure, backend scripts that automate creation and management of events, create and trigger content, and extract data for TV graphics or analytics.

Backend processing and special functionality powering voting, gamification, push notifications, data capture and more.

The cloud mesh network of distributed processing powering the massive scalability of the system, allowing each app to connect via websocket.

How data travels in the platform

In the diagram below, the Studio is the control interface for content creators and product teams. All devices are connected persistently to via socket connections, ready for content to be triggered. For example if a live event starts at 8pm, all devices will be triggered at almost exactly the same time to say "We're Live!".

The infrastructure is a distributed series of edge nodes running on AWS which handle the core socket connectivity. There are layers of control and dependency, with a standard approach to fail-overs if and when a server has a problem, the client device will simply connect to another and state is preserved.

Processing, for example counting the number of votes cast or the percentage of people who have predicted an outcome, takes place in a distributed manner, ensuring high levels of scalability.

The infrastructure uses a lightweight proprietary protocol that is available in either plain text or via secure websockets. The underlying edge servers, known as the EnMasse Mesh, are cloned instances which have awareness of each other. They are written in C++ for speed and efficiency, fine tuned and fully supported by our team.

The platform does not rely on third party data transport providers or intermediaries.