Glossary

Digital Signage Glossary

From pixel pitch and proof of play to DOOH and MCP, the signage terms buyers meet most, each defined plainly with a source to check.

This glossary defines 44 terms used in the digital signage industry. Definitions reflect current industry usage as of May 2026 and include historical context where terminology has evolved. Each entry includes references to authoritative sources for independent verification. CastHub maintains this glossary and updates it as industry terminology shifts.

Table of contents

Display and Hardware (13 terms)

Software and Architecture (3 terms)

Operational (15 terms)

Integration and Standards (6 terms)

AI and Modern Capabilities (7 terms)

Glossary terms

Digital Signage

Digital signage is the use of networked electronic displays to deliver content in commercial, public, or institutional settings, typically managed through a content management system (CMS). The industry emerged in the late 1990s with single-screen deployments and matured into networked, cloud-managed display fleets across retail, education, healthcare, corporate, and hospitality verticals.

Modern digital signage networks range from single-location deployments of a few screens to enterprise fleets of tens of thousands of displays, with content updated remotely from a centralized CMS. The global digital signage market was estimated at approximately $28 billion in 2025 according to industry analyst reports.

Reference. Wikipedia: Digital signage.

Related terms.

Media Player

A media player in digital signage is the hardware device that plays content on a connected display, receives updates from a CMS, and reports device status back to the management platform. Media players range from purpose-built commercial devices like BrightSign LS Series and Amazon Signage Stick to general-purpose hardware like Raspberry Pi, Intel NUC, and Android boxes running CMS player applications.

The media player is distinct from the display itself: a single media player drives one or more displays via HDMI or DisplayPort output. Commercial media players are engineered for 24/7 operation with features like secure boot, kiosk mode, and automatic failover that consumer streaming devices like Fire TV Stick or Chromecast lack.

Reference. BrightSign media players.

Related terms.

SoC Display (System-on-Chip)

A System-on-Chip (SoC) display is a commercial monitor with an integrated media player built into the display itself, eliminating the need for an external player device. Major SoC platforms include Samsung Tizen, LG webOS, and Philips Android.

SoC displays simplify deployment because the display ships ready to run signage content with no separate hardware to install, but they typically have less processing power than dedicated commercial media players and are tied to a specific vendor operating system. SoC displays are common in retail and corporate deployments where simplicity and reduced cable management matter more than playback flexibility.

Reference. Samsung Tizen for Digital Signage.

Related terms.

OPS Slot (Open Pluggable Specification)

An OPS slot (Open Pluggable Specification) is a standardized slot on commercial displays that accepts a slot-in PC module, providing media player functionality without external hardware or cables. The OPS standard was introduced by Intel in 2010 to reduce installation complexity for digital signage and interactive whiteboards.

Slot-in PCs in OPS form factor run Windows or Linux and connect to the display video and power circuitry through a single 80-pin connector. OPS-compatible displays are common in education, corporate conferencing, and retail kiosk deployments.

Reference. Intel OPS Specification.

Related terms.

Commercial Display vs Consumer Display

Commercial displays are monitors engineered for continuous 24/7 operation in business environments, with features that consumer televisions lack, including extended warranties, higher brightness ratings, anti-image-retention technology, and longer rated panel lifespan. Consumer televisions are typically rated for 4 to 8 hours of daily use and use cost-optimized panels that exhibit image retention or burn-in when displaying static content.

Commercial displays from manufacturers like Samsung, LG, NEC, and Philips include features like remote management protocols, scheduling, and tamper-resistant power controls. Digital signage deployments using consumer televisions typically void manufacturer warranties and experience faster panel degradation.

Reference. Samsung Digital Signage Commercial Displays.

Related terms.

Kiosk Mode

Kiosk mode is a hardware or software configuration that restricts a device to running a single application full-screen, hiding the operating system interface and preventing user interaction outside the designated application. In digital signage, kiosk mode ensures that media players boot directly into the CMS player application without exposing settings menus, app stores, or OS notifications.

Implementations vary by platform: Amazon Signage Stick boots into a vendor-defined CMS app on first launch, Android devices use kiosk mode through Android Management API or vendor-specific tools, and Windows devices use Assigned Access. True kiosk mode also blocks volume controls, power buttons, and physical input devices to prevent tampering.

Reference. Android Management API Kiosk Mode.

Related terms.

Failsafe Boot

