Mersive Polaris Cloud

Polaris Cloud as a ware →Where AI hath its place →

Govern the room, not the box alone.

Analytics

Usage for each room, for each day: meetings, connections in all, hours in use, posts shared, and the meeting's average length, over the last 7, 30, 60 or 90 days, or all of time.

With breakdowns by mode of connection, sharing protocol, the client's operating system and conferencing platform, as well as counts of downtime, unreachability and reboots for each room, and CSV export of any view.

An open cloud API

A REST API out of Polaris Cloud, enabled for each organization.

Reboot a device or change its HDMI input; put a display to sleep and wake it, one at a time or every device in the organization at once; send HDMI-CEC or serial power commands; set the display to mirror or extend; read the status of device, display, network and the whole across the fleet; read the motion sensor's state and history; set a room's digital-signage URL, or one URL across the whole organization; and read, create, update and delete the room's calendar events. Draw the fleet into the tooling of watchfulness and automation thou already runnest.

Peruse the Polaris API reference →

Activation & licensing

Claim devices, assign subscriptions, and see exactly what is licensed where: renewals and entitlements in one view, visible to partners where thou wouldst have them be.

Governance of rooms and devices

Govern every meeting room from one console, not device by device.

Configuration templates: define a room's profile but once (its appearance and idle-screen content, signage, share protocols, network and proxy, calendar integration, the display's power and reboot schedule, and the window for firmware updates), then assign it to as many devices as thou choosest. Each device beareth one template, and editing the template applieth it anew to every device assigned thereto. Devices may also be edited in bulk without a template, and brought aboard in bulk from a CSV of as many as 1,000 devices. Firmware updates are scheduled for each device or across the fleet through a template: turn auto-update on, then choose 'as soon as may be' or a weekly window (a day and an hour), and, if thou wilt, hold the update back whilst folk are still connected. Thou mayst also choose any set of devices and update them forthwith.

Alerts & health

A room that cannot be reached, a pod that rebooted in the night, a firmware window about to open: brought to light by email ere the 9am meeting findeth it.

Six triggers: a pod unreachable for a number of minutes thou settest (1 to 60, by default 5), a pod rebooted, a pod unassigned from its template, and a firmware update available, about to begin, and completed. Alerts go to the administrator signed in, and to as many as five email addresses besides, and each recipient chooseth which of the six they would have.

The MCP server SHIPPETH Q4 2026

An MCP server upon the selfsame cloud API, that AI agents and assistants may work the fleet as thine own tooling doth already.

Polaris & AI →

The USB bus, for each device SHIPPETH Q4 2026

Sight of each device's USB bus from the cloud: the camera, the microphone and speaker, and a touch display, each shown as the room reporteth it.