Documentation

Docs

An overview for customers, operators, and app reviewers. This page intentionally avoids internal system specifications and implementation detail.

What Pixelogy Does

Pixelogy helps teams operate display networks made of render nodes. Operators use Pixelogy Control to prepare projects, manage nodes, launch display content, monitor health, and apply updates.

Main Parts

A typical deployment includes a customer portal, an on-prem control plane, one or more render nodes, project media, and optional integrations such as Zoom. The portal helps with fleet services and account workflows. The on-prem control plane is where operators run the show.

Operator Workflow

Operators create or import projects, choose surfaces such as text, images, video, NDI, web, or Zoom sources, assign projects to nodes, preview changes, and launch approved content to physical displays.

Node Management

Render nodes appear in Pixelogy Control with status, version, network, display, and update information. Operators can see whether a node is online, launch or stop assigned content, and apply approved updates.

Zoom Meetings

The Zoom integration lets an authorized Zoom user connect their account to Pixelogy Control. A render node can then join approved meetings as a visible participant and display meeting video on Pixelogy outputs. Full user guide at /docs/zoom-meetings; reviewer test plan at /docs/zoom-meetings/test-plan.

Privacy And Permissions

Pixelogy uses connected account and meeting information only to operate requested workflows. Customers remain responsible for meeting permissions, participant notices, content rights, and local deployment access.

Getting Help

If something is not working, collect the site name, node name, what you were trying to do, what happened, and when it happened. Then contact Pixelogy support.