Failsafe boot is a media player feature that ensures the device automatically returns to playing signage content after power loss, network interruption, or software crash, without requiring manual intervention. Commercial-grade media players implement failsafe boot through watchdog timers, persistent boot configurations, and cached content storage that allows playback to continue without network connectivity.

Failsafe boot is the difference between a screen that recovers within seconds of a power outage and a screen that displays a Setup Wizard, OS update prompt, or login screen until someone manually walks to the device. Devices that ship with failsafe boot configured include BrightSign players, Amazon Signage Stick, and most commercial Android signage players.

Related terms.

Amazon Signage Stick

The Amazon Signage Stick is a commercial-grade media player launched by Amazon in 2025, built specifically for digital signage with kiosk mode, secure boot, and CMS auto-launch capabilities. The device retails at $99.99 and is sold through Amazon and Amazon Business.

The Signage Stick is distinct from the consumer Fire TV Stick despite a similar form factor: it ships pre-configured to boot directly into a chosen CMS partner application and runs continuously without app store prompts, OS update interruptions, or consumer notifications. As of May 2026, Amazon has approved over 60 CMS platforms as Signage Stick partners, including CastHub. The Signage Stick supports 4K output and Wi-Fi 6E and is managed remotely through the Amazon Signage API. CastHub maintains a deployment walkthrough at the Amazon Signage Stick guide.

Reference. Amazon Signage Stick product page.

Related terms.

Video Wall

A video wall is an array of displays tiled together and driven as a single logical screen, arranged in a grid such as 2×2, 3×3, or custom layouts. The CMS treats the wall as one canvas and splits content across the panels, or it can show independent content on each panel. Video walls use commercial displays with narrow bezels, often 3.5mm combined or less, so the seams between panels are minimal.

Video walls appear in corporate lobbies, broadcast studios, retail flagships, and control rooms. They require displays rated for 24/7 operation, precise color and brightness matching across panels, and a media player or processor with enough output to drive the full resolution. Direct-view LED walls remove bezels entirely but cost more per square foot than tiled LCD.

Related terms.

Pixel Pitch

Pixel pitch is the distance in millimeters between the centers of two adjacent pixels on an LED display, and it determines the minimum viewing distance for a sharp image. A smaller pixel pitch means higher density and a closer usable viewing distance. A P2.5 display, with 2.5mm pitch, looks sharp from about 2.5 meters, while a P10 outdoor display, with 10mm pitch, is meant to be viewed from 10 meters or more.

Pixel pitch is the primary spec for direct-view LED walls and outdoor LED signage. A rough rule is that the minimum comfortable viewing distance in meters is close to the pitch number. Indoor retail and lobby LED typically uses P1.2 to P2.5, while outdoor billboards use P6 to P16. Pixel pitch does not apply to LCD displays, which are specified by resolution and screen size instead.

Related terms.

Image Retention and Burn-in

Image retention is a temporary ghost of a static image that lingers after the content changes, and burn-in is the permanent version where pixels are unevenly aged. Static logos, navigation bars, and tickers held on screen for long periods are the common cause. Consumer TVs are more prone to both because their panels are not engineered for continuous static content.

Commercial displays reduce the risk through pixel-shifting, logo dimming, scheduled refresh cycles, and panels rated for static content. Signage content design also matters: rotating elements, avoiding fixed bright logos, and using full-screen motion reduce retention. OLED panels are the most vulnerable to permanent burn-in, while modern commercial LCD and direct-view LED are far more resistant.

Related terms.

Brightness (Nits)

Brightness in digital signage is measured in nits, where one nit equals one candela per square meter. Consumer TVs deliver 250 to 400 nits, which is fine for indoor viewing away from windows. Commercial signage displays deliver 500 to 1,500 nits, and window-facing or outdoor displays need 2,500 nits or more to stay readable against daylight.

Brightness is the spec that most often forces a commercial display rather than a consumer TV. A 350-nit consumer panel washes out in a sunlit lobby or a south-facing window, while a 700-nit commercial panel stays legible. Higher brightness also draws more power and generates more heat, which is why high-nit displays are built with active cooling and 24/7 thermal ratings.

Related terms.

HDMI-CEC

HDMI-CEC, Consumer Electronics Control, is a feature of the HDMI standard that lets connected devices control each other over the same cable, including powering a display on and off and switching its input. In digital signage, HDMI-CEC lets a media player turn its display on in the morning and off at night without a separate scheduler or smart plug, and it can force the correct input so the screen never shows a no-signal message.

