Home/Platform/Meet Polaris

Meet Mersive Polaris: wireless screen sharing from any browser.

One platform turns every display into a shared workspace: joined from a browser, BYOM and client agnostic, managed from one cloud.

The signature diagram

Glass. Workspace. Cloud.

Three layers, one platform: the display renders, the workspace composites, the cloud connects and manages. Expand any layer for the plain-language depth.

How a share reaches the room, in three steps Step one, join: the laptop, the phone, the Polaris pod and a remote participant in a browser each send a short signaling ping up to Polaris Cloud and get an answer back: authenticate, resolve the screen key, exchange SDP and ICE. Step two, connect: direct links form between the endpoints and the pod, and the cloud drops out of the media path. Step three, compose: the shares land side by side on the display as one workspace, and the remote participant sees the same workspace live in the browser. THE ROOM direct {/* THE LABEL LIVES INSIDE THE ICON. On one line at 14 it measured 131 against a cloud 96 wide and ran out both sides, and it was centered on 450 where the shape's own center is 465, so it was off to the left as well. Two lines at 12 measure 59 and 42, which sit in the belly of the cloud with 18 to spare. The green orb that used to ride above it is gone on Damian's call, 29 Aug 2026. */} POLARIS CLOUD authenticate · resolve the screen key · SDP + ICE introduces the endpoints, then leaves the media path Polaris pod the workspace: every share, side by side laptop · sharing phone · sharing REMOTE / APP.MERSIVE.COM remote · sharing The Mersive Workspace the same workspace, live in the browser How a share reaches the room, in three steps Step one: the laptop, the phone and a remote participant in a browser each ping Polaris Cloud and get an answer back. Step two: direct links form down to the Polaris pod and the cloud leaves the media path. Step three: the shares land side by side on the display as one workspace. THE ROOM POLARIS CLOUD resolving the screen key out of the media path ALSO IN THE ROOM ANOTHER NETWORK laptop phone remote Polaris pod every share, side by side
  1. JoinDevices dial out to Polaris Cloud, which authenticate, resolve the screen key, trade SDP and ICE.
  2. ConnectThe cloud introduces them and steps aside. Media runs on direct links to the pod: in the room it never leaves the building, and from outside it never touches a VPN.
  3. ComposeShares land side by side on the display as one workspace, and the same workspace renders live in the browser for everyone who isn’t in the room.
Layer 1 · in the roomThe glass

Any display becomes a Polaris endpoint: meeting room, classroom, lobby wall.

＋ more

The display stops being a destination you cable into and becomes a rendering target: the Polaris device behind it draws whatever the workspace says to draw.

  • Any display qualifies. The panel you already own, driven by a Polaris device behind it: no smart-panel firmware to depend on, no vendor-matched displays.
  • In Polaris Pro rooms, the AV plugs in here. Camera and mic cable into the Pro device, so meetings can borrow them wirelessly.
  • Idle displays still work. When no one is sharing, the same display runs signage, managed from the same portal. Signage →
Layer 2 · the unit of workThe workspace

Every share, side by side, composited live, fed from any device, in-room or remote.

＋ more

The workspace is what makes the display worth looking at: not one mirrored screen but a composited canvas of simultaneous sources, mirrored live to every participant signed in at app.mersive.com.

  • Multi-source, live. A deck from a laptop, a guest's browser tab, photos from a phone, a dashboard from another building: side by side, rearranged from the Dock.
  • Any device feeds it. Native share or web-join from the browser; sources from other networks arrive via cross-network sharing.
  • It belongs to the room. The workspace is rendered by the room's Polaris hardware, not by whichever laptop happens to be open, so shutting a lid does not end the meeting; it just removes the content from that device while everything else stays exactly where it was.
Layer 3 · above the fleetThe cloud

Routes every workspace, manages every room: one admin plane for the whole fleet.

＋ more

Polaris Cloud does two jobs: it introduces sessions (the signaling that lets endpoints find each other across networks) and it runs the fleet, which is conference room management for every room and screen you own.

  • Session brokering. Devices and displays find each other through the cloud; same-network traffic stays on your LAN; cross-network traffic flows over a WebRTC direct, encrypted connection the cloud negotiated.
  • Conference room management. Bulk config, templates by room type, staged firmware, analytics and health alerts, for meeting rooms and signage alike, from one login. Polaris Cloud →
  • What it doesn't do. Store your workspace content. The candid data-path story lives in the Trust Center.
100% web-based

How to share your screen from a browser

Sharing from the browser does not require an app, downloading, installs or admin rights; you share to the room display from a browser tab. A guest who walked in can share, and there is no client to package, approve, patch, or manage.

Four steps, zero software:

1Open a browser

Web-join works on any device with a current browser, Chromebooks and locked-down loaners included. Phones share through the Mersive app or native protocol.

→
2Go to app.mersive.com, type the screen key

The 6-character key is on the display. Every key is globally unique and expires ten minutes after it’s issued.

→
3You’re on the display

Your share lands in the workspace next to everyone else’s, composited live, not queued behind a presenter.

→
4The Dock rides in the tab

Layout, participants, handoff, end meeting: the room’s controls live in the same browser tab you joined from.

✓ No client✓ No admin rights✓ Works on Chromebooks
Every way in

Web share is the front door. It isn't the only door.

