# TelemetryOS > TelemetryOS is a vertically integrated screen platform — Node hardware, hardened Edge OS, Studio cloud, video CDN, and application runtime engineered together as one stack. One vendor provides the hardware, operating system, cloud platform, video CDN, and enterprise controls — so organizations can run digital signage, interactive kiosks, and custom screen applications that read sensors, control equipment, and scale across thousands of locations without stitching together multiple vendors. Most digital signage solutions are content schedulers: they loop images and videos on a screen. TelemetryOS solves a different problem. It provides the complete stack for screens that sense and respond — from a hardened edge device (Node Pro) wired into the operational environment via sensors, PLCs, cameras, serial equipment, and actuators (lighting, relays, and industrial controls over MQTT), to a cloud platform where teams manage fleets, deploy code, and monitor performance at scale. The platform evolved from TelemetryTV, an established digital signage CMS that already powers tens of thousands of screens globally. TelemetryOS extends that proven foundation with a low-code application layer, an integrated CI/CD pipeline (push code on GitHub, it deploys to screens), and an IoT integration fabric (APIs, webhooks, MQTT, serial) that lets screens react to real-time business data — inventory changes, sensor triggers, jackpot events, queue status — without custom middleware. The result is a single platform that handles both traditional signage (playlists, scheduling, media libraries, proof-of-play) and interactive applications (kiosks, dashboards, guided selling, wayfinding) without maintaining two separate systems. --- ## TelemetryTV to TelemetryOS Evolution URL: https://telemetryos.com/evolution TelemetryOS is the evolution of TelemetryTV: the proven content scheduling, device management, media library, proof-of-play, and fleet monitoring foundation customers already know, extended with a modern screen application layer. The page is designed for TelemetryTV customers arriving from telemetrytv.com. Its central message is that TelemetryOS is optional, pilot-friendly, and built on what already works. TelemetryTV remains supported, while TelemetryOS is the next-generation path for screen networks that need custom applications, Git-to-screen deployment, integrations, real-time data, IoT, and fleet observability. Primary CTA: Explore TelemetryOS, linking to the homepage. Key messages: - TelemetryOS carries forward familiar signage operations: playlists, schedules, media, proof-of-play, users, and device monitoring. - New capabilities include React screen applications, managed deployment, staged rollout, rollback, SDK access, APIs, MQTT, sensors, cameras, and operational data integrations. - Migration is not mandatory. Customers can start with a pilot, run TelemetryTV and TelemetryOS side by side, and move use cases gradually. - Use cases highlighted include retail and kiosks, healthcare, transportation, quick service restaurants, corporate communications, and industrial manufacturing. --- ## Platform Overview URL: https://telemetryos.com/product/platform-overview Complete digital signage and kiosk platform — content scheduling, video CDN, device management, proof-of-play, and emergency overrides — plus a full application layer for when you need screens to do more. ### Enterprise Signage, Fully Managed Playlists, scheduling, video delivery, device monitoring, and remote management — the foundations that every screen network requires, built into one vertically integrated stack. - **Content Scheduling & Playlists** — Create playlists, set time-based schedules, assign content to screens or groups, and manage your entire media library from one cloud console. Dayparting, looping, and priority-based scheduling come built in. - **Video CDN & Media Delivery** — Integrated content delivery network with adaptive bitrate streaming optimizes video for every screen and connection. Content is cached locally on devices for reliable playback regardless of network conditions. - **Device Management & Monitoring** — Live screenshots, health telemetry, console log streaming, and remote restart for every device. Organize by location, department, or custom tags — manage thousands of screens without dispatching a technician. ### Operational Controls - **Emergency Overrides & Priority Alerts** — Push critical notifications — fire alerts, security messages, severe weather warnings — to every screen instantly, preempting all scheduled content. Priority levels ensure the right message reaches the right screens. - **Proof-of-Play & Audit Logging** — Verify that content played when and where it was supposed to. Timestamped playback logs, screenshot capture, and reporting give you the compliance and accountability trail that advertisers and regulators require. - **Role-Based Access & Enterprise Controls** — SAML SSO, granular role-based permissions, and audit logging let multiple teams share one platform. Content managers schedule, developers deploy apps, and ops teams manage the fleet — each from the same console. ### Hardware That Just Works - **Purpose-Built Hardware, Zero Configuration** — Node Mini and Node Pro are preconfigured for TelemetryOS. Plug in, connect to your network, and the device appears in your console ready for content. No OS setup, no app installs, no manual provisioning. - **Automatic OS Updates & Watchdog Recovery** — TelemetryOS Edge applies updates atomically in the background and activates on reboot. Watchdog recovery handles crashes and power loss automatically — no maintenance windows across your fleet. ### Fleet Management at Scale - **Live Device Dashboards** — See real-time screenshots, CPU and memory usage, network status, and storage levels for every device. Spot problems before they become outages. - **Remote Diagnostics & Restart** — Stream console logs, inspect running applications, and remotely restart unresponsive devices. Resolve field issues in minutes instead of scheduling a site visit. - **Group-Based Deployments** — Organize devices by location, department, or custom tags. Push content, applications, or OS configurations to a group and every device updates automatically — with staged rollout controls. - **Enterprise Network Support** — WPA enterprise Wi-Fi, 802.1x authentication, static IP, proxy server configuration, and VLAN support. - **SOC 2 Type I & GDPR Compliance** — SAML SSO, role-based access control, audit logging, end-to-end encryption, and a documented compliance program. ### Application Platform When playlists aren't enough, build full screen applications in React — interactive kiosks, live dashboards, data-driven menus, wayfinding — using the same web technologies your team already knows. - **React & TypeScript SDK** — Full @telemetryos/sdk with persistent storage, hardware APIs, weather, MQTT, proxy fetch, media library, and playlist control. - **AI-Native Development** — 18-tool MCP server and domain-specific skills let AI agents build, test, and deploy complete screen applications. Works with Claude Code, Cursor, and Windsurf. - **Git-to-Screen CI/CD** — Connect GitHub, push a commit, and TelemetryOS automatically builds and deploys to every assigned screen. Branch deployments, staged rollouts, and one-click rollback. ### IoT & Hardware Integration - **MQTT Integration** — Publish and subscribe to any MQTT broker on your local network. Read sensors, send commands to actuators, and control equipment in real time — bidirectional messaging with no middleware. - **Hardware I/O** — WebSerial, WebUSB, Bluetooth, and camera browser APIs work natively in TelemetryOS applications. Connect PLCs, barcode scanners, RFID readers, USB cameras, and control systems from JavaScript. - **Docker on Device** — Run containerized workloads directly on Node Pro alongside your screen application — local data processing, protocol bridges, and custom integration services. - **Offline-First Architecture** — Content and applications cache locally. Screens on isolated networks keep running and processing without any cloud dependency. --- ## Page Layout Engine URL: https://telemetryos.com/product/page-layout-engine Visual canvas editor included in every TelemetryOS Studio plan — design multi-zone screen layouts, schedule content by daypart, manage video walls, and publish to your fleet instantly. ### A Layout Editor Built for Signage - **A Canvas Built for Screens** — Infinite pan-and-zoom canvas, layers panel, multi-select, grouping, snap-to-grid, and pixel-precise positioning — a professional design environment purpose-built for digital signage, not repurposed from presentation software. - **Scheduling Baked In, Not Bolted On** — Every page carries its own schedule: day of week, time windows, date ranges, and device tag targeting. The right content plays on the right screen at the right moment, without a separate scheduling system. - **AI Assist Page Generation** — Describe the screen you need and AI Assist drafts the layout — content regions, styling, and structure ready on the canvas to refine and publish. ### Designed for Operators, Not Just Designers - **Draft → Publish Workflow** — Edit a draft of any live layout without touching what's on screen. A ready-for-review flag brings stakeholders into the loop before one-click fleet-wide publishing. - **Content Override & Interrupt** — Push priority content to any screen or the entire fleet — immediate, scheduled, recurring, or CAP webhook-triggered. Displays return to normal rotation when the override expires. - **Touch-Native Interactivity** — Buttons that navigate pages, trigger media, or launch websites, each with timeout-and-return behavior. One editor powers passive signage and interactive kiosks. - **iOS App Companion** — Pair new screens by QR code, push overrides, and manage media from iPhone, iPad, or Mac. ### From Canvas to Venue - **Video Wall Layouts** — Define a multi-screen grid and position content that spans physical displays. The editor renders exact panel boundaries so walls are designed before installation. - **Rich Media Zones** — Image, video (with subtitle/VTT support), animated GIF, WebShot, Canva design, and AI-generated assets play natively, with rotation intervals, fit modes, and zoom effects. - **Embedded Application Blocks** — Drop live application blocks — weather, dashboards, news feeds — onto the canvas as positioned items, version-pinned or always-latest. - **35+ Page Transitions** — Fade, push, fold, glue, scale, and more, applied per page or as a playlist default and previewed in the editor. - **Ad Campaign Integration** — Inject ad content from campaign folders into media zones at configurable frequency, with proof-of-play CSV exports for advertisers. - **Real-Time Fleet Sync** — Publish and every assigned device updates instantly via WebSocket. - **Reusable Page Templates** — Export any layout as a portable template with embedded or linked media; import across teams, brands, or locations. --- ## Node Hardware Series URL: https://telemetryos.com/product/hardware Purpose-built hardware for every screen deployment. From single-screen signage to enterprise-grade multi-display deployments, TelemetryOS Nodes deliver reliable, secure, always-on performance. ### Node Mini — $299 Compact, fanless media player for single-screen signage and displays. Quad-core ARM processor with 4K output. Ideal for standard digital signage deployments requiring reliable, cost-effective hardware. ### Node Pro — $499 High-performance, enterprise-grade hardware for multi-screen deployments. Intel N150 processor with triple 4K output, Docker container support, RS-232/RS-485 serial communication, USB peripherals, and MQTT connectivity. **Node Pro key capabilities:** - Triple 4K display output (60Hz per display) - Intel N150 processor with hardware-accelerated graphics - Docker container support for edge workloads - RS-232/RS-485 serial for direct industrial equipment communication - USB peripheral access (cameras, scanners, RFID readers, sensors) - MQTT broker connectivity for IoT integration - Offline caching and watchdog auto-recovery - Fanless passive cooling for silent 24/7 operation ### Node Max — Custom High-performance hardware for on-device LLMs, multi-camera vision, and heavy container workloads. AMD Ryzen AI processor with quad 8K-capable output (1x DP, 1x HDMI, 2x USB-C), up to 64 GB DDR5 memory, up to 8 TB NVMe storage, dual 2.5 GbE, and WiFi 7-ready connectivity. ### Shared Hardware Benefits - **Fanless Design** — Silent operation with passive cooling eliminates moving parts for maintenance-free deployment - **Ultra-Low Power** — Efficient operation enables deployment anywhere with minimal infrastructure requirements - **1-Year Hardware Warranty** — Comprehensive hardware protection for peace of mind and long-term reliability - **Optimized Provisioning** — Preconfigured setup enables quick deployment to get Nodes online in minutes --- ## Developer App URL: https://telemetryos.com/product/developer-app Desktop IDE with AI-native development, live canvas preview, MCP server, and one-command deployment. The TelemetryOS Developer App is a desktop IDE purpose-built for digital signage and kiosk application development. Features include: - Live canvas preview across 8 aspect ratio presets (5:1 to 1:5) with hot module replacement and light/dark modes - Built-in device emulation — 4-scope storage, media library, weather, MQTT, and device APIs simulated locally, no hardware or network required - Integrated MCP server with 18 tools for AI-assisted development; 15 domain-specific skills for screen app workflows - One-command deploy — version bump, archive, upload, cloud build, and rollout to assigned screens, also exposed as an MCP tool - Git-to-screen CI/CD with branch deployments, staged rollouts, and one-click rollback - Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI agent --- ## SDK URL: https://telemetryos.com/product/sdk Build screen applications with React and TypeScript. The TelemetryOS SDK provides platform APIs while standard browser APIs handle hardware access. **Three Mount Points:** - Render — visual component on physical screens and Studio preview - Settings — configuration UI in TelemetryOS Studio for administrators - Web — browser-accessible interfaces for staff dashboards, operator desks, and public forms **SDK APIs:** - 4-scope persistent storage (Application, Instance, Device, Shared) with real-time sync - Bidirectional MQTT — publish commands to actuators, subscribe to sensor data - Proxy fetch with fleet-wide caching and CORS handling - Media library queries by folder, tag, or individual item - Playlist control — advance pages, adjust duration, navigate programmatically - Emergency override triggers and event listeners - Weather data — 30+ fields including conditions, forecasts, and severe alerts - Device webhooks — stream logs, playback events, and view data **Browser APIs (native access):** - WebSerial — RS-232/RS-485 serial communication with PLCs, actuators, and equipment - WebUSB — barcode scanners, RFID readers, USB sensors - Web Bluetooth — peripheral pairing and communication - Camera API — USB camera streaming directly into applications **Developer Experience:** - 23 pre-styled React settings components (dropdowns, sliders, color pickers, toggles) - Store hooks with automatic subscriptions and cleanup - UI scale hooks for responsive sizing across screen dimensions - Offline-first — applications run client-side after download **Shipping:** - Works with AI agents via the Developer App's 18-tool MCP server (Claude Code, Codex, Cursor, and any MCP-compatible agent) - Git-to-screen CI/CD — push a commit and TelemetryOS builds, hosts, and deploys to every assigned screen, with branch deployments and one-click rollback - Developer App live canvas preview across 8 screen aspect ratios with hot reload --- ## Deployment Pipeline URL: https://telemetryos.com/product/deployment Push code, we build, host, and deploy to every screen. The complete hosting platform for screen applications — no servers, no CDN, no deployment scripts. **How It Works:** - Connect GitHub, or upload a zip file for simpler workflows - Every push triggers a cloud build with real-time log streaming - Build artifacts are hosted on TelemetryOS infrastructure and delivered via CDN - New builds deploy automatically to every assigned device - One-click rollback to any previous version — zero downtime **Advanced Workflows:** - Branch deployments — develop branch to QA devices, main to production - One-click publish from the Developer App — same flow exposed to AI agents via the built-in MCP server for automation pipelines - Staged rollouts to device subsets before fleet-wide release - Versioned build history with instant rollback from the console - Platform MCP server at `mcp.telemetryos.com/mcp` — connect Claude Code, Codex, or any MCP-compatible agent to manage devices, playlists, media, and overrides. Scoped tokens with granular resource, action, and field-level permissions enforce least-privilege access. - Webhook notifications keep team communication and monitoring platforms in the loop on every build and deploy - Data residency: host your account in US, EU, UK, Canada, or Asia-Pacific regions without changing your deployment workflow **What You Don't Manage:** - No build servers (Jenkins, GitHub Actions, CircleCI) - No hosting infrastructure (S3, CDN, Cloudfront) - No deployment scripts (Ansible, shell scripts) - No rollout orchestration — staged deploys and canary releases built in --- ## AI Development URL: https://telemetryos.com/product/ai-development Build screen applications with AI agents. An 18-tool MCP server and 15 domain-specific skills turn Claude Code, Cursor, Windsurf, and any MCP-compatible AI agent into TelemetryOS application specialists. ### 18-Tool MCP Server The Developer App includes a built-in Model Context Protocol server that gives AI agents direct control over the development environment: - **Store Tools (6)** — Read, write, delete, list keys, dump entries, and list namespaces across all 4 storage scopes - **Visual Capture Tools (2)** — Screenshot the rendered application at any aspect ratio; automatic sweep across all 8 presets - **Canvas Control Tools (4)** — Set aspect ratio, background, active tab (render/settings/web), and color scheme (light/dark) - **Log & Diagnostics Tools (3)** — Read console output, dev server logs, and platform operation logs with time and level filtering - **Runtime Control Tools (2)** — Soft/hard reload, restart dev server - **Data Tools (1)** — Reset all simulation data to defaults The AI agent never needs to leave the code editor — the MCP server provides visual feedback, data manipulation, and diagnostics. ### 15 Domain-Specific Skills Skills encode deep platform expertise into structured guidance: - **Planning** — 6-phase interactive requirements gathering (Vision, Render, Data, Settings, Multi-Mode, Summary) - **Architecture** — Mount point architecture, multi-mode app patterns - **Design** — Signage display patterns, kiosk interaction patterns (touch, idle, sessions), web view SPA routing, settings UI components - **Data & Integration** — Store sync patterns, proxy fetch for external APIs, weather API, media library access - **Testing** — Visual testing via MCP screenshots, store data testing via MCP tools - **Debugging** — Common errors and fixes reference guide ### Agent-Agnostic Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI agent. Zero-configuration setup — open a TelemetryOS project and the MCP server, skills, and tool permissions are pre-configured. ### End-to-End AI Workflow 1. Scaffold — create a new project from a template in the Developer App, AI skills pre-loaded 2. Requirements — AI gathers requirements through structured 6-phase conversation 3. Implement — skills-guided code generation for store, settings, render, and web views 4. Test — AI takes screenshots at every aspect ratio, seeds test data, reads logs 5. Iterate — reload, adjust, screenshot again — visual feedback loop in the editor 6. Publish — one action inside the Developer App (or via MCP) handles version bump, cloud build, and deploy to screens --- ## Edge AI URL: https://telemetryos.com/product/edge-ai Run LLMs and computer vision on the device. TelemetryOS Edge AI brings conversational kiosks, visual inspection, and smart retail to Node Max — private by design, no cloud round-trip. ### Three Pillars - **On-Device LLMs** — Open-weight language models run directly on the Node Max NPU, iGPU, and CPU. Conversational concierge kiosks, multilingual wayfinding, and retrieval-augmented product discovery answer in real time without the latency, privacy exposure, or per-query cost of cloud LLMs — and keep working when the network doesn't. - **Multi-Stream Computer Vision** — Detection, classification, OCR, and embedding models run on live USB or IP camera feeds: visual inspection at line speed, out-of-stock detection on the shelf, queue measurement, occupancy, and audience-aware content. Footage is analyzed on the device and discarded. - **Private by Design** — No cloud round-trip and no PII stored. Inference runs inside the hardened TelemetryOS Edge environment on the device, which is what makes AI deployable in healthcare, gaming, education, and other regulated spaces. ### How Edge AI Runs - AMD Ryzen AI silicon on Node Max: 12-core Zen 5 CPU, Radeon 890M GPU, and XDNA 2 NPU rated at up to 50 TOPS — up to 80 TOPS combined platform AI compute. Quad 8K-capable output (1x DP, 1x HDMI, 2x USB-C), up to 64 GB DDR5, up to 8 TB NVMe. - AI runtimes ship as Docker sidecars beside the TelemetryOS application: llama.cpp with Vulkan acceleration, Ollama as a hosted endpoint, ONNX Runtime for vision and speech, Whisper for speech recognition — exposing local OpenAI-compatible or gRPC endpoints. - TelemetryOS validates the runtime configurations end-to-end on TelemetryOS Edge and the Ryzen AI silicon; specific models refresh with the ecosystem, the runtimes and silicon are the stable interface. - OCuLink eGPU expansion: four lanes of PCIe 4.0 to an external GPU enclosure scale Node Max from the integrated NPU to discrete-GPU class inference. ### Managed Like Any Other Workload - TelemetryOS Studio manages the AI sidecar and the screen application as one fleet — health monitoring, remote diagnostics, group deployments, staged rollouts. - AI container images update through the same signed OTA pipeline as the OS and applications, with one-click rollback. - The screen application fronting an AI workload deploys via git-to-screen CI/CD like any TelemetryOS app. - Standard x86 / Linux / Docker / open-source ML stacks — no CUDA lock-in, no proprietary inference SDK forks. ### Regulated Deployments In most regulated jurisdictions, patient data and casino surveillance footage cannot transit cloud AI services. Node Max runs the language model and the vision pipeline on the device inside TelemetryOS Edge — the data never leaves the property. TelemetryOS is SOC 2 Type I certified and GDPR compliant, with application sandboxing, audit logging, and cloud data residency across US, EU, UK, Canada, and Asia-Pacific regions. ### Common Edge AI Deployments - **AI Concierge Kiosks** — guests get answers in their own language, around the clock, with conversations processed entirely on the device - **AI Visual Inspection** — defect detection at line speed with millisecond latency, results flagged to floor screens and correlated with MQTT sensor data - **Smart Drive-Through Menus** — anonymous vehicle recognition and order recall on the device, no faces, no PII - **Smart Cooler & Shelf Screens** — out-of-stock detection and anonymous engagement measurement while the glass keeps selling - **Healthcare Digital Front Door** — multilingual check-in and translation with PHI staying in the facility by architecture - **Multi-Container Edge Compute** — the TelemetryOS application, inference sidecars, MQTT brokers, content caches, and protocol adapters running concurrently on one Node Max --- ## Device Management URL: https://telemetryos.com/product/device-management Fleet monitoring, remote diagnostics, and control at scale. TelemetryOS Studio provides centralized device management for screen fleets of any size: - Live thumbnails with CPU, memory, and network telemetry for every device - Console log streaming, crash reports, and live screenshots for remote debugging - Remote restart and application control — fix field issues without truck rolls - Group-based organization by location, function, or custom tags - Group deployments with staged rollouts and one-click rollback - Offline alerts by email, SMS, or webhook with configurable thresholds - Atomic background OS updates with watchdog recovery — no maintenance windows - Zero-touch hardware provisioning; QR code pairing from the iOS app - Fleet health, commands, and emergency overrides from iPhone, iPad, and Mac - Proof-of-play reporting with CSV exports - REST API and webhooks for monitoring and ITSM integration - Git-to-screen CI/CD for application deployments - Role-based access, SCIM provisioning, audit logging, SOC 2 Type I, GDPR, and data residency in US, EU, UK, Canada, and Asia-Pacific - Manages Edge AI workloads on Node Max alongside the rest of the fleet --- ## iOS App URL: https://telemetryos.com/product/ios-app Native iPhone, iPad, and Mac app — manage your screen fleet from your pocket. The TelemetryOS iOS app puts the whole network in your pocket for operators, installers, and field techs: - Fleet health at a glance — live device status for every screen - Drill into device stats, logs, and settings; send commands remotely - Pair new screens on-site by scanning a QR code — no laptop or console session required - Control which applications, playlists, and pages screens run - Push instant overrides to any screen or group, including emergency preemption - Browse, upload, or AI-generate media and deploy it from anywhere - Verify a new install is online, running the right content, and reporting healthy telemetry before leaving the site - Included with every TelemetryOS Studio plan --- ## Digital Signage URL: https://telemetryos.com/product/digital-signage Enterprise digital signage software: content scheduling, playlists, an integrated video CDN, proof-of-play reporting, and instant overrides at fleet scale. TelemetryOS handles full traditional digital signage alongside interactive applications: - Content scheduling with dayparting, targeting rules, content expiration, and priority-based scheduling - Playlist management with templates, content libraries, and AI Assist page generation in the Page Layout Engine - Multi-location fleet targeting — push a campaign to one store, a region, or the whole network in a single action - Proof-of-play reporting with timestamped playback logs, screenshot capture, and CSV exports for advertisers, regulators, and audits - Media library with cloud storage, version control, auto-expiry, and integrated video CDN delivery (adaptive bitrate streaming) — smooth playback at 10 or 10,000 screens - Advertising campaign management — schedule, target, and verify ad campaigns in the same console as operations, turning the screen network into a revenue channel - Offline caching — content plays through network outages and syncs when connectivity returns - Emergency overrides — instant, scheduled, or CAP-triggered from emergency management systems, with priority levels - iOS app for QR code device pairing, fleet health, and overrides from iPhone, iPad, and Mac - Grows into full React screen applications with git-to-screen CI/CD, and on-device Edge AI on Node Max (private by design) - Enterprise security: SOC 2 Type I, GDPR, SAML SSO, SCIM provisioning, RBAC, audit logging, and data residency across US, EU, UK, Canada, and Asia-Pacific --- ## Interactive Kiosks URL: https://telemetryos.com/product/interactive-kiosks Self-service kiosk software on the same console as your signage — peripheral access via the SDK, offline resilience, remote fleet management, and on-device AI when you're ready. TelemetryOS enables full interactive kiosk deployments: - Real kiosk applications: full React/JS apps with business logic — self-order, patient check-in, directories, product catalogs — not just touchscreen content - Hardware peripheral integration via the TelemetryOS SDK (RFID, barcode scanners, thermal printers, cameras, RS-232 serial) in JavaScript, no native drivers - One console with your signage — the self-order kiosk, the menu boards, and the promo screens run on the same platform, content pipeline, and fleet monitoring - Offline-first architecture — application code and content cache locally, kiosks keep operating through network outages and sync when connectivity returns - Git-to-kiosk deployment with staged rollouts and one-click rollback - Real-time connectivity — TelemetryOS enables applications to connect to POS, appointment scheduling, inventory, loyalty, and payment systems via REST APIs and webhooks - iOS app for QR code kiosk pairing, on-site device health, and pocket overrides - AI Assist in the Page Layout Engine drafts attract loops and touch layouts from a prompt - Edge AI on Node Max (additive): on-device LLM concierge kiosks and computer vision — private by design, no cloud round-trip, no PII stored - Session analytics and proof-of-play with timestamped logs and CSV exports - Emergency overrides — instant, scheduled, or CAP-triggered — preempt the kiosk experience - Secure kiosk mode: session timeouts, idle resets, lockscreen enforcement, application sandboxing, and tamper-resistant lockdown built into TelemetryOS Edge - Enterprise security: SAML SSO, SCIM provisioning, RBAC, audit logging, SOC 2 Type I and GDPR compliance, and data residency across US, EU, UK, Canada, and Asia-Pacific --- ## IoT Integration URL: https://telemetryos.com/product/iot-integration MQTT, RS-485 serial, USB peripherals, Docker, and hardware integration. TelemetryOS bridges OT and IT — connecting industrial equipment, sensors, cameras, and actuators to displays that visualize, control, and respond in real time. ### SDK-Powered IoT Integration MQTT, RS-232/RS-485 serial, USB devices, and cameras are all accessible from your JavaScript application via the TelemetryOS SDK. No native drivers, no custom integration layer. Node Pro and Node Max run Docker containers alongside the screen application — protocol bridges, local data processing, and custom integration services live on the device instead of a separate industrial PC. ### Hardware Integration Details - **MQTT broker integration, zero configuration** — Publish and subscribe to any MQTT broker on your local network. Read sensors, send commands to actuators, and let a threshold crossing trigger an alert overlay on every screen in the zone — no middleware required. - **RS-232 & RS-485 for PLCs and legacy equipment** — TelemetryOS SDK exposes serial communication via JavaScript. Connect to PLCs, SCADA systems, and legacy machines without custom driver development. - **WebUSB, cameras, and Bluetooth built in** — USB cameras stream directly into your application via browser APIs. Barcode scanners, RFID readers, and USB sensors connect through WebUSB. Bluetooth peripherals pair natively. One Node device connects to multiple I/O sources simultaneously. - **Local processing — data stays on-premises** — Run data processing, protocol bridges, and inference in Docker containers on the device. Sensitive OT data stays on your network unless you explicitly push it to the cloud. ### Enterprise OT/IT Integration - WPA enterprise Wi-Fi, 802.1x, static IP, and proxy server configuration - Git-to-screen CI/CD — push a commit and integration code builds and deploys to every assigned screen, with staged rollouts and one-click rollback - Watchdog crash recovery and atomic OS updates — no maintenance windows - Cloud + Edge Hybrid Architecture — process time-sensitive data locally, sync aggregated analytics to cloud ### Real-World Industrial Applications - **Manufacturing Production Dashboards** — Connect to PLCs, SCADA systems, and MES via MQTT or serial. Display live output, downtime, quality metrics, and shift targets — updated every second, visualized in React. - **Sensor-Triggered Alerts & Overrides** — A temperature spike, pressure fault, or stopped conveyor can trigger a priority override that preempts content on every screen in the zone — the same override system that handles CAP-triggered emergency alerts fleet-wide. - **Quality Control Terminals** — Build barcode-scanning QA terminals that log inspections, flag defects, and push results to central quality systems. - **Retail & Venue Intelligence** — Motion sensors, RFID shelf readers, and proximity data drive screens that respond to what's actually happening in the space. ### Edge AI: Vision Pipelines at the Sensor's Edge The same camera APIs that stream video into your application feed on-device vision models on Node Max — visual inspection, defect detection, and queue measurement that run next to the conveyor with millisecond latency and no cloud round-trip. Camera footage and OT data never leave the site; inference runs in a hardened on-device environment, which is what makes vision deployable on regulated and air-gapped floors. Related: Real-Time Operations Dashboards and AI Visual Inspection use cases, and Node Pro hardware. --- ## Security & Compliance URL: https://telemetryos.com/product/security-compliance SOC 2 Type I and GDPR compliant, with SAML SSO, SCIM provisioning, role-based access control, audit logging, and a locked-down appliance OS — the security posture IT teams require before a screen platform touches their network. ### Compliance Posture - **SOC 2 Type I** — A verified, independently examined compliance program covering security policies, vulnerability management, incident response, and personnel training - **GDPR** — Privacy-respecting defaults with tenant-scoped isolation, plus data export and deletion workflows for subject access and erasure obligations - **Five Data Regions** — Choose where account data lives: United States, European Union, United Kingdom, Canada, or Asia-Pacific - Suitable for healthcare, financial services, and government deployments ### Identity & Access - **SAML SSO** — Single sign-on with Active Directory, Okta, and Azure AD; your identity provider stays the source of truth - **SCIM Provisioning** — Automated user provisioning and deprovisioning from your directory - **Role-Based Access Control** — Granular, customizable roles separating content managers, developers, and operations teams - **Audit Logging** — Every console action logged with who, what, and when ### Hardened at the Edge - **Locked-Down Appliance OS** — Purpose-built operating system with minimal attack surface; no exposed desktop, no drift from a known-good state - **Application Sandboxing** — Every screen application executes in containerized isolation - **End-to-End Encryption** — HTTPS/TLS for all user, API, and device traffic, with certificate-based device identity and network segmentation in a zero-trust architecture - **Automatic Updates with Rollback** — Over-the-air security patches apply atomically and roll back automatically if anything fails ### Edge AI, Private by Design - On-device LLMs and computer vision run directly on Node Max — camera feeds and conversations are processed on-premises - No cloud round-trip and no PII stored; inference runs in a hardened on-device environment - Keeping data on-site is what makes AI deployable in healthcare, gaming, and government settings ### Enterprise Governance Capabilities - **API Token Management** — Scoped API access with token rotation and instant revocation - **Data Export & Deletion** — Self-service workflows for GDPR and internal data-retention policies - **Proof-of-Play Exports** — Timestamped playback logs and CSV exports for advertisers, regulators, and audits - **Tenant Isolation** — Privacy-first defaults with tenant-scoped access isolation - **Zero-Trust Networking** — Certificates, segmentation, and least-privilege access control between devices, cloud, and users - **Security Specialists** — Security engineers for deployment reviews, architecture consultation, and questionnaire support --- ## Blocks URL: https://telemetryos.com/product/blocks Pre-built application blocks and components for screen development. Blocks are reusable, composable building blocks that accelerate screen application development on TelemetryOS. --- ## Getting Started URL: https://telemetryos.com/getting-started Onboarding guide and quick start resources for new TelemetryOS customers. Covers initial device setup, connecting to TelemetryOS Studio, deploying your first content or application, and configuring fleet management. --- ## Pricing URL: https://telemetryos.com/pricing TelemetryOS pricing has two dimensions: a per-device fee and an account plan. **Device Fee:** Every Node device includes 1 year of service with purchase. After the first year, the device fee renews at $99/year per device. The device fee covers cloud fleet management, over-the-air OS and security updates, device telemetry and health monitoring, remote diagnostics, and CDN-backed content delivery. Every device includes a 1-year hardware warranty. Premium and Enterprise account plans extend the warranty up to 5 years from activation (requires continuous subscription). **Account Plans:** - **Standard** — Free. Basic remote management, 10GB storage, 100GB bandwidth. - **Premium** — $2,995/year. API access, GitHub CI/CD, webhooks, 1TB storage, 5TB bandwidth, AI anomaly detection, templates, role-based permissions. Extended hardware warranty (up to 5 years). - **Enterprise** — Contact sales. Everything in Premium plus SAML/SCIM SSO, audit logging, dedicated CSM, SOC 2 report, 10TB storage, 50TB bandwidth, custom MSA. --- ## Demo URL: https://telemetryos.com/demo Book a live product demonstration with TelemetryOS product experts. --- ## Industries ### Corporate Communications URL: https://telemetryos.com/industries/corporate-comms Lobby screens, KPI wallboards, and meeting-room displays that deliver one message to every office, on schedule. **One message, every office, on schedule** Workplace screens multiply fast: a town-hall display in the lobby, KPI wallboards above the operations floor, room schedules outside every conference room, and breakroom screens nobody remembers installing. When each runs on its own system — or worse, a laptop and an HDMI cable — internal comms teams can't actually reach the workforce, and IT can't see which screens are even on. TelemetryOS consolidates the entire workplace estate. Corporate communications displays carry leadership messages, policy updates, and town-hall streams scheduled by daypart, office, and campaign from one console — so the Singapore office gets the all-hands replay at a civilized hour and a compliance deadline hits every region on its own clock. Room schedule displays and wayfinding directories in larger campuses get people to the right space without a front-desk escort. Every device reports health, uptime, and proof of playback to one dashboard, which turns "is the lobby screen working in Denver?" from a Slack question into a console query. And because TelemetryOS devices play content and applications locally, an office network blip never blanks the lobby in front of a visiting customer. **Dashboards that summarize themselves — privately** The most valuable workplace screens show live data: real-time dashboards pulling from BI tools, ticketing queues, sales pipelines, and operations systems. TelemetryOS enables applications to connect to any REST API, so a wallboard reflects the state of the business as it changes — not a screenshot from last Tuesday. TelemetryOS Edge AI takes those dashboards a step further. Running on Node Max, an on-device language model can summarize live ops data into plain language right on the wallboard — "ticket backlog up 18% since 9am, driven by the EU region" — without your internal metrics ever transiting a third-party cloud LLM. For companies whose security teams would never approve streaming revenue figures and incident data to an external AI service, on-device inference is what makes AI-assisted dashboards deployable at all. Private by design, with no cloud round-trip. As with any fleet, you match hardware to the job: Node Mini for meeting-room schedules and breakroom screens, Node Pro for lobby displays and multi-screen wallboards, and Node Max where on-device intelligence adds real value. One fleet, one console, one content pipeline. **Built for IT, loved by comms** Workplace signage only works when both owners are happy: communications teams need to publish without filing tickets, and IT needs a fleet they can actually operate. TelemetryOS applications are built once with the React SDK — internal tools teams treat a dashboard like any other React project — and ship through a git-to-screen pipeline, so a merged pull request updates every office within seconds. Per-region content and per-office branding are configuration, not separate installs. IT manages the whole estate from one console with fleet health, remote diagnostics, and proof of play across every office — and the same platform runs kiosks, signage, and sensors, so the visitor check-in kiosk in the lobby isn't yet another vendor. See pricing for how device licensing scales from one headquarters to a global office footprint. Q: Can we schedule different content for different offices and time zones? A: Yes. Content is scheduled by daypart, location, or campaign from one console, so the Berlin office sees its town-hall replay at 9am local while New York runs quarterly results. Changes publish to every targeted screen in seconds. Q: Can wallboards show live data from our internal systems? A: TelemetryOS enables applications to connect to any REST API, so dashboards can read from your BI platform, ticketing system, sales CRM, or operations tooling and update in real time — your data sources, your access controls. Q: Is it safe to put internal metrics on screens managed by a cloud platform? A: Dashboard applications render on the device, and with TelemetryOS Edge AI, any AI-driven summarization of live ops data also runs locally — internal metrics don't transit a third-party LLM. TelemetryOS is GDPR compliant and SOC 2 Type I certified. Q: What happens to office screens when the network drops? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so lobby screens and wallboards never go blank during an outage. Everything syncs automatically when connectivity returns. Q: What hardware do we deploy across offices? A: The TelemetryOS Node family. Node Mini drives meeting-room and breakroom displays economically, Node Pro powers lobby screens and multi-display wallboards, and Node Max adds on-device AI for live data summarization — all managed from one console. --- ### Education URL: https://telemetryos.com/industries/education Event boards, room schedules, wayfinding, and instant emergency alerts — one communication layer across every building on campus. **One communication layer across campus** A campus is dozens of buildings full of screens that grew up separately: event boards in the commons, room schedules outside lecture halls, dining menus, shuttle trackers at stops, and donor recognition walls in the lobby. Most institutions run them on a patchwork of departmental systems — which means no single place to publish, no single view of what's actually working, and no way to reach every screen when it matters. TelemetryOS turns that patchwork into one layer. Campus digital signage publishes events, announcements, and dining menus by building, department, or campus-wide schedule from one console. Room schedule displays read live bookings, shuttle boards show real arrival times, and wayfinding directories get visiting families from the parking lot to the right office during orientation week. Every device reports health, uptime, and proof of playback to the same dashboard. The moment that justifies the whole system is the emergency. When something happens, an emergency alert override takes over every screen in every building in seconds — weather closures, lockdown instructions, evacuation routes — and because TelemetryOS devices play content locally, screens stay up and informative even if campus networks are degraded. When the all-clear comes, every screen returns to its schedule automatically. **A campus assistant that respects student privacy** Students and visitors increasingly expect to ask a screen a question and get an answer — where a building is, when the next shuttle leaves, how to reach the registrar. TelemetryOS Edge AI makes that practical for education: language models run entirely on the device, so a multilingual campus assistant on an interactive kiosk can answer in a student's own language without sending a single conversation to the cloud. No round-trip, no PII, no transcript of a 17-year-old's questions sitting in a third-party LLM provider's logs. That assistant runs on Node Max, the edge-AI tier of the Node hardware family, which executes language models and computer vision on the device itself. The same hardware can count foot traffic through a commons to inform space planning, or spot a crowd forming where one shouldn't be — with all footage staying on-site. For institutions serving minors, on-device is not a nice-to-have; it's the only architecture that fits the policy. Few campuses need AI everywhere. The common pattern is Node Mini on room schedules and menu boards, Node Pro on kiosks and large-format commons displays, and Node Max at the handful of high-traffic touchpoints where an assistant earns its keep. It's all one fleet, one console, one content pipeline. **Built for multi-building, multi-campus scale** Education deployments succeed on repeatability across buildings that were never built the same way. TelemetryOS applications are built once with the React SDK and deployed everywhere through a git-to-screen pipeline — a student developer or campus IT team pushes a change, and every screen across every building updates within seconds. Per-building content, per-department schedules, and per-campus branding are configuration, not separate installs. For university IT and the integrators who serve education, the entire estate — kiosks, signage, and sensors on one platform — is managed from one console with fleet health, remote diagnostics, and proof of play, so a screen failing in a building across campus is a ticket, not a walk. See pricing for how device licensing scales from a single building to a multi-campus system. Q: Can we push an emergency alert to every screen on campus at once? A: Yes. An emergency override takes over every targeted screen — commons boards, room schedules, kiosks, dorm displays — across every building in seconds, then returns each screen to its scheduled content when the all-clear is given. Q: Can screens pull live data like room bookings, events, and shuttle locations? A: TelemetryOS enables applications to connect to any REST API, so screens can read from your room booking system, events calendar, or shuttle GPS feed and reflect changes in real time — your data sources, your integration logic. Q: What happens to campus screens when the network goes down? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so a network outage never blanks an event board or kiosk. Everything syncs automatically when connectivity returns. Q: How does TelemetryOS handle student privacy with AI kiosks? A: With TelemetryOS Edge AI, the assistant runs entirely on the device — conversations never make a cloud round-trip and no PII is collected or transmitted. That's the right default for campuses serving minors and for institutions with strict student data policies. Q: What hardware fits a campus deployment? A: The TelemetryOS Node family. Node Mini drives room schedules and menu boards economically, Node Pro powers interactive kiosks and large commons displays, and Node Max adds on-device AI for multilingual campus assistants — all managed from one console. --- ### Healthcare URL: https://telemetryos.com/industries/healthcare Patient check-in, wayfinding, and facility-wide communication on one managed platform — with AI that keeps patient data inside the building. **One platform for every screen in the facility** A hospital or clinic network runs screens with very different jobs: check-in kiosks at the entrance, wayfinding directories in the atrium, queue boards in waiting rooms, education displays in exam rooms, and staff communication screens behind the scenes. Run them on separate systems and you get separate consoles, separate failure modes, and separate vendors to call when a screen goes dark. TelemetryOS consolidates all of it. Patient check-in kiosks shorten front-desk queues, wayfinding directories get visitors from parking garage to the right department without staff intervention, and queue boards keep waiting rooms calm with realistic expectations. Every device reports health, uptime, and proof of playback to one dashboard — so a dark screen is an alert in your console, not a complaint at the front desk. Resilience is non-negotiable in clinical environments. TelemetryOS devices play content and applications locally, so a network outage never blanks a check-in kiosk or queue board mid-clinic. And when something urgent happens, emergency override messaging takes over every targeted screen in seconds — code alerts, lockdown instructions, evacuation routes — then hands the screens back when the event clears. **AI that keeps PHI inside the building** Healthcare is exactly where cloud AI breaks down: in regulated jurisdictions, sending patient data to a cloud LLM is a compliance problem before it's a technology decision. TelemetryOS Edge AI takes a different path — language models and computer vision run entirely on the device, so a check-in assistant can answer questions, guide a patient through arrival, and translate on the spot without a single byte of patient data making a cloud round-trip. No PII leaves the facility, by design. That intelligence runs on Node Max, the edge-AI tier of the Node hardware family. The same device can run an on-screen assistant at the entrance and computer vision in the lobby — estimating queue length to staff the front desk, or detecting a fall in a waiting area — while all footage stays on-site. For chairside patient education, an on-device assistant can walk a patient through a procedure in their own language while the clinician finishes charting. You don't need AI on every screen. Most facilities start with Node Mini on queue boards and waiting room displays, Node Pro on kiosks and directories, and add Node Max where on-device intelligence earns its place. One fleet, one console, one content pipeline. **Built for health-system scale** Multi-facility rollouts live or die on repeatability. TelemetryOS applications are built once with the React SDK and deployed to every campus through a git-to-screen pipeline — push a change, and every facility updates within seconds. Per-department content, per-building wayfinding data, and per-clinic check-in flows are configuration, not custom installs. TelemetryOS is GDPR compliant and SOC 2 Type I certified, with the architecture decisions — local playback, on-device AI — that healthcare IT teams actually ask about. For health systems and the integrators who serve them, that means a patient experience application becomes a product: build it once, deploy it across 5 or 500 sites, and manage the entire estate from one device management console with fleet health, remote diagnostics, and proof of play. See pricing for how device licensing scales with your footprint. Q: How does TelemetryOS keep patient data private at check-in kiosks? A: With TelemetryOS Edge AI, language models and computer vision run entirely on the device — patient interactions never make a cloud round-trip, and no PII leaves the facility. That matters in jurisdictions where sending patient data to cloud LLMs simply isn't an option. Q: Can check-in kiosks connect to our EHR or practice management system? A: TelemetryOS enables applications to connect to any REST API, so a check-in kiosk built on the platform can read appointments, verify identity, and update arrival status against your EHR or scheduling system — with your integration logic, your data governance. Q: What happens to waiting room screens and kiosks if the network goes down? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so an outage never blanks a queue board or check-in kiosk mid-clinic. Everything syncs automatically when connectivity returns. Q: Can we push emergency messaging to every screen at once? A: Yes. An emergency override takes over every targeted screen across one facility or an entire health system in seconds — code alerts, evacuation routes, lockdown instructions — then returns each screen to its scheduled content when cleared. Q: What hardware should we deploy across a hospital? A: The TelemetryOS Node family. Node Mini handles waiting room and queue displays economically, Node Pro drives interactive check-in kiosks and wayfinding directories, and Node Max adds on-device AI for assistants and computer vision — all managed from one console. --- ### Hospitality & Venues URL: https://telemetryos.com/industries/hospitality-venues Concierge kiosks, event directories, and venue floor screens that carry the guest experience from lobby to venue floor. **Every guest touchpoint, one managed fleet** A hotel, casino, or convention property is a screen network whether anyone planned it that way or not: concierge kiosks in the lobby, event directories outside ballrooms, restaurant menus and promotions, wayfinding directories in the corridors, and floor screens across the gaming or event space. Run them on separate systems and the guest experience fragments — the directory says one thing, the kiosk says another, and nobody can change either without a vendor call. TelemetryOS runs all of it as one fleet. Event directories pull tonight's schedule from your event management system, promotions switch by daypart and venue zone — happy hour graphics roll out across the property at 4pm and roll back at 7pm — and casino and venue displays run high-impact video across the floor from the same console. Every device reports health, uptime, and proof of playback to one dashboard, so a dark screen outside the ballroom is an alert, not a complaint from an event planner. Hospitality runs on uptime through the worst moments. TelemetryOS devices play content and applications locally, so a connectivity drop during a sold-out event never blanks the directories or the floor — screens keep serving guests and sync automatically when the network returns. **A concierge that answers on the device** The front desk can't be everywhere, and guests ask the same hundred questions at all hours: where's the spa, what time does the restaurant close, how do I get to Ballroom C. AI concierge kiosks built on TelemetryOS Edge AI answer in the guest's own language, around the clock — and because the language model runs entirely on the device, guest conversations never make a cloud round-trip. No PII leaves the property, and the concierge keeps working even when the internet doesn't. That privacy posture is decisive in gaming. Casino operators face strict compliance rules about where patron and surveillance data can go, which makes most cloud AI undeployable on the floor. Node Max, the edge-AI tier of the Node hardware family, runs both language models and computer vision on the device itself — so a property can add AI-driven experiences and floor analytics while every conversation and every frame of footage stays on-site. Hardware follows the touchpoint: Node Mini for event directories and menu screens, Node Pro for interactive kiosks and video-heavy floor displays, Node Max where the AI concierge and vision use cases pay for it. One fleet, one console, one content pipeline from lobby to venue floor. **Built for portfolios, not just properties** Hospitality groups and the integrators who serve them need experiences that repeat across properties without rebuilding for each one. TelemetryOS applications are built once with the React SDK and shipped through a git-to-screen pipeline — a concierge application or event directory updates across every property within seconds of a push. Per-property branding, local restaurant data, and venue-specific layouts are configuration, not custom installs. The entire portfolio — kiosks, signage, and sensors on one platform — is managed from one console with fleet health, remote diagnostics, and proof of play, so operations teams see every screen on every property without leaving their desk. See pricing for how device licensing scales from a boutique hotel to a resort portfolio. Q: Does the AI concierge send guest conversations to the cloud? A: No. With TelemetryOS Edge AI, the language model runs entirely on the device — guest conversations never make a cloud round-trip, no PII is transmitted, and the concierge keeps answering even if the property's internet goes down. Q: Can kiosks and displays connect to our PMS, POS, or event management system? A: TelemetryOS enables applications to connect to any REST API, so a concierge kiosk can read tonight's events, restaurant availability, or loyalty offers from your property systems — with your integration logic and your data governance. Q: What happens to venue screens when connectivity drops? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so an outage never blanks an event directory or casino floor screen mid-shift. Everything syncs automatically when connectivity returns. Q: Why does on-device AI matter for casino and gaming properties? A: Gaming operators face strict rules about where player and surveillance data can go. TelemetryOS Edge AI runs language models and computer vision on the device itself, so AI-driven experiences on the floor work without patron data leaving the property — a deployable architecture where cloud AI often isn't. Q: What hardware runs a full property? A: The TelemetryOS Node family. Node Mini drives event directories and menu screens economically, Node Pro powers interactive kiosks and video-heavy floor displays, and Node Max adds on-device AI for concierge and vision use cases — all managed from one console. --- ### Industrial & Manufacturing URL: https://telemetryos.com/industries/industrial-manufacturing Production wallboards, andon displays, and safety screens that put operations data on the floor in real time — with AI inspection that runs right at the line. **Operations data on the floor, in real time** A plant runs on numbers — takt time, OEE, scrap rate, units to target — but those numbers too often live in an MES dashboard nobody on the floor can see. Printed metrics from yesterday's shift don't change behavior. A real-time production wallboard over the line does. TelemetryOS turns floor screens into live operational displays. Applications subscribe to your data over MQTT, serial, and sensor I/O, so an andon board flips state the moment a line stops, a safety display counts hours since the last recordable, and a target board updates with every unit scanned. A sensor crossing a threshold can trigger an alert overlay on every screen in the zone — no operator intervention required. Plants are also hard environments for connected devices, which is why local playback matters. TelemetryOS devices cache applications and content on the device, so a network drop in the middle of a shift never blanks a board. When the connection returns, everything syncs automatically — and your team sees fleet health for every screen, in every facility, from one console. **AI inspection that never leaves the building** Visual inspection is where edge AI earns its place on the line. With TelemetryOS Edge AI, cameras run defect-detection models directly on the device — analyzing parts at line speed with millisecond latency, flagging anomalies to the adjacent screen, and logging results locally. There's no cloud round-trip to add lag, and no footage of your process or your people leaving the site. That inference runs on Node Max, the edge-AI tier of the Node hardware family, which executes computer vision and on-device language models as a self-contained appliance at the line. The same unit that scores parts can drive the inspection display beside it, correlate defect spikes with sensor data arriving over MQTT, and surface the trend on the supervisor's wallboard — all on one platform. Privacy by design is what makes this deployable in regulated and IP-sensitive environments. Nothing identifiable is captured or transmitted, models run where the cameras are, and TelemetryOS is GDPR compliant and SOC 2 Type I certified. You can start with one inspection cell on Node Max while Node Mini and Node Pro handle the wallboards, and scale from there — it's all one fleet. **One platform from the line to the break room** The screens that show line metrics can also carry plant communications — shift schedules, safety campaigns, recognition, and policy updates — scheduled by daypart, zone, or facility from the same console. One platform replaces the patchwork of consumer TVs, USB sticks, and single-purpose andon controllers that plants accumulate over time. For integrators and plant IT, everything is built once with the React SDK and rolled out through a git-to-screen pipeline: push a change, and every facility updates within seconds, with remote diagnostics and proof-of-play to verify it. See pricing for how device licensing scales across plants. Q: Can TelemetryOS display live data from our PLCs and sensors? A: Yes. TelemetryOS enables applications to connect to MQTT brokers, serial devices, and sensor I/O, so a wallboard can subscribe to line telemetry and update the moment a value changes. The same application can also read from REST APIs exposed by your MES or historian. Q: What happens to the boards if the plant network goes down? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so a network interruption never blanks an andon board or safety display mid-shift. Updates sync automatically when connectivity returns. Q: How does AI visual inspection work without sending footage to the cloud? A: Defect-detection models run entirely on the device with TelemetryOS Edge AI on Node Max. Cameras are analyzed at the line with millisecond latency, results are flagged locally, and footage never leaves the site — no cloud round-trip, no PII exposure. Q: Can one console manage screens across multiple plants? A: Yes. Fleet health, proof-of-play, and remote diagnostics for every device — across every facility — live in one console. IT can verify a board in a remote plant is online and showing the right content without sending anyone to the floor. Q: What hardware should we deploy on the floor? A: The TelemetryOS Node family. Node Mini handles single wallboards economically, Node Pro drives multi-screen dashboards and interactive stations, and Node Max adds on-device AI for visual inspection and computer vision — all managed from the same console. --- ### Quick Service Restaurants URL: https://telemetryos.com/industries/qsr Menu boards, drive-throughs, kiosks, and kitchen screens that run as one managed fleet — and get smarter with AI that runs right on the device. **One platform for every screen in the restaurant** A quick-service restaurant is full of screens doing different jobs: menu boards behind the counter, a drive-through lane outside, self-order kiosks by the door, and kitchen displays in the back. Most operators run them on different systems from different vendors — which means different consoles, different failure modes, and different invoices. TelemetryOS consolidates all of it. Dynamic menu boards switch by daypart and campaign, self-order kiosks run beside scheduled content on the same console, and every device reports health, uptime, and proof of playback to one dashboard. When a board goes dark in one store, it's an alert in your console — not a customer complaint. Because TelemetryOS devices play content locally, service doesn't stop when the network does. Boards and kiosks keep running from the device through an outage and sync automatically when the connection returns — which matters at 12:05pm on a Saturday. **A drive-through that gets smarter on the device** The next wave of QSR technology is AI at the edge — and it has to respect privacy to be deployable. With TelemetryOS Edge AI, the drive-through board recognizes a returning vehicle and recalls past orders entirely on the device. No faces, no PII, no cloud round-trip — just a tailored greeting and order suggestions that lift average ticket size. That intelligence runs on Node Max, the edge-AI tier of the Node hardware family, which executes language models and computer vision on the device itself. The same hardware can watch queue length and trigger an extra register callout, or flag a stocked-out item from a camera feed — while all footage stays on-site. You don't need AI everywhere on day one. Most operators start with Node Mini on menu boards and Node Pro on kiosks, then add Node Max where the AI use case pays for it. It's all one fleet, one console, one content pipeline. **Built for franchise scale** QSR rollouts live or die on repeatability. TelemetryOS applications are built once with the React SDK and deployed to every store through a git-to-screen pipeline — push a change, and every location updates within seconds. Regional pricing, localized menus, and per-store overrides are configuration, not custom installs. For franchisors and the integrators who serve them, that means a menu application becomes a product: build it once, deploy it across 50 or 5,000 stores, and manage the entire estate from TelemetryOS Studio. See pricing for how device licensing scales with your footprint. Q: Can TelemetryOS update menus across hundreds of locations at once? A: Yes. Menus are scheduled by daypart, store, or campaign from one console, and changes publish to every targeted screen in seconds. A limited-time offer can go live across the whole network at 11am and disappear at 2pm without anyone touching a screen. Q: What happens to menu boards and kiosks when the network goes down? A: They keep running. TelemetryOS devices cache content and applications locally and play from the device, so an outage never blanks a board mid-service. Updates sync automatically when connectivity returns. Q: How does the drive-through AI work without storing customer data? A: Vehicle recognition and order recall run entirely on the device using TelemetryOS Edge AI — no faces, no PII, and no cloud round-trip. The board greets a returning vehicle with relevant suggestions while the data never leaves the restaurant. Q: Can menu boards pull live prices and sold-out states from our POS? A: TelemetryOS enables applications to connect to any REST API, so menu boards can read items, prices, and availability from your POS or menu management platform and reflect changes in real time. Q: What hardware runs all of this? A: The TelemetryOS Node family. Node Mini handles single menu boards economically, Node Pro drives multi-screen counters and kiosks, and Node Max adds on-device AI for drive-through intelligence and computer vision — all managed from the same console. --- ### Retail & Kiosks URL: https://telemetryos.com/industries/retail-kiosks Programmable store walls, shelf-edge media, and self-service kiosks that run as one managed fleet — with on-device AI that watches the shelf while the glass keeps selling. **Every screen in the store, one programmable fleet** Retail screens have multiplied — campaign walls behind checkout, shelf-edge strips in the aisle, self-service kiosks at the entrance, cooler doors in the grocery section — and most chains run them on a patchwork of vendor systems that can't share content, scheduling, or monitoring. Every new screen type becomes another console and another contract. TelemetryOS runs all of it as one fleet. Campaigns are scheduled by daypart, store, or promotion from a single console: the breakfast push on cooler doors in the morning, the weekend offer on the checkout wall Friday through Sunday, localized pricing per region — all configuration, not site visits. Kiosks run interactive applications beside scheduled content on the same devices and the same pipeline. And because TelemetryOS devices play content locally, trading doesn't stop when the network does. A connectivity drop never blanks a wall or a kiosk mid-shift; screens keep running from the device and sync automatically when the connection returns. Fleet health, remote diagnostics, and proof-of-play for every store roll up to one dashboard. **Retail media and AI that respect the shopper** In-store screens are becoming sellable inventory. A retail media network on TelemetryOS gives brand partners targeted placement by store, daypart, and campaign — with per-screen proof-of-play that verifies every impression you bill for. Smart cooler screens turn the highest-dwell fixture in grocery into dynamic media that merchandises what's actually behind the glass. The intelligence layer runs on the device. With TelemetryOS Edge AI on Node Max, a camera over the shelf flags an out-of-stock facing to the store team while the glass keeps selling, and anonymous computer vision measures engagement — dwell, glances, traffic — with no faces stored, no PII, and no cloud round-trip. On-device language models can even power a product-finder kiosk that answers shopper questions locally. Privacy by design is what makes this deployable at retail scale: footage never leaves the store, nothing identifiable is retained, and TelemetryOS is GDPR compliant and SOC 2 Type I certified. Most chains start with Node Mini on shelf-edge and cooler screens and Node Pro on walls and kiosks, then add Node Max where the AI use case pays for itself. **Built for chain-scale rollouts** Retail deployments live or die on repeatability. TelemetryOS applications are built once with the React SDK and rolled out through a git-to-screen pipeline — push a change, and every store updates within seconds. TelemetryOS enables applications to connect to your commerce APIs, so prices, availability, and promotions on screen stay in lockstep with the systems of record. For integrators and retail media operators, that means a screen network becomes a product: build the application once, deploy it across 50 or 5,000 stores, and manage the entire estate from one console. See pricing for how device licensing scales with your footprint. Q: Can TelemetryOS run campaigns across hundreds of stores at once? A: Yes. Campaigns are scheduled by daypart, store, or campaign from one console, and changes publish to every targeted screen in seconds. A weekend promotion can go live across the whole estate Friday morning and come down Sunday night without anyone touching a screen. Q: How does proof-of-play work for retail media? A: Every device reports playback to the console, so you can verify exactly which creative ran on which screen, in which store, and when. That verified record is what brand partners and media buyers need to pay against — and it comes from the same console that monitors fleet health. Q: What happens to store screens when the network goes down? A: They keep selling. TelemetryOS devices cache content and applications locally and play from the device, so an outage never blanks a campaign wall or kiosk mid-trading. Updates sync automatically when connectivity returns. Q: How does on-device AI work without capturing shopper data? A: Computer vision runs entirely on the device with TelemetryOS Edge AI on Node Max — no faces stored, no PII, no cloud round-trip. Cameras can flag an out-of-stock shelf or count anonymous engagement while all footage stays in the store. Q: What hardware runs all of this? A: The TelemetryOS Node family. Node Mini handles shelf-edge and cooler screens economically, Node Pro drives video walls and self-service kiosks, and Node Max adds on-device AI for shelf monitoring and engagement analytics — all managed from the same console. --- ### Transportation & Public Spaces URL: https://telemetryos.com/industries/transportation-public-spaces Departure boards, wayfinding directories, and service alerts that stay accurate through outages — information travelers can trust, on screens you can manage from anywhere. **Information travelers can trust** In a station or terminal, a wrong screen is worse than no screen. Travelers make real decisions on what the board says — which platform, which gate, how long — and the moment displays go dark or stale, staff absorb every question the screens stopped answering. Reliability isn't a feature here; it's the whole product. TelemetryOS is built for that standard. Departure boards read live arrivals, departures, and delays from your scheduling feeds, and because every device caches its application and data locally, boards stay live through network outages — showing the last known schedule instead of a blank panel, then syncing the moment connectivity returns. When service is disrupted, an emergency alert override can take over targeted screens — one platform, one terminal, or the entire network — in seconds from one console. Operationally, a transit estate is hundreds of screens spread across stations you can't easily visit. Fleet health, proof-of-play, and remote diagnostics for every device roll up to a single dashboard, so a failed board in an outlying station is an alert in the console, not a passenger complaint on social media. **Wayfinding and assistance that meet travelers where they are** Static maps don't answer the question a traveler actually has. Interactive wayfinding directories on TelemetryOS let people search a destination, see the route from where they're standing, and carry it with them via QR hand-off to their phone — no app install, no account. The same screens carry scheduled content by daypart and location: commuter information at rush hour, retail and events programming off-peak. TelemetryOS Edge AI takes assistance further without taking data anywhere. On Node Max, on-device language models answer traveler questions in multiple languages right at the kiosk — directions, connections, accessibility routes — with no cloud round-trip and nothing retained. Vision models running on the same hardware gauge crowd and queue levels anonymously, so operations dashboards can flag a building platform crush or a security queue blowing out before it becomes an incident. Privacy by design is what makes AI viable in public space: no faces stored, no PII, footage analyzed and discarded on the device — and TelemetryOS is GDPR compliant and SOC 2 Type I certified. Agencies typically run Node Mini on departure boards, Node Pro on directories and video walls, and add Node Max where assistance and crowd awareness justify it — one fleet throughout. **Built for networks, not single stations** Transit screens scale by the line, not the screen. TelemetryOS applications are built once with the React SDK and deployed across every station through a git-to-screen pipeline — push a change, and the whole network updates within seconds, with per-station configuration handling local feeds, languages, and layouts. TelemetryOS enables applications to connect to scheduling systems, AVL feeds, and sensor inputs, so screens, kiosks, and sensors run on one platform. For agencies and the integrators who serve them, that means a departure board becomes a product you operate, not a fleet of one-off installs you maintain. See pricing for how device licensing scales across stations and terminals. Q: Can TelemetryOS show live departures from our scheduling system? A: Yes. TelemetryOS enables applications to connect to any REST API or data feed, so departure boards can read arrivals, departures, platforms, and delays from your scheduling or AVL system and update in real time across every screen. Q: What happens to departure boards when the network goes down? A: They stay live. TelemetryOS devices cache content and applications locally and play from the device, so boards keep showing the last known schedule through an outage instead of going dark — and sync automatically the moment connectivity returns. Q: Can we override every screen with a service alert at once? A: Yes. An alert can take over targeted screens — a platform, a terminal, or the whole network — in seconds from one console, then release back to normal content when the disruption clears. Scheduling by daypart, location, and campaign handles the routine programming. Q: How does on-device AI help travelers without compromising privacy? A: With TelemetryOS Edge AI on Node Max, language models answer traveler questions in multiple languages directly on the kiosk, and computer vision gauges crowd and queue levels anonymously. No faces stored, no PII, no cloud round-trip — footage and conversations never leave the station. Q: What hardware suits stations and terminals? A: The TelemetryOS Node family. Node Mini drives individual departure boards economically, Node Pro powers video walls and interactive directories, and Node Max adds on-device AI for multilingual assistance and crowd awareness — all managed from the same console. --- ## Use Cases ### AI Concierge Kiosks URL: https://telemetryos.com/usecases/ai-concierge-kiosks A concierge that answers on the device. A screen runs an assistant locally, answering naturally and working even when the network can't — a hotel concierge that never sends the conversation to the cloud. **A concierge that answers on the device** Guests don't want to download an app or wait in line at the front desk to ask where to eat. A concierge kiosk answers those questions instantly — but most conversational kiosks ship every utterance to a cloud service, which means latency, a hard dependency on the network, and guest conversations leaving the building. TelemetryOS Edge AI takes a different path: the assistant runs on the device. On-device language models answer naturally, in real time, without a cloud round-trip. A hotel concierge kiosk can recommend restaurants, explain checkout policies, and give directions with the conversation processed entirely on local hardware — no PII stored, nothing transmitted for inference. That architecture also makes the kiosk resilient. Because the model and the content both live on the device, the concierge keeps working when the network can't. A connectivity outage that would silence a cloud-dependent kiosk doesn't interrupt a guest mid-question; the device continues answering locally and syncs with the console when the connection returns. **Built for hospitality operators and integrators** A concierge kiosk is one application on a platform that runs them all. The same TelemetryOS deployment can drive lobby signage, wayfinding screens, and event boards alongside the kiosk — one console for content scheduling, device monitoring, and fleet management across every property. For integrators, the assistant itself is buildable, not a black box. Applications are written with a React SDK and deployed git-to-screen, and TelemetryOS enables applications to connect to property management systems, booking engines, or any REST API for live answers grounded in real data. Brand the experience per property, tune what the assistant knows per location, and roll updates across the fleet from one place — with the privacy story intact, because inference never leaves the device. Q: Does the AI concierge send guest conversations to the cloud? A: No. TelemetryOS Edge AI runs language models directly on the device, so the conversation is processed locally and never leaves the kiosk. There is no cloud round-trip and no PII stored — privacy is a property of the architecture, not a policy. Q: What happens if the kiosk loses its internet connection? A: The concierge keeps answering. Because the assistant runs on the device, it doesn't depend on a live connection to respond. TelemetryOS devices also cache all content locally, so the kiosk stays fully functional through an outage and syncs updates when connectivity returns. Q: Can the concierge answer questions specific to my property? A: Yes. The assistant is an application, so it can be grounded in your own content — amenities, hours, dining, local recommendations, house policies. TelemetryOS enables applications to connect to any REST API, so it can also read live data like restaurant availability or event schedules. Q: How do I manage concierge kiosks across multiple properties? A: From one console. TelemetryOS gives you fleet-wide device management, monitoring, and content scheduling, so you can update the assistant, push new property content, and verify every kiosk is healthy across all locations without site visits. Q: What hardware does an AI concierge kiosk require? A: A touchscreen kiosk paired with a TelemetryOS device with the compute for on-device inference, such as the Node Pro or Node Max. The device runs the assistant locally and is managed remotely from the TelemetryOS console. --- ### AI Visual Inspection URL: https://telemetryos.com/usecases/ai-visual-inspection A line that watches itself. Cameras run inspection models on the device and drive the result to the floor screen instantly — flagging a defect in milliseconds, with footage staying on-site. **A line that watches itself** Visual inspection is a job humans do inconsistently and cloud AI does too slowly. A defect that takes a 300-millisecond round-trip to score has already moved down the line, and streaming production video off-site is a non-starter for most manufacturers — the footage shows the process, and the process is the IP. TelemetryOS Edge AI closes the loop on the device. Cameras at the line run inspection models locally, scoring each frame in milliseconds and driving the result to the floor screen instantly — a flagged defect appears at the station while the part is still in reach. Footage stays on-site, inference never leaves the device, and the inspection loop has no cloud dependency to fail. Because the screen and the model run on the same platform, the result isn't buried in a dashboard somewhere. The display at the line shows the live pass/fail state, the catch that just happened, and the shift's defect trend — and because TelemetryOS devices cache and play content locally, both inspection and display keep running through a plant network outage, syncing results when the connection returns. **Built for manufacturers and integrators** An inspection station is one application on a platform built to run the whole floor. The same TelemetryOS deployment drives andon boards, safety signage, and production dashboards — one console for fleet device management, monitoring, and content across every line and every plant, so a camera or screen that drops offline is an alert, not a quality gap discovered at audit. For integrators, the inspection logic is theirs to build. Applications are written with a React SDK and deployed git-to-screen, so a model update or a new defect class rolls out to every station from a git push. TelemetryOS enables applications to connect to MES, QMS, and historian systems over any REST API, so defect events flow into the quality record automatically — while the video that produced them never leaves the building. Q: Where does inspection inference actually run? A: On the device, at the line. TelemetryOS Edge AI runs computer vision models locally on hardware like the Node Pro or Node Max, so a frame is captured, scored, and acted on in milliseconds — without a round-trip to a cloud service in the inspection loop. Q: Does production footage leave the factory? A: No. Video is processed on the device and footage stays on-site, which matters when the line itself is proprietary. There's no cloud round-trip for inference and no PII stored — what leaves the site is what you choose to send, such as defect counts or alerts to your quality systems. Q: How do inspection results reach operators on the floor? A: The floor screen is the same platform. Inspection results drive TelemetryOS displays at the line instantly — a flagged defect, a live pass/fail rate, a station-level andon state — so operators see the catch in the moment it happens, not in a report the next morning. Q: Can inspection results feed my MES or quality management system? A: TelemetryOS enables applications to connect to any REST API, so an inspection application can push defect events, counts, and images you choose to retain into your MES, QMS, or historian, and pull work-order context back to display alongside live results. Q: What happens to inspection if the plant network goes down? A: The line keeps watching itself. Models run on the device and screens play locally cached content, so inspection and floor displays both continue through an outage. Results queue on the device and sync to the console and your systems when connectivity returns. --- ### Campus Digital Signage URL: https://telemetryos.com/usecases/campus-digital-signage Turn a campus into one communication layer. Manage signage the same way across every building — a commons board carrying events today and an emergency alert the moment it's needed. **Turn a campus into one communication layer** Campus screens tend to grow one building at a time. The library has one system, athletics has another, and the residence halls have whatever a student plugged in three years ago. The result is a patchwork no one can update quickly and no one can trust in an emergency. TelemetryOS replaces the patchwork with one platform. Every screen in every building is managed the same way from one console, with content scheduled by building, department, or audience. The commons board carries today's events, the science building shows seminar schedules, and the rec center runs its own programming — each updated by the team that owns it, all visible to central IT. The same layer that carries daily content carries the urgent kind. An emergency alert publishes to every screen on campus the moment it's needed, overriding scheduled content, then releases screens back to normal when it clears. And because TelemetryOS devices play content locally, a network problem in one building doesn't take its screens down — playback continues from the device, with updates syncing when the connection returns. **Built for distributed institutions** Campus signage rarely stops at announcement boards. The same platform runs cafeteria menus, room-booking displays outside classrooms, donor recognition walls, and the video board in the arena — one console, one content pipeline, one fleet for IT to monitor. For campus IT teams and the integrators who serve education, that consolidation is the point. Device health, proof of playback, and content schedules are visible across every building, so a dark screen in a far corner of campus is a dashboard alert, not a work order filed weeks later. And because TelemetryOS is an application platform, signage can go beyond posters: live event feeds from the campus calendar, transit departure boards, and dining menus driven by food-service data are applications built with a React SDK and deployed git-to-screen, not custom one-off installs. Q: Can I push an emergency alert to every screen on campus at once? A: Yes. An alert publishes from the TelemetryOS console to every screen immediately, overriding whatever is scheduled. When the alert clears, screens return to their normal programming automatically — no one has to walk building to building. Q: How do different departments manage their own screens? A: Screens are organized into groups, so student affairs can run the commons boards, athletics can run the arena screens, and each residence hall can manage its own — all in one console, with campus-wide content and alerts still controlled centrally. Q: Can signage pull events from our campus calendar automatically? A: TelemetryOS enables applications to connect to any REST API, so a signage application can read from your events calendar, room booking, or LMS systems and keep today's events on screen without anyone re-entering them. Q: What happens to campus screens if a building loses network? A: Screens keep playing. TelemetryOS devices cache content locally and continue playback from the device, so a switch failure in one building never blanks its boards. Pending updates sync when connectivity returns. Q: What hardware does campus digital signage require? A: Any commercial display paired with a TelemetryOS device. The Node Mini covers standard boards, the Node Pro handles interactive and high-resolution screens, and everything is managed remotely from the TelemetryOS console — useful when screens are spread across dozens of buildings. --- ### Casino & Venue Displays URL: https://telemetryos.com/usecases/casino-venue-displays Big screens, one fleet. Run ambitious display networks without splitting content, hardware, and monitoring across vendors — big-screen displays above the floor, one console. **Big screens, one fleet** Casinos and large venues run some of the most ambitious display networks anywhere: big-format screens above the floor, promo displays at every turn, menu boards in the restaurants, wayfinding at the entrances, dashboards in the back of house. Ambition usually arrives with fragmentation — one vendor for the spectacle screens, another for signage, a third for kiosks, and no single view of any of it. TelemetryOS runs the whole property as one fleet. Every screen type is an application on the same platform, managed from one console with one content pipeline. Promotions schedule by daypart and zone, a property-wide campaign publishes everywhere at once, and live content — jackpot tickers, event schedules, table availability — comes from apps that connect to the systems the venue already runs, since TelemetryOS enables applications to connect to any REST API. On a floor that never closes, screens can't depend on the network minute to minute. TelemetryOS devices cache content and play it locally, so the displays above the floor keep running through a network issue and resync when it clears. Hardware scales with the screen: Node Mini for standard displays, Node Pro for demanding content, Node Max for big-format output. **One console, no vendor seams** The operational cost of a fragmented network shows up at 2am, when a marquee screen is dark and three vendors each say it isn't theirs. With one fleet on TelemetryOS, the console shows device health, playback status, and proof-of-play for every screen on the property — the dark screen is an alert with diagnostics, and most fixes happen remotely. Proof-of-play matters beyond uptime: promotions, sponsor content, and entertainment partners all want evidence of what ran where and when, and the console provides it across the whole network. For venue operators and the integrators who build for them, consolidation is the unlock — new screens, new zones, and new interactive experiences are deployments on a platform already in place, not another vendor added to the pile. Q: Can one platform really run every screen type in a venue? A: Yes. On TelemetryOS, screens, kiosks, and sensors are applications on one platform — the big-format displays above the floor, promo screens at the cage, restaurant menu boards, wayfinding kiosks, and back-of-house dashboards all run from the same console with the same content pipeline. Q: How do we schedule different content across a 24/7 venue? A: Content is scheduled by daypart, zone, or campaign from the TelemetryOS console. Breakfast promos in the café, afternoon entertainment listings on the concourse, and headliner content above the floor at night each publish to the right screens automatically — and a property-wide takeover is one change, not fifty. Q: What happens to floor displays if the network has an issue? A: Screens keep playing. TelemetryOS devices cache content and play it locally, so a network problem never blanks the displays above the floor. Devices resync automatically when connectivity returns, and the console shows exactly which screens are healthy. Q: Can displays pull live data like jackpots, events, or table status? A: TelemetryOS enables applications to connect to any REST API, so display apps can read from your casino management system, event calendar, or booking platform and render live jackpot tickers, event schedules, and promotions that update themselves. Q: What hardware drives large-format venue displays? A: TelemetryOS devices scale with the screen — Node Mini for standard displays, Node Pro for demanding content, and Node Max for big-format and video-wall-class output. Every device is monitored and managed remotely from the TelemetryOS console. --- ### Chairside Patient Education URL: https://telemetryos.com/usecases/chairside-patient-education Explain care right at the chairside. A custom app an integrator builds once and resells to every practice — a 3D anatomy screen a physician rotates to explain a procedure. **Explain care right at the chairside** The most important conversation in healthcare happens at the chairside, and most of it is spoken. A clinician describes a procedure, a patient nods, and half the detail is gone by the parking lot. A screen at the point of care changes that: a 3D anatomy model the physician rotates while explaining, a treatment plan stepped through frame by frame, a before-and-after the patient can actually see. TelemetryOS makes that screen an application, not a fixed appliance. Integrators build a chairside education app once with the React SDK — anatomy viewers, procedure explainers, consent walkthroughs — and deploy it git-to-screen to every practice they serve. One codebase becomes a product an integrator resells across dental groups, dermatology clinics, orthopedic offices, and veterinary practices, with updates shipping to the whole installed base at once. The same screen earns its keep between consultations. Scheduled content runs when the app isn't in use — practice information, health education, seasonal reminders — and the clinician switches to the interactive app the moment a patient sits down. Devices play locally, so a network hiccup never interrupts a consultation in progress. **Built for integrators who serve many practices** A chairside install is rarely one room. A practice has operatories, a waiting room, and reception; a dental service organization has hundreds of practices. TelemetryOS manages all of it from one console — every device, every screen, every app version — so an integrator supports the whole fleet remotely instead of dispatching trucks. That fleet view is what turns a custom app into a recurring business. Device health and proof-of-play are visible per practice, content schedules are set per location or across the group, and the education app itself updates from a single git push. TelemetryOS enables applications to connect to any REST API, so the same app can read from practice management or imaging systems the integrator already works with — making each install stickier and each renewal easier. Q: How do integrators build a chairside education app on TelemetryOS? A: Applications are built with the TelemetryOS React SDK and deployed git-to-screen. An integrator builds the app once — a 3D anatomy viewer, a procedure explainer, a treatment-plan walkthrough — then deploys it to every practice they serve, with updates pushed from one codebase to every screen. Q: Can a clinician interact with the screen during a consultation? A: Yes. Touch and interactive input are first-class on TelemetryOS, so a physician can rotate a 3D model, zoom into a region, or step through a procedure animation directly on the chairside screen while talking the patient through it. Q: Can the same screen show waiting content between consultations? A: Yes. The interactive education app runs alongside scheduled content on the same device. Between appointments the screen can show practice information, health education, or promotions, then switch to the interactive app when the clinician needs it. Q: How is patient privacy handled on chairside screens? A: TelemetryOS Edge AI runs on-device — any computer vision or LLM features execute locally with no cloud round-trip, private by design. The platform is GDPR compliant and SOC 2 Type I certified, and applications you build control exactly what data is displayed or stored. Q: What hardware runs a chairside education display? A: A commercial touch display paired with a TelemetryOS device such as the Node Mini or Node Pro. Devices are managed remotely from the TelemetryOS console, so an integrator can monitor and update every practice's screens without site visits. --- ### Corporate Communications Displays URL: https://telemetryos.com/usecases/corporate-communications-displays One message, every office, on schedule. Push a CEO update or live KPIs to every location at once — a lobby video wall carrying the town-hall instead of a screensaver. **One message, every office, on schedule** Workplace screens have a credibility problem. Most run a screensaver, a stale slide deck, or whatever the last person plugged in. When leadership has something to say — a CEO update, quarterly results, a safety alert — there's no reliable way to put it in front of every employee at once. TelemetryOS makes those screens a managed communications channel. Content publishes from one console to every office, on a schedule or instantly, targeted by location, floor, or department. A lobby video wall can carry the live town-hall at 10am, switch to the quarterly KPI dashboard after, and run brand content the rest of the day — across every site, without anyone touching a screen. Because TelemetryOS devices play content locally, a flaky branch-office connection never takes the channel down. Screens cache their content and keep playing through outages, syncing updates when connectivity returns, so the message is on the wall whether the WAN cooperates or not. **Built for distributed organizations** Corporate screens rarely stop at the lobby. The same platform that drives the video wall also runs floor-level dashboards, meeting-room signage, cafeteria menus, and factory-floor safety boards — one console, one content pipeline, one fleet for IT to monitor. For IT operators and the integrators who deploy at enterprise scale, that consolidation is the point. Device health, proof of playback, and content schedules are visible across every site, so a dark screen in a regional office is a dashboard alert, not a help-desk ticket from the receptionist. And because TelemetryOS is an application platform, communications can go beyond slides: live KPI boards fed by your BI stack, room-booking displays, and per-region messaging are applications built with a React SDK and deployed git-to-screen, not custom one-off installs. Q: Can I push one message to every office at the same time? A: Yes. TelemetryOS publishes from one console to every screen that should receive the content, in seconds. A CEO update or all-hands announcement can go live across headquarters, regional offices, and remote sites simultaneously, or on a schedule per time zone. Q: Can displays show live KPIs and dashboards? A: TelemetryOS enables applications to connect to any REST API, so screens can pull live metrics from your BI, sales, or operations systems and render them as always-current dashboards — no screenshots, no stale exports. Q: What happens to office displays if a site loses connectivity? A: Screens keep playing. TelemetryOS devices cache content locally and continue playback from the device, so a lobby wall never goes dark during an outage. Updates sync automatically when the connection returns. Q: How do I show different content in different offices or departments? A: Schedule content by location, group, or screen from one console. The lobby can carry brand content, engineering floors can show sprint dashboards, and the warehouse can run safety messaging — all managed centrally, all targeted precisely. Q: Is TelemetryOS suitable for enterprise IT requirements? A: TelemetryOS is GDPR compliant and SOC 2 Type I certified. The console gives IT teams fleet-wide device management, monitoring, and proof-of-play, so a screen network is operated like any other managed system rather than a collection of unmanaged TVs. --- ### Customer Feedback Terminals URL: https://telemetryos.com/usecases/customer-feedback-terminals Capture the rating at the moment of experience. A countertop touchscreen asks one question at the counter, routes praise to public reviews, and pages a manager about problems while the customer is still in the building. **Capture the rating at the moment of experience** Emailed surveys arrive hours after the visit and most go unanswered. The honest signal exists for about three seconds — at the counter, right after the experience — and that is exactly where a feedback terminal lives. One question, three faces or a 0–10 scale, one tap before the customer picks up their coffee or their keys. TelemetryOS runs feedback terminals as applications on the same managed fleet as digital signage, menu boards, and kiosks. The screen asks for a rating; the application decides what happens next. A high score can roll straight into a public-review prompt with a QR deep-link. A low score can open a private comment field and page a manager — and because TelemetryOS enables applications to connect to REST APIs and webhooks, that page lands in Slack, Teams, or a ticketing queue in seconds, while the customer is still in the building. Captured at the point of experience, response rates run far beyond anything an emailed survey achieves, and the responses come with context: location, daypart, and screen, all visible alongside fleet health in the same console that watches the rest of the screen network. **One fleet from the menu board to the counter** Single-purpose feedback hardware locks the workflow to a vendor, and a survey tablet on a stand fails quietly until someone notices the dead screen. TelemetryOS treats the feedback terminal as one more device in the fleet — monitored from the device management console, updated over the air, and reporting health and interaction data next to every other screen in the building. Storage scopes carry the multi-location load. Brand colors and the question set live at the application scope and deploy to every café, store, or branch at once; each location's review URL and alert webhook live at the instance scope; the offline response queue lives on the device. Corporate changes the question once, and eight hundred locations update without losing their local routing. The hardware stays standard, too. A Node Mini drives a countertop touchscreen for the rating flow, while Node Pro handles larger interactive displays — the same devices, SDK, and console an operator already uses for the wall behind the counter. The wall is what the brand says; the counter is where the customer tells you whether you got it right. Q: Can a feedback terminal send alerts to Slack, Teams, or our CRM? A: Yes. TelemetryOS enables applications to connect to REST APIs and webhooks, so a low score can page a manager in Slack or Teams within seconds, open a ticket in Zendesk, or log the response in HubSpot or any CRM that accepts a webhook. Q: How is this different from a survey tablet on a stand? A: A consumer tablet running a survey app is an unmanaged island — no fleet view, no remote updates, no failover. On TelemetryOS, every feedback terminal is a managed device with health monitoring, over-the-air application updates, and the same console that runs your menu boards and signage. Q: Can the flow change based on the score? A: Yes. The feedback app is a real application, not a static form. High scores can route to a public-review prompt with a QR deep-link, while low or middling scores open a private comment field and a page-the-manager action — your app controls the logic. Q: What happens if the network drops mid-shift? A: TelemetryOS devices run applications locally, so the terminal keeps collecting responses through an outage. The app can queue submissions on the device and sync them when connectivity returns, so a network blip never costs a response. Q: Can one brand config roll out to hundreds of locations? A: Yes. TelemetryOS storage scopes let an application keep brand colors and question sets at the application level, per-location settings like review URLs and webhooks at the instance level, and offline queues on the device — so corporate pushes one update and every location stays itself. --- ### Dynamic Menu Boards URL: https://telemetryos.com/usecases/dynamic-menu-boards Menu boards that keep up with service. Update menus by daypart, store, or campaign, and local playback keeps the counter moving even when the network wobbles. **Menu boards that keep up with service** A menu board is the hardest-working screen in a quick-service restaurant. It has to be right — the right items, the right prices, the right daypart — at every location, every minute the store is open. Doing that with static signage or consumer TVs means ladders, printed inserts, and price drift between stores. TelemetryOS turns menu boards into a managed application. Menus are scheduled by daypart, store, or campaign from one console, and every change publishes to the right screens in seconds. A limited-time offer can go live across 400 stores at 11am and disappear at 2pm without anyone touching a screen. Because TelemetryOS devices play content locally, the counter keeps moving even when the network doesn't. Boards don't blank, spin, or fall back to a stale menu when connectivity wobbles — playback continues from the device, and updates sync when the connection returns. **Built for multi-site operators** Menu boards rarely live alone. The same platform that drives the boards behind the counter also runs the drive-through displays, the self-order kiosks, and the promo screens in the dining room — one console, one content pipeline, one fleet to monitor. For operators and integrators, that consolidation is the point. Device health, proof of playback, and content schedules are visible across every location, so a board that's down in one store is a dashboard alert, not a customer complaint. And because TelemetryOS is an application platform, menu boards can go beyond static layouts: live POS-driven sold-out states, dynamic pricing, and localized menus per market are all applications, not custom one-off installs. Q: How do I schedule menu changes by daypart? A: TelemetryOS lets you schedule content by time of day, day of week, or date range. Build a breakfast, lunch, and dinner menu once, assign each to its daypart, and every board switches automatically — per store, per region, or across the whole fleet. Q: What happens to my menu boards if the internet goes down? A: Menus keep playing. TelemetryOS devices cache content locally and play it from the device, so a network outage never blanks a board mid-service. When connectivity returns, the device syncs any pending updates automatically. Q: Can I update prices across hundreds of locations at once? A: Yes. Price and item changes publish from one place to every screen that should receive them, in seconds. You can target a single store, a franchise group, a region, or the entire network — and verify from the console that every board took the update. Q: Can menu boards pull live data from my POS or menu management system? A: TelemetryOS enables applications to connect to any REST API, so menu boards can read items, prices, and availability from your POS or menu management platform and mark items sold out in real time. Q: What hardware do I need for digital menu boards? A: Any commercial display paired with a TelemetryOS device, such as the Node Mini or Node Pro, purpose-built media players that run content reliably 24/7 and are managed remotely from the TelemetryOS console. --- ### Emergency Alert Overrides URL: https://telemetryos.com/usecases/emergency-alert-overrides Take over every screen in seconds. Push severe weather, lockdown, evacuation, or safety instructions across a fleet, then return screens to normal scheduling when the all-clear comes. **Take over every screen in seconds** Daily content is valuable, but emergency content is the moment the screen network has to prove itself. A campus closure, severe weather warning, evacuation route, or facility lockdown cannot wait for someone to find the right CMS login. It has to preempt whatever is running and reach the right screens immediately. TelemetryOS treats emergency alerts as priority overrides on the same fleet that runs ordinary digital signage, kiosks, dashboards, and wayfinding. A safety team can push a message to every screen, or to a targeted group of buildings, floors, or zones, and scheduled content resumes when the alert clears. The same device management layer that monitors menu boards, dashboards, kiosks, and room displays becomes the alerting surface when time matters. Because TelemetryOS enables applications to connect to REST APIs, webhooks, MQTT, serial, and emergency alert feeds, integrators can build alert workflows around the systems an organization already uses. CAP-triggered severe weather alerts, facilities alarms, security desk overrides, and manual Studio actions can all drive the same visible screen takeover. **Built for organizations with distributed facilities** Emergency communication fails when every building has its own screen system. Corporate campuses, schools, hospitals, venues, transit hubs, and factories need one accountable layer that knows which screens are online and which message each audience should see. TelemetryOS devices run locally and cache content, so an unstable network does not blank the screen at the exact moment people need instructions. Devices report health, proof of playback, and status to the console; authorized teams can also use the TelemetryOS iOS app for field commands and emergency overrides. Node Mini handles standard alert displays, Node Pro drives interactive kiosks and large displays, and Node Max adds local AI where teams want on-device summarization or vision-triggered workflows. The result is not a separate emergency product bolted beside signage. It is one managed screen fleet that carries normal communication every day and priority instructions when the situation changes. Q: Can emergency alerts override scheduled content immediately? A: Yes. TelemetryOS includes priority override workflows that can preempt normal playlists and applications across every targeted screen. When the alert ends, screens return to their scheduled content automatically. Q: Can alerts be triggered by CAP feeds or external systems? A: Yes. TelemetryOS enables applications to connect to REST APIs, webhooks, and emergency alert feeds, including CAP-based sources, so teams can build alerts that trigger from the systems they already trust. Q: Can we target only affected buildings, floors, or zones? A: Yes. Devices are organized into groups and tags, so an alert can go to an entire fleet, a single campus, or a specific building zone. Integrators can also build application logic that maps external alert data to the right device groups. Q: What happens if the network is degraded during an emergency? A: TelemetryOS devices run locally and cache content on the device, so screens do not go blank when the network is unstable. Alert applications can show the latest active instruction and sync state back when connectivity returns. Q: Can field teams trigger or clear alerts from mobile? A: Yes. The TelemetryOS iOS app supports fleet commands and emergency overrides, so authorized teams can act from the field while central operations retains visibility and control. --- ### Interactive Kiosks URL: https://telemetryos.com/usecases/interactive-kiosks Kiosks become part of the platform. Interactive kiosks run beside scheduled content and remote support, not as a separate system — a self-order kiosk on the same console as the menu boards. **Kiosks become part of the platform** Most operations run kiosks as an island: separate vendor, separate software, separate support contract, separate monitoring. The self-order kiosk lives in one system while the menu boards two metres above it live in another, and nobody can see both from the same place. Every new screen type adds another silo. TelemetryOS treats kiosks as what they are — interactive applications on the same platform as everything else. A self-order kiosk runs on the same console as the menu boards, the queue display, and the promo screens. Kiosk apps are built with the React SDK and deployed git-to-screen, and TelemetryOS enables applications to connect to any REST API, so ordering flows talk to your POS, check-in screens talk to your booking system, and wayfinding pulls from your facilities data. Interactivity doesn't displace scheduled content; the two run side by side. A kiosk can attract with scheduled promotions until someone touches it, then drop into the ordering flow, then return to the loop. Devices execute applications locally, so the kiosk stays responsive through a network outage and syncs when connectivity returns. **One console for kiosks and everything around them** The case for consolidation shows up in operations. When kiosks join the same fleet as the signage, device health, app versions, and proof-of-play for every screen type sit in one view. A kiosk that's down at one location is a dashboard alert with remote diagnostics behind it, not a phone call routed between vendors who each blame the other. For integrators, that's the difference between installing kiosks and operating a kiosk business. One platform covers the hardware — Node Mini, Node Pro, or Node Max depending on the workload — one console covers monitoring and content, and one codebase covers the app across every site. Adding a new interaction, a new screen, or a new location is a deployment, not a new vendor relationship. Q: Can kiosks and digital signage really run on one platform? A: Yes — that's the design. On TelemetryOS, screens, kiosks, and sensors are all applications on one platform. A self-order kiosk, the menu boards above the counter, and the promo screen by the door are managed from the same console with the same content pipeline and the same fleet monitoring. Q: How are kiosk applications built on TelemetryOS? A: Kiosk apps are built with the TelemetryOS React SDK and deployed git-to-screen. Integrators and developers build ordering flows, check-in screens, wayfinding, or product finders as web applications, then ship updates to the entire kiosk fleet from one codebase. Q: Can a kiosk connect to my POS, booking, or queue system? A: TelemetryOS enables applications to connect to any REST API, so a kiosk app can read menus and submit orders to your POS, check guests into your booking system, or pull live queue status — whatever backend your operation already runs. Q: What happens when a kiosk loses network connectivity? A: The application keeps running. TelemetryOS devices cache content and execute applications locally, so the kiosk stays interactive through an outage and syncs with backend systems when the connection returns. How an app handles offline transactions is under the developer's control. Q: How do I monitor and support a fleet of kiosks remotely? A: From the TelemetryOS console. Device health, app status, and proof-of-play are visible per kiosk across every site, so a frozen screen is a dashboard alert rather than a customer complaint — and most fixes happen remotely instead of with a site visit. --- ### Patient Check-In Kiosks URL: https://telemetryos.com/usecases/patient-check-in-kiosks Calm navigation and self check-in. Patient kiosks tie into the directory and appointment system to cut reception load — mapping the way and checking patients in with a code scan. **Calm navigation and self check-in** A clinic lobby concentrates two problems at the same desk: patients who need to check in, and patients who need to find where they're going. Reception absorbs both, queues build, and the first minutes of every visit are spent waiting in the wrong line. TelemetryOS moves both jobs to the kiosk. A check-in application connects to your appointment system, so a patient scans a code from their confirmation, the kiosk verifies the appointment, and reception sees the arrival without working the queue. The same kiosk ties into the facility directory, mapping the route to imaging on the second floor or the lab down the hall, with a clear next step instead of a hallway full of signs. Reliability matters more in healthcare than anywhere else, and TelemetryOS devices run applications locally. A kiosk stays on through a network outage, continuing to show wayfinding and facility information rather than a blank screen, and syncs with your systems when connectivity returns. **Built for healthcare operators** Check-in kiosks rarely live alone. The same platform that runs them also drives waiting-room screens, department wayfinding displays, and staff-facing boards — one console, one content pipeline, one fleet for IT to monitor across every clinic and floor. For healthcare IT teams and the integrators who deploy for them, that consolidation is the point. Device health, proof of playback, and application versions are visible across every kiosk, so a frozen check-in screen is a dashboard alert before it becomes a line at reception. And because TelemetryOS is an application platform, kiosks can go beyond check-in: queue status displays, multilingual wayfinding, and forms that hand off to a patient's phone are applications built with a React SDK and deployed git-to-screen — and Edge AI runs on the device itself, private by design, with no cloud round-trip. Q: How does self check-in work on a TelemetryOS kiosk? A: A check-in application runs on the kiosk and connects to your scheduling system. The patient scans a code from their appointment confirmation or enters their details, the kiosk confirms the appointment, and reception sees the arrival without handling the queue themselves. Q: Can kiosks connect to our appointment and directory systems? A: TelemetryOS enables applications to connect to any REST API, so a kiosk application can read from your scheduling, EHR-adjacent, and facility directory systems to confirm appointments and route patients to the right department. Q: How is patient privacy handled on shared kiosks? A: TelemetryOS is GDPR compliant and SOC 2 Type I certified, and Edge AI capabilities run on-device with no cloud round-trip. Check-in applications can be built to keep patient interactions local to the kiosk and your systems, with sessions clearing between patients. Q: What happens to check-in kiosks if the clinic network goes down? A: TelemetryOS devices cache content and applications locally, so kiosks stay on and continue showing wayfinding and facility information through an outage rather than going dark, syncing with your systems when connectivity returns. Q: What hardware do patient check-in kiosks require? A: A touch-capable kiosk enclosure or commercial display paired with a TelemetryOS device such as the Node Mini or Node Pro, with peripherals like barcode scanners attached. Every kiosk is managed remotely from the TelemetryOS console with fleet-wide health monitoring. --- ### Real-Time Operations Dashboards URL: https://telemetryos.com/usecases/real-time-dashboards Operations data, on the floor. Connect operations data to the floor — a production wallboard showing live output and a sensor-triggered alert the instant a station goes down. **Operations data, on the floor** Most plants already have the data: output, takt, quality, downtime, all flowing through MES and SCADA systems. What the floor sees is usually something else — a TV running a stale browser tab, a whiteboard updated at shift change, numbers nobody trusts. The gap between what operations knows and what the floor sees costs real time. TelemetryOS closes that gap by running dashboards as applications on managed screens. A wallboard app built with the React SDK reads live from your MES, historian, or BI platform — TelemetryOS enables applications to connect to any REST API — and shows the floor its actual numbers as they change. Because screens, kiosks, and sensors are applications on one platform, a sensor event can flip a board to an alert state the instant a station goes down: red banner, downtime clock, affected line called out, then back to normal when it clears. The floor is a hostile place for fragile setups, so resilience lives at the device. TelemetryOS devices cache and execute locally, keeping dashboards on screen through network drops and resyncing when connectivity returns. A board that must be trusted can't be one router reboot away from blank. **One fleet across lines, shifts, and plants** A dashboard program rarely stops at one screen. Line boards, andon-style alerts, shipping-dock status, break-room KPIs, and safety messaging all want screens — and without a platform, each becomes its own mini-project with its own PC under a desk. TelemetryOS runs all of them as one fleet from one console, with content targeted per line, shift, or site. That console view is what makes the program operable. IT sees device health and proof-of-play across every plant; a dead screen on a night shift is an alert, not a surprise during the morning Gemba walk. And because dashboards are applications deployed git-to-screen, improving them is a code push: add a metric, refine an alert threshold, roll it to every plant at once. Edge AI extends the same screens further — on-device computer vision and LLMs run locally, private by design, with no production data making a cloud round-trip. Q: How does a wallboard get live data from our production systems? A: TelemetryOS enables applications to connect to any REST API, so a dashboard app can read from your MES, SCADA historian, ERP, or BI platform and render live output, OEE, and line status as the numbers change — no manual exports or stale spreadsheets on a TV. Q: Can a screen react to a sensor event, like a station going down? A: Yes. Screens, kiosks, and sensors are all applications on one platform, so a sensor-triggered event can flip a wallboard to an alert state the instant a station stops — red banner, downtime clock, and the affected line called out — then return to the normal dashboard when it clears. Q: What happens to floor dashboards if the network drops? A: Screens don't go black. TelemetryOS devices cache content and run applications locally, so the dashboard stays up through an outage and resyncs live data when the connection returns. Apps can indicate when data is stale so the floor never reads old numbers as current. Q: Can different lines, shifts, or plants see different dashboards? A: Yes. Content is scheduled and targeted per screen, line, shift, or site from the TelemetryOS console. Line 3 sees its own takt and quality numbers, the shipping dock sees order status, and the break room shows plant-wide KPIs and safety messaging — all from one place. Q: What hardware survives a factory floor? A: Commercial displays driven by TelemetryOS devices such as the Node Pro or Node Max, purpose-built media players that run 24/7 and are managed remotely from the TelemetryOS console — so IT can support screens across plants without walking the floor. --- ### Room Schedule Displays URL: https://telemetryos.com/usecases/room-schedule-displays Room availability that stays current. Door-side and lobby screens read booking systems, show what is happening now, and guide people to the right space without another tablet fleet. **Room availability that stays current** Room displays are often the first screen fleet a workplace or campus forgets it owns. A tablet outside a conference room shows an old meeting, the lobby board misses a room change, and visitors ask the front desk where to go. The problem is not the calendar data. The problem is that the screen network is not managed like infrastructure. TelemetryOS runs room schedules as screen applications on managed devices. Door-side displays can show the current meeting, next booking, availability, and check-in state; lobby boards can roll those same bookings into a floor-wide overview. Because TelemetryOS enables applications to connect to REST APIs, the app can read from Google Calendar, Microsoft 365, EMS, Robin, or the booking system the organization already uses. The same deployment can do more than show the calendar. A room display can release an abandoned booking, guide a visitor to a different open space, or show a local fallback state when the network is degraded. The screen keeps running on the device; the application can tell people the schedule is stale instead of pretending old data is current. **Built for workplaces, campuses, and venues** Room schedules are not isolated screens. They belong next to lobby directories, wayfinding directories, event boards, and corporate communications displays. TelemetryOS lets those touchpoints run on one fleet with one console for device health, updates, and content targeting. For corporate real estate teams, that means fewer orphaned tablets and fewer vendor-specific admin tools. For campuses and venues, it means room changes, event schedules, and wayfinding can come from the same data sources and appear on the right screens by building or floor. Node Mini covers standard door-side displays, Node Pro handles interactive boards and larger formats, and TelemetryOS device management gives IT one place to see whether the fleet is healthy. A room schedule display should not be a static calendar taped to a wall. It should be a dependable endpoint that reflects the state of the building. Q: Can room displays connect to Google Calendar, Outlook, or a room booking platform? A: Yes. TelemetryOS enables applications to connect to REST APIs, so a room schedule app can read from Google Calendar, Microsoft 365, EMS, Robin, or another booking platform and render the current room state on screen. Q: Can the same deployment run lobby boards and door-side displays? A: Yes. Door-side screens, lobby directory boards, floor maps, and room availability dashboards can all run as applications on the same TelemetryOS fleet, with content targeted by device group or location. Q: What happens if the booking system or network is unavailable? A: TelemetryOS devices keep the application running locally. The app can show the last known schedule with a clear stale-data state, keep wayfinding visible, and sync fresh bookings when connectivity returns. Q: Can people book or release a room from the display? A: Yes. If the booking system exposes the right API, the screen application can include check-in, release, or reservation actions. TelemetryOS provides the touch-capable runtime and peripheral APIs; your app controls the workflow. Q: Which Node device should run room schedule displays? A: Node Mini is a good fit for standard door-side and small lobby displays. Node Pro fits larger multi-display or interactive deployments, and all devices are monitored from one console. --- ### In-Store Retail Media Networks URL: https://telemetryos.com/usecases/retail-media-networks Turn shelves into an ad network. Shelf-edge and end-cap screens run brand campaigns with proof-of-play — a grocery end-cap promoting the product right beside it. **Turn shelves into an ad network** Retail media is moving into the store, and the store has a problem the web never had: thousands of physical screens, spread across hundreds of locations, that all have to run the right campaign at the right time — with evidence that they did. A grocery end-cap promoting the product right beside it is a high-value placement, but only if the operator can book it, run it, and prove it played. TelemetryOS runs the screen network as a managed application fleet. Campaigns are scheduled by daypart, store, or campaign group from one console, so a brand flight can launch across every end-cap in a region at 8am Monday and end cleanly two weeks later. Shelf-edge screens, end-caps, and cooler doors are all applications on the same platform, targeted from the same pipeline. Proof-of-play is built into the platform, not bolted on. Every device logs what played, where, and when, and that record flows back to the console — the reconciliation data that turns in-store screens into sellable inventory. And because devices cache and play content locally, a store's network outage never blanks a paid placement; logs sync when connectivity returns. **Built for operators selling inventory** A retail media network is only as sellable as it is operable. The TelemetryOS console gives operators one view of the entire fleet — device health, content schedules, and playback verification across every store — so a dark screen is a dashboard alert before it becomes a make-good conversation with a brand. Because TelemetryOS is an application platform, the network can grow beyond looping creative. Applications are built with a React SDK and deployed git-to-screen, so a retail media application can connect to ad servers for automated campaign booking, pull live product data to pair ads with on-shelf availability, and report playback back for billing. For integrators and retailers, that means one platform carries the network from pilot aisle to chain-wide rollout. Q: How does proof-of-play work for retail media campaigns? A: Every TelemetryOS device logs what played, where, and when, and reports it back to the console. That playback record is the evidence brands and agencies need to reconcile a campaign — which screens ran the creative, for how long, across which stores — without manual audits. Q: Can I target campaigns to specific stores, aisles, or dayparts? A: Yes. Campaigns are scheduled by daypart, store, or campaign group from one console. A brand buy can run on end-caps in 200 stores during evening hours only, while shelf-edge screens in another region run a different campaign — all from the same content pipeline. Q: What happens to ad playback if a store loses connectivity? A: Playback continues. TelemetryOS devices cache campaign content locally and play it from the device, so a network outage never blanks a paid placement mid-flight. Playback logs are stored on the device and sync to the console when the connection returns. Q: Can the network connect to my ad server or campaign management platform? A: TelemetryOS enables applications to connect to any REST API, so a retail media application can pull campaign bookings, creative, and flight dates from your ad server or campaign platform, and push playback data back for billing and reporting. Q: What hardware runs a shelf-edge or end-cap screen network? A: Any commercial display paired with a TelemetryOS device such as the Node Mini for shelf-edge and end-cap screens, or the Node Pro for larger formats. Every device in the network is monitored and managed remotely from the TelemetryOS console. --- ### Retail Storefront Displays URL: https://telemetryos.com/usecases/retail-storefront-displays Make the store wall programmable. Schedule and update high-traffic retail displays across every location from one place — like a flagship wall behind checkout that changes by campaign. **Make the store wall programmable** A storefront display is retail's most visible asset, and the hardest to keep current. The wall behind checkout, the window-facing screens, the endcap displays — each one has to carry the right campaign at the right store on the right date, and with static signage that means print runs, shipping, and store staff on ladders. TelemetryOS turns those screens into a managed application. Campaigns are scheduled by store, region, or date range from one console, and every change publishes to the right screens in seconds. A flagship wall can switch from the spring campaign to a flash sale at 9am across every location, then back again at close, without a single site visit. Because TelemetryOS devices play content locally, a store's screens stay live even when its network doesn't. Displays don't blank or freeze mid-campaign when connectivity wobbles — playback continues from the device, and updates sync when the connection returns. **Built for multi-site retailers** Storefront displays rarely live alone. The same platform that drives the wall behind checkout also runs window displays, endcap screens, and in-aisle kiosks — one console, one content pipeline, one fleet to monitor across every banner and region. For retail operators and the integrators who serve them, that consolidation is the point. Device health, proof of playback, and campaign schedules are visible across every location, so a dark screen in one store is a dashboard alert, not a district manager's discovery. And because TelemetryOS is an application platform, displays can go beyond looping video: live pricing, inventory-aware promotions, and localized content per market are applications built with a React SDK and deployed git-to-screen, not custom one-off installs. Q: Can I run different campaigns at different stores from one console? A: Yes. TelemetryOS schedules content by store, region, or campaign from a single console. A flagship wall can carry the national launch while a regional store runs a local promotion, and both update the moment you publish. Q: What happens to storefront displays if a store loses internet? A: Displays keep playing. TelemetryOS devices cache content locally and play it from the device, so a network outage never blanks a window display or checkout wall. When connectivity returns, the device syncs any pending updates automatically. Q: How do I coordinate a campaign launch across hundreds of stores? A: Build the campaign once, schedule it with a start and end date, and assign it to the stores that should run it. Every screen switches over at the scheduled moment, and the console shows proof-of-play so you can verify each location took the change. Q: Can displays pull live data like inventory or pricing? A: TelemetryOS enables applications to connect to any REST API, so a storefront display can read pricing, stock levels, or promotions from your commerce or inventory systems and update on screen without anyone republishing content. Q: What hardware do I need for retail storefront displays? A: Any commercial display paired with a TelemetryOS device. The Node Mini suits single screens, the Node Pro handles demanding storefront content, and the Node Max drives large video walls — all managed remotely from the TelemetryOS console. --- ### Self-Order Kiosks URL: https://telemetryos.com/usecases/self-order-kiosks Ordering that fits the counter. A compact self-order terminal browses the menu, takes modifiers and upsells, pairs with tap-to-pay, and fires the kitchen — on the same fleet as the menu boards above it. **Ordering that fits the counter** Most self-order hardware assumes a big lobby and a bigger contract: a floor-standing kiosk locked to one POS ecosystem, or a consumer tablet in a plastic mount that nobody can support at fifty locations. The cafés, food halls, bakeries, and counter-service restaurants in between are left taking orders the way they always have — one register, one line. TelemetryOS runs self-order as an application on a compact countertop touchscreen. The app browses the menu, handles modifiers and upsell prompts, looks up loyalty, takes tap-to-pay through a paired NFC reader, fires the kitchen display, and prints or texts the receipt. Because TelemetryOS enables applications to connect to any REST API, the ordering flow talks to the POS the operation already runs — Toast, Square, Lightspeed, Revel — and WebUSB, WebSerial, and Web Bluetooth are exposed as standard browser capabilities, so payment readers and printers pair without low-level drivers. In casual dining the same hardware becomes a tableside reorder terminal: another round of drinks, a dessert, the check — without flagging down a server. **The same engine as the menu board** A self-order kiosk should not be a second system bolted beside the menu boards. On TelemetryOS, it is the same platform doing one more job. The dayparting engine that flips the boards from breakfast to lunch flips the kiosk at the same moment; a limited-time offer published from one place lands on the board, the kiosk, and the window sign together; and application-scope storage means corporate marketing rolls a promotion out to two hundred stores in one push. Operations see every ordering screen in the same device management console as the rest of the fleet — health, application versions, and interaction data per location, with over-the-air updates instead of site visits. A frozen kiosk is a dashboard alert before it is a lunchtime queue. Node Mini drives a countertop ordering touchscreen; Node Pro powers larger-format and multi-display interactive kiosks. Same SDK, same console, same fleet — ordering simply becomes another application the screen network runs. Q: Can a self-order kiosk connect to our POS? A: Yes. TelemetryOS enables applications to connect to any REST API, so an ordering app can read menus from and submit orders to Toast, Square, Lightspeed, Revel, or whatever system your operation already runs, and fire the kitchen display when the order completes. Q: How do payments and receipt printers work? A: TelemetryOS exposes WebUSB, WebSerial, and Web Bluetooth as standard browser capabilities, so an application can pair an NFC payment reader or receipt printer without low-level drivers. The payment itself is processed by your payment provider; the kiosk app drives the flow. Q: Can the kiosk menu stay in sync with the menu boards? A: Yes. The same dayparting engine that switches the boards from breakfast to lunch drives the kiosk, and shared application data means a price change or limited-time offer published once shows up on the board and the ordering screen together. Q: How do we roll out a promotion to every store? A: Application-scope storage means corporate publishes the offer once and every location's kiosk picks it up, while per-store settings like POS credentials and pricing stay at the instance level. One push, every store, no per-site visits. Q: What happens if the network goes down during service? A: TelemetryOS devices run applications locally, so the kiosk stays responsive through an outage. How an application handles offline ordering and queued transactions is under the developer's control, and devices sync state when connectivity returns. --- ### Smart Cooler Screens URL: https://telemetryos.com/usecases/smart-cooler-screens One pane of glass: merchandising and ad revenue. Cooler doors show a full-door ad, then flip to a live planogram as a shopper steps in — an on-device camera flags out-of-stocks while the glass keeps selling. **One pane of glass: merchandising and ad revenue** A cooler door is prime real estate doing one job: keeping things cold. Replace the glass with a screen and it can do three — sell brand campaigns as retail media inventory, merchandise what's inside with a live planogram, and watch its own shelves for out-of-stocks. The catch is that doing all three usually means three systems and a cloud video pipeline nobody's privacy team wants to approve. On TelemetryOS, the cooler door is one application. The screen runs a full-door brand ad in rotation, then flips to a live planogram view as a shopper steps in — the transition decided by on-device computer vision, with no cloud round-trip. Campaigns are scheduled by daypart, store, or campaign from one console, and proof-of-play logs make every door sellable, auditable inventory. The same device watches the shelves. An interior camera runs detection models locally on TelemetryOS Edge AI, flagging an empty facing the moment it happens — while the glass keeps selling. Footage is processed on the device, with no faces or PII stored, and because devices cache and play content locally, an outage never blanks a paid placement or pauses detection. **Built for c-store and grocery operators** Cooler screens earn their keep at fleet scale, and fleet scale is what the TelemetryOS console is for. Device health, content schedules, and playback verification are visible across every door in every store, so a failed screen is a dashboard alert before it's a missed impression or an angry brand partner. End-caps, shelf-edge screens, and checkout displays run on the same platform, from the same pipeline. For integrators and retailers, the application layer is open. Cooler applications are built with a React SDK and deployed git-to-screen, and TelemetryOS enables applications to connect to ad servers, planogram systems, and inventory platforms over any REST API — so out-of-stock flags can flow straight into replenishment, and campaign bookings can flow straight onto the glass. One platform, one device per door, three revenue and labor stories. Q: How does the cooler door switch between ads and the planogram? A: The door screen is a TelemetryOS application. On-device computer vision detects a shopper approaching and flips the display from a full-door brand ad to a live planogram view of what's inside, then returns to ad rotation when the shopper moves on — all decided locally, with no cloud round-trip. Q: How does out-of-stock detection work, and where does the camera data go? A: An on-device camera watches shelf state inside the cooler and runs detection models locally on TelemetryOS Edge AI. When a facing runs empty, the application flags it for store staff or your replenishment system. Video is processed on the device — no faces, no PII stored, nothing streamed to the cloud. Q: Can I sell the cooler doors as retail media inventory? A: Yes. Cooler screens run brand campaigns with the same scheduling and proof-of-play as any TelemetryOS retail media deployment. Every device logs what played, where, and when, giving brands the playback evidence they need to reconcile a campaign across stores. Q: What happens to cooler screens if the store loses connectivity? A: The glass keeps selling. TelemetryOS devices cache ads and planogram content locally and play from the device, and the detection models run on the device too. An outage doesn't blank a paid placement or stop out-of-stock detection; everything syncs when the connection returns. Q: What hardware do smart cooler doors require? A: Cooler-door displays paired with a TelemetryOS device with the compute for on-device vision, such as the Node Pro or Node Max, plus an interior camera for shelf detection. Every door in every store is monitored and managed from the TelemetryOS console. --- ### Smart Drive-Through Menu Boards URL: https://telemetryos.com/usecases/smart-drive-through-menus A drive-through that remembers — anonymously. The board recognizes a returning vehicle and recalls past orders on the device, with no faces or PII stored, to greet the driver with a tailored promo. **A drive-through that remembers — anonymously** The drive-through is where personalization pays fastest: a relevant promo at the order point lifts ticket size, and a faster decision keeps the lane moving. But personalizing the lane has usually meant cameras streaming to the cloud, facial recognition, and a privacy conversation no operator wants to have with customers or regulators. TelemetryOS Edge AI puts the intelligence on the device instead. Computer vision running locally on the board's device recognizes a returning vehicle — not a person — and recalls past orders to greet the driver with a tailored offer the moment they pull up. No faces are stored, no PII is retained, and nothing leaves the device for inference. Privacy isn't a setting; it's the architecture. The smart layer sits on top of a board that already works. Menus are scheduled by daypart, store, or campaign from one console, price changes publish across the fleet in seconds, and local playback means the lane keeps serving when the network drops. The recognition models run on the device too, so personalization survives an outage along with the menu. **Built for QSR operators and integrators** A smart lane is one application on the platform that runs the rest of the store. The same TelemetryOS deployment drives the indoor menu boards, self-order kiosks, and promo screens — one console for content, device health, and proof of playback across every location, so a dark board is a dashboard alert, not a stalled lane. For integrators, the personalization logic is buildable rather than locked in. Applications are written with a React SDK and deployed git-to-screen, and TelemetryOS enables applications to connect to POS and loyalty systems so an anonymous vehicle match can map to a relevant offer, live pricing, or real-time sold-out states. Pilot it in one lane, measure the lift, and roll it across the chain from the same console. Q: How does the menu board recognize a returning vehicle without storing PII? A: TelemetryOS Edge AI runs computer vision on the device, matching vehicle signatures locally rather than identifying people. No faces are captured for recognition, no personal data is stored, and nothing is sent to the cloud — recognition and recall happen entirely on the board's device. Q: What happens to the drive-through boards if the network goes down? A: Service continues. TelemetryOS devices cache menus and play them locally, and the on-device recognition models don't depend on connectivity. The lane keeps moving through an outage, and the device syncs any pending updates when the connection returns. Q: Can the boards still do standard daypart and promo scheduling? A: Yes. Smart drive-through boards are still TelemetryOS menu boards underneath: schedule breakfast, lunch, and dinner menus by daypart, run limited-time offers by store or region, and publish price changes across the fleet in seconds from one console. Q: Can the board connect to my POS to act on past orders? A: TelemetryOS enables applications to connect to any REST API, so a drive-through application can read menu data, item availability, and order history from your POS to pair an anonymous vehicle match with a relevant promo — sold-out items drop off the board automatically. Q: What hardware does a smart drive-through lane require? A: Outdoor-rated displays paired with a TelemetryOS device with the compute for on-device vision and inference, such as the Node Pro or Node Max, plus a lane camera. Every device is monitored and managed remotely from the TelemetryOS console. --- ### Transit Departure Boards URL: https://telemetryos.com/usecases/transit-departure-boards Departure boards people can trust. Managed playback, monitoring, and local caching keep critical boards predictable — an overhead bank of departures that stays live even if a screen drops the network. **Departure boards people can trust** A departure board has one job: be right, and be on. Passengers plan around it, staff get blamed when it's wrong, and a black screen above a platform erodes trust in the whole system. Yet many transit displays still run on unmanaged players nobody can see into — discovered down only when a passenger complains. TelemetryOS runs departure boards as managed applications. A board app built with the React SDK reads live data from your AVL system or GTFS-realtime feed — TelemetryOS enables applications to connect to any REST API — and renders departures, delays, and platform changes the moment the data moves. The same screens carry service alerts and safety messaging, scheduled by station or taken over immediately when something urgent happens. Resilience is built in at the device. TelemetryOS devices cache content and execute applications locally, so an overhead bank of departures stays live even if a screen drops the network; it keeps playing from the device and resyncs when the connection returns. No black screens mid-rush because a switch rebooted. **Monitored like the infrastructure it is** Departure boards are infrastructure, and infrastructure needs monitoring. The TelemetryOS console gives operations teams one view of every device across every station: health, playback status, app version, and proof-of-play. A screen that fails at the end of a far platform is an alert with remote diagnostics behind it, not a discovery made on a walk-through three days later. That one console scales from a single station to a whole network. Content and schedules are managed per station, per platform, or system-wide; new stations join the fleet as deployments, not projects. For agencies and the integrators who serve them, the result is a display network that behaves predictably — which, for a departure board, is the entire point. Q: How do departure boards get live arrival and departure data? A: TelemetryOS enables applications to connect to any REST API, so a departure board app can read from your AVL system, GTFS or GTFS-realtime feeds, or operations platform and render live departures, delays, and platform changes as the data changes. Q: What happens to a departure board when it loses network connectivity? A: The board keeps playing. TelemetryOS devices cache content and run applications locally, so a screen that drops the network doesn't go black — it continues from the device and resyncs live data the moment connectivity returns. A well-built app can also flag when its data is stale rather than showing silently wrong times. Q: How do we know every board in every station is actually working? A: The TelemetryOS console shows device health, playback status, and proof-of-play for the entire fleet. A failed screen in a far station surfaces as an alert with remote diagnostics behind it, so operations teams find problems before passengers do. Q: Can the same screens show service alerts and other content? A: Yes. Departures, service disruption alerts, safety messaging, and advertising are all content on the same platform — scheduled by station, platform, or time of day, with urgent alerts able to take over the relevant screens immediately. Q: What hardware is suitable for station departure boards? A: Commercial displays driven by TelemetryOS devices such as the Node Pro or Node Max, built to run 24/7 and managed remotely from the TelemetryOS console. Overhead banks, platform screens, and concourse walls all run on the same managed fleet. --- ### Visitor Check-In Terminals URL: https://telemetryos.com/usecases/visitor-check-in-terminals Retire the clipboard at every front desk. One check-in application greets visitors, members, guests, and contractors — confirming details, capturing signatures and badge photos, and notifying the host in seconds. **One check-in layer for every front desk** Reception is where first impressions and paperwork collide. The clipboard gets lost, the iPad-on-a-stand belongs to a per-device subscription vendor, and every venue type — office, clinic, salon, gym, co-working space — somehow ends up with its own disconnected check-in stack. TelemetryOS runs check-in as an application on a countertop touchscreen at the desk. The terminal identifies the visitor, confirms and updates contact details, presents the consent form or NDA for signature, captures a badge photo through the front camera, and notifies the host the moment check-in completes. Because TelemetryOS enables applications to connect to REST APIs, the arrival ping lands in Slack, Teams, Google Workspace, Microsoft 365, or Calendly — whatever the front office already lives in — and barcode and QR decoding turn an emailed confirmation into a ten-second check-in. The camera, the scanner, and the signature pad are not peripherals with proprietary SDKs. They are standard browser capabilities of the platform, which is why a check-in flow that would take a vendor integration elsewhere is a few lines of application code here. **Built for operators with more than one front desk** The check-in market is sliced into verticals — visitor management for offices, intake for healthcare, bookings for fitness and salons. A multi-brand operator running a dental group and a medspa, or hotels alongside restaurants and gyms, ends up operating four vendor stacks that do the same job with different logins. On TelemetryOS, check-in is one application on one managed fleet, whether the person arriving is a patient, a guest, a member, or a contractor. Per-location branding and workflow live in instance-scope settings; the application itself deploys everywhere from one codebase. Reception staff get a browser-accessible companion view for walk-ins and overrides, and device management gives IT health, versions, and proof the lobby screen is alive at every property. The same fleet runs the rest of the building, too — the lobby wayfinding directory, the room schedule displays upstairs, the signage behind the desk. Node Mini drives a countertop check-in touchscreen; Node Pro covers larger interactive lobby installations. One console, one SDK, and a front desk that finally stopped photocopying forms. Q: Can the terminal capture badge photos and scan documents? A: Yes. TelemetryOS exposes the camera as a standard browser capability, so a check-in application can capture a badge photo or scan a driver's license or insurance card in a few lines of code, with no separate hardware SDK. Barcode and QR decoding handle appointment confirmations. Q: How does the host find out their visitor has arrived? A: Host notification is an HTTPS call. TelemetryOS enables applications to connect to REST APIs, so arrival pings can go to Slack, Teams, Google Workspace, Microsoft 365, Calendly, or whatever system the front office already uses. Q: Can visitors sign an NDA or consent form on the screen? A: Yes. The check-in app is a full touch application, so it can present documents, capture signatures, and store the result in your system of record — visitor management for an office, consent workflows for a clinic or salon. Q: We run different brands and venue types. Can one platform cover them? A: Yes. A multi-brand operator running offices, clinics, gyms, and hospitality venues can deploy one check-in application with per-location branding and workflows, instead of a different vendor stack at each property. Same OS, same fleet, same console. Q: Can reception staff manage walk-ins and overrides? A: Yes. A TelemetryOS application can expose a browser-accessible companion view, giving the receptionist a phone-friendly admin surface for walk-ins, overrides, and the day's arrivals while the terminal handles the queue. --- ### Wayfinding & Directories URL: https://telemetryos.com/usecases/wayfinding-directories Give every visitor a next step. Searchable maps and location-aware content move people through complex spaces — a mall directory shoppers tap, with a QR hand-off to their phone. **Give every visitor a next step** Complex spaces lose people. Malls, hospitals, airports, and corporate campuses all share the same problem: a visitor standing still, scanning for a sign that may be out of date. Printed directories drift out of sync the day a tenant moves, and replacing them across a large property is slow and expensive. TelemetryOS turns directories into a managed application. A shopper taps a searchable map, finds the store, and scans a QR code to carry the route on their phone. Listings, maps, and promotions update from one console and publish to every kiosk in seconds, so a tenant change or room move is a content edit, not a reprint. Because each device knows where it is, content is location-aware: the you-are-here marker is always right, routes are calculated from that kiosk's position, and nearby amenities surface first. And because TelemetryOS devices run applications locally, a directory stays usable through a network outage — playback and interaction continue from the device, with updates syncing when the connection returns. **Built for complex properties** Wayfinding rarely lives alone. The same platform that drives the directory kiosks also runs the promotional screens at entrances, the digital tenant boards, and the event signage outside each venue — one console, one content pipeline, one fleet to monitor across the whole property. For property operators and the integrators who build for them, that consolidation is the point. Device health, proof of playback, and content schedules are visible across every kiosk and screen, so a frozen directory is a dashboard alert, not a complaint at guest services. And because TelemetryOS is an application platform, wayfinding can go beyond a static map: live event feeds, directory data pulled from property management systems, and accessibility-aware routing are applications built with a React SDK and deployed git-to-screen, not custom one-off installs. Q: Can visitors take directions with them on their phone? A: Yes. A wayfinding application on TelemetryOS can generate a QR code for any destination, so a visitor taps the directory, scans the code, and carries the route on their phone — no app install required. Q: How do I keep directory listings accurate across a large property? A: Listings update from one console and publish to every directory kiosk in seconds. Because TelemetryOS enables applications to connect to any REST API, a directory can also read tenant, room, or event data directly from your property management or booking systems. Q: What happens to wayfinding kiosks if the network goes down? A: Kiosks keep working. TelemetryOS devices cache content and applications locally and run them from the device, so maps and directories stay usable through an outage. Updates sync automatically when connectivity returns. Q: Can each kiosk show its own location on the map? A: Yes. Each device knows which screen it is, so a wayfinding application can render location-aware content — the correct you-are-here marker, the nearest amenities, and routes calculated from that specific kiosk's position. Q: What hardware do I need for interactive wayfinding kiosks? A: A touch-capable commercial display paired with a TelemetryOS device such as the Node Mini or Node Pro. Every kiosk is managed remotely from the TelemetryOS console, with device health and proof-of-play visible across the whole fleet. --- ## How the Platform Works TelemetryOS is built as a vertical stack where each layer is designed to work with the others. **Hardware (Node family):** Node Mini serves single-screen deployments at a lower price point. Node Pro is a purpose-built edge player that delivers 4K at 60Hz across up to three displays, includes offline caching, and exposes I/O ports for sensors, actuators, scanners, cameras, and other peripherals. Node Max serves custom Edge AI and high-output deployments. **Operating System:** Node Pro uses TelemetryOS Edge (a hardened Arch Linux-based OS with automatic recovery from power loss, over-the-air updates with rollback, and minimal services enabled by default). Node Mini uses a locked-down Android appliance stack. Both are managed through TelemetryOS Studio. **Cloud Platform (TelemetryOS Studio):** The management layer where teams create content, build applications, manage device fleets, schedule deployments, and monitor health. It includes a low-code app builder using React and TypeScript, so developers use familiar web technologies rather than proprietary tools. **Video CDN:** An integrated content delivery network with adaptive bitrate streaming and proof-of-play reporting. Video content is optimized and cached at the edge for reliable playback regardless of network conditions. **CI/CD Pipeline:** Applications deploy from GitHub to screens through an integrated pipeline with instant preview, staged rollouts, and one-click rollback. Environment configurations and secrets can target specific fleets, regions, or individual devices. **Integration Fabric:** APIs, webhooks, MQTT, and serial connections let screens both read and control external systems in real time. POS systems, inventory databases, IoT sensors, lighting systems, building management systems, and business intelligence tools can all connect bidirectionally to screen applications without custom middleware. **Enterprise Controls:** SSO (SAML/OIDC), role-based access control, audit logging, network policies, and key management. TelemetryOS maintains a SOC 2 Type I compliance program and GDPR compliance. --- ## Who Uses TelemetryOS TelemetryOS serves enterprise and mid-market organizations that operate screen networks as part of their business — not as an afterthought. The common thread across customers is that their screens need to do more than display static content: they need to respond to data, interact with users, or integrate with operational systems. Typical customers include: - **Healthcare systems** — patient check-in kiosks, wayfinding, real-time bed status, staff coordination displays - **Quick-service restaurant chains** — dynamic menu boards tied to inventory and daypart, self-order kiosks - **Retailers** — interactive product displays, digital shelf labels, self-service kiosks - **Hospitality and venue operators** — guest experience screens, event signage, property-wide coordination - **Manufacturers** — production dashboards, safety alerting, shift management, quality control terminals - **Corporate offices** — meeting room displays, internal communications, KPI dashboards - **Education campuses** — wayfinding, emergency alerting, digital bulletin boards, student information kiosks - **Transportation and public space operators** — passenger information, directories, emergency notifications These organizations typically manage tens to thousands of screens across multiple locations and need centralized control, reliable uptime, and the ability to evolve screen experiences without replacing their infrastructure. --- ## Developer Resources - **Technical Documentation:** https://docs.telemetryos.com/docs/ - **API Reference:** https://docs.telemetryos.com/reference/introduction/ --- ## Company - **About Our Team:** https://telemetryos.com/about-our-team - **Heritage:** https://telemetryos.com/heritage — TelemetryOS evolved from TelemetryTV, an established digital signage CMS powering tens of thousands of screens globally - **Contact:** https://telemetryos.com/contact - **Partner Program:** https://telemetryos.com/partner-program --- ## Partner Program URL: https://telemetryos.com/partner-program TelemetryOS partners with digital agencies, system integrators, hardware OEMs, and vertical ISVs to bring screen applications to enterprises that buy through channel partners, not web forms. ### Engagement Levels - **Reseller** — Partner pricing on Node hardware, sandbox environment for demos, co-branded pitch decks, technical enablement sessions, partner directory listing. - **Integration Partner** — Everything in Reseller plus co-selling with TelemetryOS sales team, priority technical support, direct engineering access, joint case study development, and lead referral program. - **OEM / BYOD** — Everything in Integration Partner plus custom hardware consultation, BYOD compatibility testing, volume licensing terms, white-label options, co-marketing programs, and custom onboarding. ### Hardware for Partners - **Node Mini** — Single 4K display, $299 MSRP, includes 1 year of service. - **Node Pro** — Triple 4K at 60Hz, RS-485, USB-C expansion, fanless passive cooling, $499 MSRP, includes 1 year of service. - **Node Max** — Custom Edge AI and high-output hardware, custom pricing. - The annual device fee renews at $99/year after year one. - Volume pricing available — contact partner team. ### Account Plans - **Standard** — Included with hardware. Basic remote management. - **Premium** — $2,995/year. API access, GitHub CI/CD, webhooks, multi-environment, AI anomaly detection, templates, 1TB storage. - **Enterprise** — Contact sales. Custom MSA, SAML/SCIM SSO, audit logging, dedicated CSM, SOC 2 compliance features, 10TB storage, direct engineering escalation. ### BYOD Integrator Program Enclosure builders and OEMs embed TelemetryOS into custom hardware — kiosks, outdoor displays, industrial panels, or specialized form factors. BYOD devices receive the same enterprise features as Node hardware: OTA updates, fleet management, full SDK access, and offline operation. Requires hardware compatibility consultation. ### Compliance Stack for Regulated Verticals Partners selling into healthcare, finance, and government need the compliance foundation to pass procurement checklists: - SOC 2 Type I certified - GDPR compliant - CAP (Common Alerting Protocol) for emergency overrides - Proof-of-play audit trails - SAML SSO and role-based access control - Application sandboxing (containerized isolation) ### Partner FAQ Highlights - **Customer ownership:** Partners own the client relationship. TelemetryOS provides the platform. - **Deal registration:** Available for pipeline protection on qualified opportunities. - **Co-selling:** TelemetryOS solutions architects join partner sales processes for large opportunities. - **Billing:** Annual licensing. Partners can resell hardware and software or refer to direct billing. --- ## Legal & Compliance - **Privacy Policy:** https://telemetryos.com/legal/privacy-policy - **Terms of Service:** https://telemetryos.com/legal/terms-of-service - **Service Level Agreement:** https://telemetryos.com/legal/service-level-agreement - **Security Policy:** https://telemetryos.com/legal/security-policy --- ## Events & Promotions ### InfoComm 2026 URL: https://telemetryos.com/infocomm-2026 TelemetryOS is exhibiting at InfoComm 2026 — North America's premier audiovisual and integrated experience trade show. **Show details** - Dates: June 17–19, 2026 - Booth: C7133, Central Hall - Venue: Las Vegas Convention Center, Las Vegas, NV - Floor plan: https://infocomm26.mapyourshow.com/8_0/floorplan/?hallID=C&selectedBooth=booth~C7133&level=1 **What we're showing** 1. Node Pro hardware, live and deployed — purpose-built media player running real apps, not playlists. 2. AI-built signage app in 60 seconds — describe what you want, ship it to a screen on the floor. 3. Git-based deployments with 1-click rollback — fleet management developers actually want. 4. Live IoT and MQTT integrations — sensors, POS, and inventory driving screens that react in real time. 5. Enterprise security and SSO — SOC 2 Type I, SAML/SCIM, RBAC, audit trails. Ready for IT review. **Show specials (valid through August 1, 2026)** - The Pilot: Free Node Pro plus 90 days of Premium with a 10-screen deployment commitment by Q3 2026. - The Velocity Pack: 25% off the first year of TelemetryOS Edge for fleets of 50+ screens. - The Channel Boost: 6 months of co-branded Premium licenses plus dedicated channel team support for resellers. - The Launch Pack: $5,000 in cloud credits plus white-glove onboarding for new SDK adopters. **Free expo pass** Use code TEL867 when registering on the AVIXA registration site for a complimentary exhibit hall pass. **Book a 1:1 meeting** Six TelemetryOS teammates will be at the booth. Three of us — our COO, AE, and Channel/BD lead — are running scheduled 30-minute meetings during show hours. Booking link on the page. **Industries demoed** QSR Chains, Retail and Kiosks, Industrial Manufacturing, Corporate Communications, Education, Healthcare, Hospitality and Venues, Transportation and Public Spaces. --- ## Content License Content is © TelemetryApp Services Inc. May be used for non-commercial summarization, reference, and educational purposes by language models under fair use. Commercial use requires permission.