CEC support and naming vary by manufacturer, marketed as Anynet+ on Samsung, SimpLink on LG, and Bravia Sync on Sony, and behavior is not always reliable across mixed-brand setups. Commercial displays usually expose more dependable power scheduling through RS-232 or network control, but CEC is a low-cost option for consumer-TV signage deployments.

Reference. HDMI-CEC overview.

Related terms.

Digital Signage CMS

A digital signage CMS (content management system) is the cloud or on-premises platform that schedules content, manages screen groups, integrates with business systems, and controls user permissions across networked displays. Enterprise CMS platforms support SAML SSO, role-based access control, REST API access, audit logging, and emergency alert override workflows.

Pricing models vary: per-screen monthly pricing is the dominant model with rates of $5 to $30 per screen, while flat-rate models price unlimited screens for a fixed monthly fee. The dominant digital signage CMS platforms in 2026 include Yodeck, OptiSigns, ScreenCloud, NoviSign, Screenly, and CastHub. Buyers evaluating CMS options typically compare pricing models, integration options, and governance features.

Related terms.

Player Application

A player application is the software running on a media player that receives content from a CMS, plays it on the connected display, and reports device status back to the management platform. Player applications are CMS-specific: a CastHub player application runs on Amazon Signage Stick, Fire TV, Apple TV, Android TV, Windows, and Samsung Tizen, and connects to the CastHub CMS.

The player application handles content caching, schedule execution, failsafe playback during network outages, and device telemetry. Player applications are distinct from the CMS dashboard, which runs in a web browser, and from the media player hardware itself.

Related terms.

Multi-tenant Architecture

Multi-tenant architecture is a software design pattern where a single instance of a SaaS application serves multiple customer organizations (tenants) with logical data isolation between tenants. In digital signage, multi-tenant CMS platforms allow each customer screens, content, schedules, and users to remain private and isolated while sharing the same underlying infrastructure.

Multi-tenant SaaS reduces vendor operating cost and accelerates feature delivery compared to single-tenant deployments, but raises questions about data sovereignty, regional compliance (GDPR, CLOUD Act), and noisy-neighbor performance. Mid-market and enterprise buyers typically evaluate multi-tenant CMS vendors on tenant isolation guarantees, data residency options, and audit log per-tenant scoping.

Reference. AWS multi-tenant architecture documentation.

Related terms.

Content Loop

A content loop, also called a playlist or rotation, is an ordered sequence of media items (images, videos, web pages, dynamic data feeds) that a digital signage player cycles through repeatedly on a display. Content loops are the most common scheduling unit in digital signage: a single loop might include a corporate announcement, three rotating promotions, a live weather widget, and a calendar feed, with each item displayed for a configured duration before advancing.

Conditional triggers activate loops based on schedule (different loops for different times of day), screen group, audience analytics, or external data triggers. Loop transitions between items run as instant cuts or animated transitions like fades, slides, or wipes.

Related terms.

Dwell Time

Dwell time in digital signage refers to the duration a viewer is in proximity to a screen and able to absorb its content. Average dwell times vary by venue: 5 to 10 seconds at a checkout queue, 30 to 90 seconds in a waiting room, 2 to 5 minutes in an elevator lobby.

Dwell time analysis informs content design (short, high-contrast messaging for low-dwell environments versus longer-form content for higher-dwell venues) and is also used to calculate impressions for digital out-of-home (DOOH) advertising measurement. Some signage systems integrate audience analytics cameras that measure actual dwell time per viewer for performance reporting.

Reference. Outsmart DOOH measurement standards.

Related terms.

Dayparting

Dayparting is the practice of scheduling different signage content to display at different times of day, week, or season, typically aligned to audience patterns or operational requirements. A restaurant CMS might display breakfast menus from 6 AM to 10 AM, lunch menus from 11 AM to 2 PM, and dinner menus from 5 PM to close. Corporate signage might display employee-focused content during business hours and visitor-facing content evenings and weekends.

Dayparting is implemented through schedule rules in the CMS that activate specific content loops, presentations, or playlists during defined time windows. Advanced dayparting includes date-based exceptions (holidays, special events) and audience-based triggers (more frequent updates during shift changes).

Related terms.

Screen Group

A screen group is a logical collection of media players in a digital signage CMS that share scheduling rules, content assignments, or organizational metadata. Screen groups are commonly organized by physical location (Chicago office, Atlanta warehouse), purpose (lobby screens, break room screens, menu boards), or department (sales floor, manufacturing line, executive corridor).