The workspace takes whatever the room brings. Web-join is the predominant path, but native casting and the Mersive mobile apps land on the same display, and they all composite together.

Web-joinany network

The browser share: no install, cross-network, guest-proof. The predominant path.

Polaris mobile appany network

Share and control from the phone in your pocket. iOS & Android.

Wired HDMIPro only

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.

AirPlayLAN only

Native Apple sharing: no Mersive software on the device.

MiracastLAN only

Native Windows sharing, straight from the OS.

Google CastLAN only

Chromecast from Chrome and Android: the Chromebook classroom's native path.

All of these: at the same time, on the same workspace. An AirPlay share, a Miracast share, a browser guest, and a phone can sit side by side on one display. 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. Web-join and the Mersive apps work from any network; native casting (AirPlay, Miracast, Google Cast) is LAN-only. Native casting reaches the room over the local link only (the room's network, a peer-to-peer Wi-Fi Direct session, or the receiver's own access point), and discovery is link-local, so it breaks the moment a VLAN boundary appears. Once its share lands in the workspace, remote participants see it like everything else. Web-join and the Mersive apps join from any network. We say so plainly on the cross-network page.
Meeting parity

Everyone sees what the display shows.

Meeting parity (what remote participants see): every source shared into the room is delivered to everyone who joined at app.mersive.com, and the layout travels with it. Order, focus, full-screen and position stay in step, because the room and every browser run the same layout code.

So a remote seat reproduces what the display shows at its own screen’s resolution rather than watching a video of the room’s screen. No craning at the display, no “can you re-share that,” no second-class seats.

Wired HDMI: two modes

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.

The room display
The room display in Main Conference Room showing five shared posts at once - a stair detail, a photo of a building, a wireframe massing study, a mechanical drawing and a floor plan - each tagged with the name of the person sharing it, above a bar reading Visit app.mersive.com and use screen key 34C-7PJ
⇄live mirror
app.mersive.com: every participant
The same five posts in the same layout and the same colors at app.mersive.com in a browser, with the share, layout and room audio controls above them and the Content Dock alongside
Why the silicon matters

Where a panel stops and the room silicon starts.

A workspace is a compositing problem: a roomful of people sharing at once means many simultaneous decode sessions rendered into one layout, and bridging your meeting to the room's AV adds real-time encode on top.

That takes purpose-built silicon, not a display's spare cycles.

The memory ceiling

Around 5 simultaneous shares on Essentials and 10 on Pro. It is a memory ceiling on the chassis, not a license: nothing in the software counts sources or refuses one, so the limit is what the silicon can hold, and the two tiers run the same code.

Mirroring versus recompositing Two lanes. Above: mirroring, as everyone else does it. One laptop sends its pixels one to one along a dashed line to a display, which shows the same picture at the same shape. One source, one screen, and nothing leaves the room. Below: recompositing, as Polaris does it. Four sources - a deck, a browser tab, a phone photo and a live dashboard - each reach their own decode chip, and the four feeds converge on the workspace compositor, which lays out a fresh workspace automatically as sources join and leave. The workspace leaves by two paths: rendered at the display's native resolution onto the room's glass as a four-up layout, and to every remote browser, where each seat runs the same layout code to rebuild the same workspace. MIRRORING VS RECOMPOSITING MIRRORING · EVERYONE ELSE one laptop pixels copied · 1 : 1 · nothing decides anything ✕ the display is a copy: one source, one screen, nothing leaves the room. RECOMPOSITING · POLARIS DECKBROWSER TABPHONE PHOTOLIVE DASHBOARD H.265H.264VP8H.264 4 simultaneous decodes · the ceiling is memory, not a license: 5 on Essentials, 10 on Pro as of Sep 2026 THE WORKSPACE a fresh workspace, laid out automatically as sources join and leave rendered at the display’s native resolution the same workspace in every remote browser every seat runs the same layout code ✓ the room draws a new picture: nobody’s laptop is load-bearing

What this buys you in the room: a panel’s composite stays on its own glass; Polaris encodes the whole meeting out to every participant, and Polaris Pro keeps enough encode headroom to hand the room’s camera and mic to your Teams, Zoom, Webex, or Meet call.

Go deeper

Evaluating Polaris? Start with these four reads.

Cross-network sharing

Content crosses subnets, VLANs, and the internet: no VPN, no UC call. Of the twelve competitors we checked in August 2026, exactly one documents a comparable off-LAN path, and it wants two ephemeral port ranges, XMPP and STUN/TURN/ICE, with signaling hosted in Azure West Europe. The other eleven document LAN-local media only.

The flagship deep-dive →

Security architecture

The trust chain, network posture, and update policy: the ten-minute read your security team actually wants. Nothing gated.

The Trust Center →

Where meetings live

Two questions classify every room ever built. This grid is the map, and Polaris is the only platform we know of holding all three agnostic models.

Where meetings live →

Hybrid meetings

BYOM today, hosted-BY-the-room next: how the meeting leaves the laptop for good, with native clients, chosen per meeting.

The hybrid family →

Also: the 10-year platform and its invariants · the tier table · Polaris Cloud · the 10-year math

See the platform live.

Hardware trials ship for every product, direct from Mersive. When the rooms prove it, we introduce your regional partner for the rollout.

Start a trial Watch on YouTube ↗