---
title: "Polaris Pro: Wireless Presentation System | Mersive"
canonical: https://www.mersive.com/pro
description: "Polaris Pro: wireless BYOM conferencing, HDMI input and dual 4K60 output, 802.1X enterprise networking, PoE+ single-cable install, subscription or perpetual license."
language: en-US
publisher: Mersive Technologies
---

# Mersive Polaris Pro

One platform. One workspace. Total collaboration

Ten live sources composited side by side, true wireless BYOM on the room's own camera and mic, and sharing that crosses networks — no VPN, no cable on the table.

[Specs](https://www.mersive.com/pro/spec)

![Mersive Polaris Pro pod](https://www.mersive.com/products/pod-pro-zoom-alpha/w1440/pod-pro-zoom-alpha-01.webp)

Inside Polaris Pro

One pod. The whole room.

- **Up to 10 simultaneous shares** Composited live, side by side, laid out as sources join and leave
- **Dual 4K60 output** 2× HDMI 2.0, 4K (3840 × 2160) at 60 Hz on both
- **HDMI input** 1× HDMI 2.0 in, with HDCP 2.0 content protection
- **The room's camera and mic** 2× USB 3.0 Type-C, host mode: what carries true wireless BYOM
- **One cable to the room** 1× 10/100/1000 RJ-45, PoE+ (802.3at Type 2)
- **16 GB LPDDR4 · 32 GB flash** MediaTek MT8395 (Genio 1200): ARM SoC, Mali GPU, on-die APU

[The full spec sheet →](https://www.mersive.com/pro/spec)

## Built for enterprise networks and the rooms where decisions actually get made.

What Pro does

## Four capabilities, one room.

### The full multi-share workspace

Live sources composited side by side, compared, annotated, rearranged live, up to the published per-tier ceiling: 5 on Essentials, 10 on Pro. The room's silicon does the work; nobody's laptop is load-bearing.

[Why the workspace wins](https://www.mersive.com/solutions/collab)

### True wireless BYOM

Your Teams/Zoom/Webex/Meet call, the room's camera and mic, no cable on the table, and multi-user, so the second presenter never waits for a dongle.

[The hybrid story](https://www.mersive.com/hybrid)

### Cross-network sharing

On every Polaris tier, Pro included: guests on LTE, staff on corp Wi-Fi, the display on an AV VLAN, one workspace, no VPN, no UC call. Eleven of the twelve competitors we checked in August 2026 document LAN-local media only, on their own published specifications; one of them says it plainly: users on a cellular network or guest Wi-Fi cannot use it. The vendor list and sources are on the [architecture page](https://www.mersive.com/platform/cross-network) and the compare matrix.

[See the architecture](https://www.mersive.com/platform/cross-network)

### Web-join: nothing to install

Share from the browser on the device you walked in with, Chromebooks included. No client, no admin rights, no dongle drawer.

[How web-join works](https://www.mersive.com/platform/how)

Security

## The device is tested too, by someone else.

Certifications scoped to a cloud say nothing about the box on the wall, so the box gets its own proof. Two outside firms have had it: one over the network, one with the lid off.

Independent scan · July 2026

### No network attack surface worth the name

An outside firm scanned a managed Pod. The ports that answer are the casting and appliance functions, and no persistent media listener was enumerable at all, the real-time media path uses ephemeral per-session UDP ports that respond only after ICE consent. There is no standing media service in the room to probe.

Independent physical attack · May 2025

### Opened, probed, and it held

A firm took a Gen 4 Pod in hand, opened it and attacked the hardware: UART and JTAG on the debug headers, an attempt to lift the firmware off the flash, a lab man-in-the-middle. **No critical, high, medium or low-severity vulnerabilities were identified.** Root login over the debug interface is refused outright, with no password prompt even offered; the firmware could not be extracted; no personally identifiable information was found stored on the device; and a presented invalid certificate was refused: the Pod failed the handshake and stopped talking to Mersive rather than trusting the interceptor.

On the device

### Secure boot, sealed keys, an allowlist and 802.1X

Secure boot is mandatory on production firmware. The device’s own identity keys are sealed into an NXP SE050 secure element. USB access is by allowlist. 802.1X with EAP-TLS makes the room a first-class citizen of your NAC rather than an exception in it.

The company, and the cloud

### ISO/IEC 27001:2022 · SOC 2 Type 2

Mersive is ISO/IEC 27001:2022 certified, with no nonconformities raised at the June 2026 surveillance audit, and the Polaris cloud this Pro unit reports to is SOC 2 Type 2 attested.

Their caveat, which we keep: that does not make compromise impossible, but it would take an adversary of significant skill and effort. The full architecture, every scope statement and the audit findings: [the Trust Center](https://www.mersive.com/security).

Open specs: nothing gated

## The specification sheet, inline.

Full transparency: the full network and security posture on the page, with no form between you and the facts.

****Sharing** 4 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| Simultaneous shares in the workspace | Polaris Pro can currently support up to 10 live sources composited side by side |
| Web-join from the browser: no app, no download | ✓ share from the device you walked in with |
| Native AirPlay · Miracast · Google Cast (LAN) | ✓ all three, built in: cast from Apple, Windows and Chromebook devices on the room network with nothing installed |
| Mobile sharing · phones and tablets | ✓ the Polaris app for iOS and Android: share your screen, photos or a live whiteboard, and control the workspace from your seat |

****Network** 3 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| 802.1X network authentication | ✓ EAP-TLS, PEAP, TTLS or EAP-PWD, on wired Ethernet and on Wi-Fi (WPA2-Enterprise). Supply a CA certificate, a client certificate and a private key; the supplied private key is held encrypted at rest under a key that is itself sealed in the NXP SE050 secure element, rather than in plaintext configuration |
| Dual-network posture: corp + guest, isolated | Wired GbE and the wireless radio run simultaneously, and the pod does not forward between them: its firewall drops all forwarded traffic and the firmware never enables IP forwarding. Corporate on the wire, guests on Wi-Fi — separated because the device is not a router, not because of a policy someone could unmake |
| Cross-network relay: subnets / VLANs / internet | ✓ cloud-negotiated direct connections; signaling is outbound-only TLS on TCP 443; no inbound firewall rules |

Plain language: 802.1x means the network itself demands the device prove who it is before granting a port; EAP-TLS proves it with a certificate instead of a password. Dual-network posture means the device sits on two networks at once, kept isolated, so guests share without ever touching the corporate LAN.

****Security** 8 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| Encryption in transit | Signaling and fleet management run outbound over HTTPS to Polaris Cloud. The device exposes no TLS listener of its own, so a port scan of the pod finds nothing to negotiate against — the encryption that matters is on the outbound leg, not on an open port in your room |
| Secure boot · secure element | ✓ secure boot is mandatory on production firmware and is rooted in Trusted Firmware-A (TF-A); NXP SE050 secure element on board holds the device’s own identity and update-verification keys in hardware |
| TAA-compliant supply chain | ✓ built with Advantech in Taiwan, a TAA-designated country, with the bare printed circuit board the only China-sourced item in the build |
| Linux-hardened OS | ✓ purpose-built, minimized Linux at the display: no Windows attack surface, no general-purpose desktop |
| Key custody: where private keys live | ✓ device private keys are generated and used *inside* the NXP SE050 secure element and never cross its boundary. The channel between the application and the secure element is itself authenticated and encrypted (GlobalPlatform SCP-03), and the keys for that channel are held in ARM TrustZone secure firmware where neither the operating system nor any application can read them. |
| Signed updates, no downgrade — and automatic rollback on a failed load | ✓ two different things, and both matter. Update packages are checked for authenticity and integrity before they are applied, and the device will not accept a **downgrade** to an earlier version, so a known-vulnerable firmware cannot be pushed back onto a Pod. Separately, the pod keeps **two firmware partitions**: a new image installs beside the running one rather than over it, and a pod that fails to come up on the new version comes back up on the last known-good one. Deliberate downgrade is refused; a bad load recovers itself. |
| Content that does not persist | ✓ shared content is composited on the fly rather than written to the device, and ephemeral session data — content, session keys and generated random values — is overwritten at the end of every session, including sessions that are abandoned rather than ended cleanly. |
| Physical: Kensington Nano Security Slot | ✓ on the chassis |

****I/O** 7 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| HDMI output: dual display | 2× HDMI 2.0, dual 4K (3840 × 2160) at 60 Hz; 1080p and 720p up to 60 Hz. CEC for display power and input control |
| HDMI input: wired ingest / room-system augmentation | 1× HDMI 2.0 in, 1280 × 720 through 4K (3840 × 2160) at up to 60 Hz, with HDCP 2.0 content protection. Polaris Pro has two wired HDMI input modes, selected by the room administrator. Workspace tile is the default: the input joins the workspace alongside wireless shares and is visible to remote participants. Direct bypass (full-screen pass-through) sends the input straight to the room display, outside the workspace. Remote participants do not receive that feed. |
| Ethernet | 1× 10/100/1000 RJ-45, PoE+ (802.3at Type 2) |
| Audio out | ✓ a dedicated analog audio-out jack on the rear panel, so room audio can go straight to a soundbar or a DSP without passing through the display |
| Video codecs | H.264 encode and decode · H.265 encode and decode · VP8 decode · VP9 decode · MPEG-4 decode · AV1 decode · JPEG/MJPEG decode. In service: H.264 carries AirPlay, Miracast and web-join over WebRTC; VP8 carries Google Cast; VP9 decodes digital signage playback |
| Wi-Fi radio | MediaTek MT7921: Wi-Fi 6 (802.11ax), 802.11 a/b/g/n/ac/ax compliant, 2.4 + 5 GHz, 2×2 MIMO; Bluetooth 5.2 (MediaTek MT7921) |
| USB: peripherals (camera, mic, speaker, touch) | 2× USB 3.0+ Type-C (female), host mode · output 5 V at 0.9 A maximum · no USB Power Delivery — this is what carries a room camera and mic for wireless BYOM. lists the port count only, without a generation or connector type, so the sheet is less specific than the requirement rather than in conflict with it. |

****Compute: the silicon behind the workspace** 4 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| Chipset / SoC | MediaTek MT8395AV/ZA (Genio 1200): 8-core ARM, 4× Cortex-A78 and 4× Cortex-A55 at up to 2.2 GHz, with Mali GPU and on-die APU (MediaTek's name for its NPU), OpenGL ES 3.0 / Vulkan. |
| NPU: on-device AI silicon | NPU 4.8 TOPS (INT8) in the MediaTek documentation, 9.6 TOPS at minimum precision (INT4), the convention MediaTek uses for its current Genio series. |
| RAM · storage | 16 GB LPDDR4 · 32 GB eMMC: 19 GB available for storage, the remainder holding the system image and the second partition that carries an OTA update and allows firmware rollback |
| Video pipeline: simultaneous decode / real-time encode | Decode 2× 4K60 or 4× 1080p60 concurrently; the compositor imposes no cap at the layout layer; the published Pro ceiling is 10 simultaneous shares, set by decode throughput |

****Power & physical** 4 rows *▾***

| Specification | Polaris Pro |
| --- | --- |
| Power | PoE+ (802.3at Type 2) for single-cable install, or 12 VDC, 2 A, 24 W max from the barrel jack. **The power supply is sold separately** on Pro |
| Dimensions · weight | 86 × 184 × 30 mm. Pro and Essentials are **different chassis**: Essentials is 58 × 140 × 30 mm. Both released data sheets print 150 × 67 × 30 mm and 204 g for both products, which cannot be true of two different enclosures; the sheets are being reissued |
| Operating environment | Indoor use only · 0°C (32°F) to 35°C (95°F) · 30% to 70% RH ambient |
| Storage environment | -20°C (-4°F) to 65°C (149°F) · 10% to 90% RH |
| Regulatory | FCC (USA) · UL (USA/Canada) · CB Scheme / IECEE (international) · UKCA (UK) · CE (EU) · RoHS (EU) · SCIP (EU) |

Radical transparency is the policy: part numbers, RAM, and the video pipeline are published here, not discovered in a teardown.

Documentation: open, one click

[**Datasheet (PDF)** Full specifications, ordering info, environmentals.](https://www.mersive.com/resources/docs) [**Deployment guide** Network requirements, ports, 802.1x setup, SSO.](https://www.mersive.com/resources/docs) [**Firmware & release notes** Every release, publicly logged: the update-policy receipt.](https://www.mersive.com/resources/firmware)

Common questions

## Polaris Pro, answered plainly.

**How many people can share at the same time on Polaris Pro?**

Around 10 live sources, composited side by side and laid out automatically as sources join and leave. The ceiling is memory on the chassis, not a license: nothing in the software counts sources or refuses one.

**Does Polaris Pro support wireless BYOM?**

Yes. The room's camera and microphone attach to the pod over USB, and the pod bridges them into a Teams, Zoom, Webex or Meet call brought in from a laptop. Link is a software bridge between the laptop in BYOM and the Pro, and the Pro is what controls the room's cameras and peripherals. That is why Link needs a Pro.

[How hybrid meetings work on Polaris](https://www.mersive.com/hybrid).

**What is the difference between Polaris Pro and Polaris Essentials?**

Essentials runs the same Polaris software as Pro: the same workspace, the same cloud, the same security posture. The differences are the chassis, not the platform.

Essentials: one HDMI output, no HDMI input, no USB, no audio out. Pro: dual HDMI output, HDMI input, 2x USB 3.0 Type-C host, analog audio out.

[Compare the Polaris family](https://www.mersive.com/products/family).

**Can a guest share from another network without a VPN?**

Yes. Cross-network sharing is included on every Polaris tier. Cloud-negotiated direct connections, with outbound-only TLS signaling on TCP 443: no VPN, and no inbound firewall rule.

[See the architecture](https://www.mersive.com/platform/cross-network).

**Can Polaris Pro take a wired HDMI source?**

Yes. Polaris Pro has an HDMI input. An HDMI source joins the workspace as a tile by default. Direct bypass takes the glass full screen and keeps that feed in the room.

**Pro continues Mersive Solstice Gen 3.** Same lineage: your rooms, workflows, and muscle memory carry forward, and a mixed Gen 3 + Polaris fleet is fully supported while you move. [The transition path →](https://www.mersive.com/products/transition)