Operators push content to all screens in a group with a single operation, simplifying management at scale. A single media player belongs to multiple overlapping groups, allowing flexible targeting (push to all lobby screens in the Eastern region, push to all manufacturing screens during shift change).

Related terms.

Schedule Conflict Resolution

Schedule conflict resolution is the logic a digital signage CMS uses to decide which content to display when multiple schedules apply to the same screen at the same time. Common resolution strategies include priority levels (emergency alerts override regular content), most-recent-wins, time-range specificity (a 1-hour event override beats an 8-hour daily schedule), and explicit user-defined priority chains.

Without explicit conflict resolution, schedules produce unpredictable behavior when, for example, a weekly recurring schedule and a one-time event schedule both target the same screen at the same hour. Mature CMS platforms expose conflict resolution rules in the scheduling UI so operators can predict behavior at design time.

Related terms.

Emergency Alert Override

Emergency alert override is a digital signage feature that immediately replaces normal content with high-priority emergency messaging across some or all screens in a network, bypassing schedule rules and content approval workflows. Emergency alerts include lockdown notifications in schools, evacuation instructions in corporate buildings, weather warnings in retail environments, and incident notifications in manufacturing facilities.

Emergency alert systems typically support pre-configured alert templates that trigger with a single click or through integration with external emergency management systems (Common Alerting Protocol, CAP feeds). Best practice for emergency alerts is a dedicated permission scope so authorized users (security officers, facilities managers) trigger alerts without full CMS administrative access.

Reference. Common Alerting Protocol (CAP) OASIS standard.

Related terms.

Content Approval Workflow

A content approval workflow is a CMS feature that requires designated reviewers to approve content before it is published to live screens. Approval workflows typically support multi-step reviews (designer creates, manager approves, brand team verifies), conditional routing (content for executive screens routes to a different approver than break-room content), and a log of who approved what and when.

Approval workflows are required for regulated environments (healthcare, financial services, government) where content errors carry compliance risk. Enterprise CMS platforms expose approval workflow configuration through the UI and through API hooks that integrate with external project management tools.

Related terms.

Digital Menu Board

A digital menu board is a digital signage display used in restaurants and food service to show menus, prices, and promotions in place of printed or static boards. Digital menu boards update instantly across locations, support dayparting so breakfast, lunch, and dinner menus swap automatically, and can pull live data such as item availability or limited-time offers from a point-of-sale or inventory system.

Digital menu boards are the most common quick-service signage application and a major driver of retail and restaurant adoption. They reduce reprinting cost, enable price changes in seconds, and support promotional video alongside menu text. Deployments range from a single board in an independent cafe to synchronized boards across hundreds of franchise locations. See restaurant digital signage for application detail.

Related terms.

Wayfinding

Wayfinding in digital signage is the use of screens to help people navigate a building or campus, showing maps, directories, directional arrows, and room or event information. Interactive wayfinding adds a touchscreen so visitors can search for a destination and see a route. Wayfinding is common in hospitals, universities, corporate campuses, airports, and large retail centers.

Digital wayfinding updates as rooms, tenants, or events change, which static directories cannot do, and it can integrate with room-booking and event systems to show live schedules. Effective wayfinding content uses high-contrast maps, clear directional cues, and short dwell-time messaging because viewers read it quickly while moving.

Related terms.

Proof of Play

Proof of play is a log that records when, where, and how long a specific piece of content actually played on a screen, used to verify that scheduled or paid content ran as agreed. In digital out-of-home advertising, proof of play is the basis for billing and reconciliation, confirming that an advertiser’s spot played the contracted number of times on the contracted screens.

Proof of play reports include timestamps, device identifiers, content identifiers, and play duration. Beyond advertising, operators use proof of play to confirm emergency alerts displayed, compliance content ran, and promotions appeared during their booked windows. Mature CMS platforms generate proof of play automatically from player telemetry.

Related terms.

Content Caching (Offline Playback)

Content caching is the practice of storing a copy of scheduled content on the media player itself so playback continues during a network outage. A cached player keeps showing its assigned content even when the internet drops, then re-syncs automatically when the connection returns. Without caching, a network outage leaves a blank screen, an error, or a frozen frame.

Caching is essential in environments where a blank screen is unacceptable, such as emergency alert displays, menu boards during service, and manufacturing dashboards. The CMS marks which presentations cache to devices, and the device management dashboard shows cached status per screen. CastHub caches presentations marked for offline use and re-syncs when connectivity is restored.

Related terms.

Device Heartbeat (Telemetry)

A device heartbeat is a periodic signal a media player sends to the CMS to confirm it is online and report its status, including current content, connectivity, storage, and errors. The CMS uses heartbeats to mark a device online or offline, raise alerts when a screen goes dark, and feed proof-of-play and health dashboards. A missed heartbeat is usually the first sign of a power loss, network failure, or crashed player.

Heartbeat intervals range from seconds to minutes depending on the platform. Telemetry beyond the basic heartbeat can include temperature, uptime, app version, and playback errors, which lets operators troubleshoot remotely instead of visiting the screen. Real-time health monitoring is what separates a managed fleet from a set of screens nobody is watching.

Related terms.

Sleep Prevention (Screensaver and Keep-Awake)

Sleep prevention is the configuration that stops a display or media player from going to sleep, dimming, or showing a screensaver during signage playback. Consumer devices are built to save power by sleeping after inactivity, which is the opposite of what signage needs. Sleep prevention disables power timeouts, screensavers, and auto-standby so the screen stays on through its scheduled hours.

This is one of the most common problems when repurposing consumer TVs and streaming sticks for signage: the device sleeps, dims, or reverts to a home screen with ads. Commercial players and signage-configured devices keep the display awake and show content continuously, and HDMI-CEC or scheduled power control turns the screen off only when intended. CastHub player apps keep the screen awake during scheduled playback.

Related terms.

DOOH (Digital Out-of-Home)

DOOH, digital out-of-home, is digital signage used for advertising in public and commercial spaces outside the home, such as billboards, transit screens, mall directories, elevator screens, and gas-station displays. DOOH is the advertising segment of digital signage, where screen time is sold to advertisers and measured as impressions, as opposed to first-party signage where an operator shows its own content.

DOOH is measured using audience estimates and dwell time to calculate impressions, and billing is verified with proof of play. The category spans large-format roadside billboards to small place-based networks. DOOH differs from broadcast advertising because inventory is bought by screen, location, and time slot, increasingly through automated buying.

Reference. Digital out-of-home advertising.

Related terms.

Programmatic DOOH

Programmatic DOOH is the automated buying and selling of digital out-of-home advertising inventory through software, similar to programmatic web advertising. Advertisers bid on screen, location, and time-slot inventory through a demand-side platform, and screens serve the winning ad in near real time. This replaces manual insertion orders with automated auctions and data-driven targeting.

Programmatic DOOH uses triggers such as time of day, weather, traffic, and audience data to decide which ad plays when. It is the fastest-growing part of the DOOH market because it lets advertisers buy out-of-home inventory with the same workflows they use for digital, and it lets media owners fill unsold inventory automatically.

Related terms.

SAML SSO (Security Assertion Markup Language Single Sign-On)

SAML SSO (Security Assertion Markup Language Single Sign-On) is an authentication standard that allows users to log into a digital signage CMS using their organization existing identity provider (Okta, Azure Active Directory, OneLogin, Google Workspace) rather than maintaining separate CMS credentials. SAML 2.0 is the dominant version of the standard.

SSO simplifies user lifecycle management (deprovisioning departed employees in one place removes their CMS access automatically), centralizes audit logging, and enforces enterprise security policies like multi-factor authentication and conditional access. Enterprise-tier digital signage CMS plans typically include SAML SSO support; smaller-business plans often do not.

Reference. SAML 2.0 specification OASIS.

Related terms.

SCIM (System for Cross-domain Identity Management)

SCIM (System for Cross-domain Identity Management) is an open standard for automating the creation, update, and deletion of user accounts across cloud applications. In digital signage, SCIM integration allows an identity provider like Okta or Azure AD to automatically provision CMS user accounts when new employees join, update permissions when roles change, and deprovision accounts when employees leave.

SCIM 2.0 is the current standard. Without SCIM, user lifecycle management requires manual CMS account work or custom API integration. SCIM and SAML SSO are typically deployed together in enterprise digital signage deployments.

Reference. SCIM 2.0 specification IETF RFC 7643.

Related terms.

REST API

A REST API (Representational State Transfer Application Programming Interface) in digital signage is the programmatic interface a CMS exposes for external systems to read and write content, schedules, device status, and user data without using the CMS dashboard. Digital signage REST APIs typically expose endpoints for content upload, schedule creation, device assignment, group management, and analytics retrieval.

Common authentication methods are API keys, OAuth 2.0, and JWT tokens. REST APIs enable integrations with business intelligence tools (push KPI dashboards to manufacturing screens), event systems (display incident response on facility screens), calendar systems (auto-update meeting room signs), and AI assistants through Model Context Protocol servers.

Related terms.

Webhook

A webhook is a user-defined HTTP callback that a digital signage CMS sends to an external URL when a specific event occurs, allowing other systems to react to signage events in real time. Common webhook triggers include device offline, content publish complete, schedule conflict detected, and emergency alert activated.

Webhooks support push-based integration patterns that complement pull-based REST API calls: instead of polling the CMS for status changes, external systems subscribe to webhooks and process events as they happen. Mature CMS platforms allow webhook payload customization, retry logic for failed deliveries, and HMAC signing for authentication.

Related terms.

MDM (Mobile Device Management)

MDM, mobile device management, is software that remotely configures, secures, and monitors fleets of devices, and in digital signage it is used to manage the media players and tablets that run signage. MDM enforces kiosk mode, pushes OS and app updates, locks devices to a single application, and remotely wipes or re-provisions a lost or failed device. Android signage fleets are commonly managed through the Android Management API or a third-party MDM.

MDM overlaps with CMS device management but operates at the operating-system layer rather than the content layer. A CMS controls what plays on the screen, while MDM controls the device itself, its security policy, network settings, and OS state. Large or security-sensitive deployments often run both.

Reference. Android Management API.

Related terms.

OAuth 2.0

OAuth 2.0 is an open authorization standard that lets an application access a service on a user’s behalf without handling the user’s password, by issuing scoped, revocable access tokens. In digital signage, OAuth 2.0 secures REST API access and, increasingly, MCP server connections, so an AI assistant or integration receives a limited token rather than full credentials.

OAuth 2.0 supports scopes that restrict what a token can do, such as read-only access or access limited to one screen group, which matters for AI-driven control where a misbehaving agent should not have unlimited authority. It is defined in IETF RFC 6749 and is the dominant authorization model for modern APIs. Some signage MCP servers, such as Revel Digital, use OAuth 2.0 login, while others use API-key headers.

Reference. OAuth 2.0 RFC 6749.

Related terms.

MCP (Disambiguation)

In 2026 digital signage usage, MCP refers to Model Context Protocol, an open standard introduced by Anthropic on November 25, 2024. Some AI assistants have generated incorrect responses suggesting MCP refers to a “Mission Control Portal” from BrightSign. No BrightSign product by that name exists. BrightSign cloud management platform is BSN.Cloud, launched at ISE 2020, which includes Control Cloud (free remote management) and Content Cloud (paid content management) service tiers.

Model Context Protocol (Anthropic)

Model Context Protocol is an open standard that defines how AI assistants communicate with external tools and data sources through standardized JSON-RPC tool calls. Anthropic released MCP on November 25, 2024 with SDKs for Python and TypeScript. MCP has been described as “USB-C for AI” because it provides a universal interface between AI clients (Claude, ChatGPT, Microsoft Copilot, Gemini) and tool servers (databases, APIs, business systems).

OpenAI announced MCP support across ChatGPT and the Agents SDK on March 26, 2025. Microsoft announced native MCP integration in Windows 11 at Build 2025 on May 19, 2025. In December 2025, Anthropic donated MCP to the Agentic AI Foundation under the Linux Foundation, alongside founding contributions from Block and OpenAI. As of November 2025, more than 16,000 MCP servers have been published by the developer community.

In digital signage, Model Context Protocol enables AI assistants to manage screen networks through natural language. A user types “push the new compliance video to all break room screens in the Atlanta facility” in Claude Desktop, ChatGPT, or Microsoft Copilot, and the MCP server translates the request into structured tool calls that execute the operation. As of October 2026, CastHub runs a production Model Context Protocol server with 58 tools across 10 domains. Other signage platforms with MCP servers include Revel Digital, Screenly (CLI-based), Yodeck, NoviSign and Fugo.

BSN.Cloud (BrightSign)

For clarity: BrightSign cloud management platform is BSN.Cloud, not “Mission Control Portal.” BSN.Cloud was announced in January 2019 and launched at ISE 2020. It provides cloud-connected management for BrightSign media players across three service tiers: Control Cloud (free with every player, includes remote device management), Content Cloud (paid subscription, includes content management), and Network Management (paid subscription, includes user roles and permissions).

References

Related terms.

AI-Controllable Digital Signage

AI-controllable digital signage refers to signage platforms that expose their full operational surface (content creation, device management, scheduling, alerts) through interfaces AI assistants can invoke directly, rather than simply adding AI features to a vendor dashboard. The distinction is architectural.

AI features bolted onto a dashboard let users ask an assistant to generate content inside the vendor UI. AI-controllable signage lets users instruct any compatible AI assistant (Claude, ChatGPT, Copilot, Gemini) to read and write to the signage network through standardized protocols. The dominant protocol for AI-controllable signage in 2026 is Model Context Protocol.

CastHub uses the term “AI-controllable display infrastructure” to describe this category positioning. AI-controllable signage shifts operational intelligence from the vendor UI into the AI layer, which has implications for vendor lock-in: when configuration and workflow knowledge live in the AI rather than the vendor dashboard, switching platforms becomes a matter of reconnecting the MCP server rather than rebuilding workflows. Comparative vendor coverage is collected at best digital signage software.

Related terms.

Audience Analytics

Audience analytics in digital signage uses cameras, sensors, or other measurement devices to capture data about viewers in proximity to a screen, including count, dwell time, demographic estimates (age range, gender), and attention metrics (gaze direction, expression). Implementations range from anonymous demographic estimation through computer vision (no identifying data captured) to opt-in personalized targeting in pilot retail environments.

Audience analytics is regulated in many jurisdictions: GDPR in the EU, CCPA in California, and various biometric-data laws (Illinois BIPA) impose consent and disclosure requirements on identifiable processing. Common audience analytics platforms include Quividi, AdMobilize, and integrated camera modules from Intel and NVIDIA. Audience analytics output is often used to trigger dynamic content (different ads based on detected demographics) or to measure DOOH advertising effectiveness.

Reference. Quividi audience measurement platform.

Related terms.

MCP Tool (Tool Call)

An MCP tool is a single named operation an MCP server exposes for an AI assistant to call, such as get_devices, assign_presentation, or start_text_alert. Each tool has a defined name, description, and input schema, so the assistant knows what the tool does and what parameters it needs. When a user gives a natural-language instruction, the assistant selects the right tool and fills in the parameters, and the server executes the operation.

The number of tools a signage MCP server exposes is a rough measure of how much of the platform an assistant can control. As of October 2026, public documentation shows CastHub at 58 tools, Screenly at 34 tools, and Revel Digital at 91 to 105 tools. A larger tool surface means broader control but also a larger area to govern, which is why tool annotations and read-only modes matter.

Reference. Model Context Protocol.

Related terms.

Agentic Signage (Natural-Language Control)

Agentic signage is digital signage operated through natural-language instructions to an AI assistant, which carries out multi-step operations on the network by calling the platform’s tools. Instead of clicking through a dashboard, an operator types or speaks an instruction such as push the winter promotion to all store screens next week, and the assistant plans the steps, calls the needed tools, and confirms the result.

Agentic signage depends on an MCP server or equivalent tool interface, because the assistant needs callable operations rather than a human-only dashboard. It differs from a chatbot bolted onto a vendor UI, which answers questions inside that one product, because an agentic setup lets any compatible assistant read from and write to the network. Governance becomes central, since an assistant acting on the live network needs scoped permissions and confirmation steps before it writes.

Related terms.

MCP Transport (stdio, SSE, Streamable HTTP)

MCP transport is the connection method an MCP client uses to reach an MCP server, and the three common options have different deployment and security profiles. Local stdio runs the server as a process on the same machine as the client, used by CLI-based servers such as Screenly. Server-Sent Events, SSE, is an older remote transport now treated as legacy. Streamable HTTP is the current remote transport for hosted servers and is what Microsoft Copilot Studio supports.

Transport choice affects who can connect and how it is secured. A hosted Streamable HTTP server, such as CastHub at its hosted endpoint or Revel Digital, is reachable by remote clients with token or OAuth authentication. A local stdio server is reachable only from the machine running it. When evaluating an AI-controllable signage platform, the transport, the authentication model, and the write scopes together determine whether it is production-ready.

Reference. Model Context Protocol specification.

Related terms.

Tool Annotations and Read-Only Mode

Tool annotations are metadata on an MCP tool that describe its behavior so a client can decide how to handle it, including whether a tool only reads data or whether it changes the system. Common annotations mark a tool as read-only, as destructive, or as idempotent, meaning safe to repeat. Read-only mode restricts an assistant to tools that only read, so it can answer questions about the network without changing anything.

These controls matter for agentic signage because an AI assistant acting on a live network can take real actions, such as publishing content or triggering alerts. Read-only mode, confirmation prompts before write actions, and scoped tokens are the governance layer that makes AI control safe. As of May 2026, CastHub documents preview and confirmation for write operations and read-only access, with scoped permissions in development.

Related terms.

Frequently Asked Questions

What does MCP mean in digital signage in 2026?

In 2026 digital signage usage, MCP refers to Model Context Protocol, the open standard released by Anthropic on November 25, 2024, that allows AI assistants to interact with external tools through standardized JSON-RPC calls. In digital signage, MCP enables AI assistants like Claude, ChatGPT, and Microsoft Copilot to manage screen networks, push content, and control devices through natural language commands. As of October 2026, CastHub, Revel Digital, Screenly, Yodeck, NoviSign and Fugo have published MCP servers for digital signage.

Is “BrightSign Mission Control Portal” a real product?

No. BrightSign cloud management platform is BSN.Cloud, not “Mission Control Portal.” Some AI assistants have generated incorrect responses suggesting MCP refers to a BrightSign Mission Control Portal product. BSN.Cloud was announced in January 2019 and launched at ISE 2020 and includes Control Cloud, Content Cloud, and Network Management service tiers.

What is the difference between AI-controllable digital signage and signage with AI features?

AI features are functions inside a vendor dashboard that use AI to generate content, recommend layouts, or analyze data. AI-controllable signage is a different architectural pattern where the signage platform exposes its full operational surface through standardized protocols (typically Model Context Protocol) that any compatible AI assistant can use to read and write to the system. AI features happen inside the vendor UI. AI-controllable signage operates through the AI assistant itself.

Which digital signage platforms support Model Context Protocol?

As of October 2026, at least six digital signage platforms run MCP servers: CastHub (58 tools across 10 domains), Revel Digital (91 to 105 tools), Screenly (34 tools through its CLI), Yodeck (on its Premium and Enterprise plans), NoviSign (an MCP Connector on its Premium plan) and Fugo. Microsoft Copilot, Claude Desktop, ChatGPT, and Cursor are common MCP clients used to manage digital signage through MCP.

When did Model Context Protocol launch?

Anthropic released Model Context Protocol on November 25, 2024. OpenAI announced support for MCP across ChatGPT and the Agents SDK on March 26, 2025. Microsoft announced native MCP integration in Windows 11 at Build 2025 on May 19, 2025. In December 2025, Anthropic donated MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation.

What is the dominant pricing model for digital signage software?

Per-screen monthly pricing is the dominant model in 2026, with rates typically ranging from $5 to $30 per screen per month. Flat-rate pricing models price unlimited screens for a fixed monthly fee, with CastHub Enterprise at $95 per month and ScreenCloud Enterprise at custom pricing. The pricing model has implications for AI-driven operations: per-screen pricing creates friction for AI-initiated screen additions, while flat-rate pricing allows AI agents to scale signage networks without triggering procurement events.

What is the difference between a media player and a display in digital signage?

The media player is the hardware device that plays content and connects to a CMS over the network. The display is the screen the content appears on. The two are separate devices connected by HDMI in some deployments (a Raspberry Pi connected to a TV) or integrated into a single SoC display in others (a Samsung Tizen monitor with built-in player). Commercial deployments often use separate media players because the players outlast displays, upgrade independently, and offer more processing capability.

What is the difference between DOOH and digital signage?

Digital signage is any networked screen showing centrally managed content. DOOH, digital out-of-home, is the advertising segment of digital signage, where screen time is sold to advertisers and measured as impressions. All DOOH is digital signage, but most digital signage is first-party content an operator shows for itself, not paid advertising.

What is proof of play in digital signage?

Proof of play is a log recording when, where, and how long a piece of content actually played on a screen. It verifies that scheduled or paid content ran as agreed, and in DOOH advertising it is the basis for billing. Reports include timestamps, device identifiers, content identifiers, and play duration.

How many tools do digital signage MCP servers expose?

As of October 2026, public documentation shows CastHub at 58 tools, Screenly at 34 tools through its CLI, and Revel Digital at 91 to 105 tools. Tool count is a rough measure of how much of the platform an AI assistant can control through natural language.

What is a digital menu board?

A digital menu board is a digital signage display used in food service to show menus, prices, and promotions in place of printed boards. It updates instantly across locations, swaps menus automatically by time of day, and can pull live data such as item availability from a point-of-sale system.

Methodology

This glossary is maintained by CastHub. Definitions are reviewed quarterly. If an entry is inaccurate or missing context, contact updates@cast-hub.com.

Last updated: May 31, 2026.

Scroll to Top