Technical Reference

This section provides essential technical reference information for working with TelemetryOS, including terminology, browser requirements, and data residency options.

Platform Terminology

Core Platform Concepts

TelemetryOS

A vertically integrated platform for screen networks that transforms connected screens from passive displays into active components of your product experience. At the edge it uses Node Pro, a hardened player with device lockdown, offline caching, and rich I/O for sensors and peripherals. In the cloud it provides a managed platform that handles fleet management, policy, updates, monitoring, and a low-code application layer.

*See also: Vertical Integration, PaaS, Node Pro, TelemetryOS Edge, and TOS Player.

Connected Screen

A physical display operated by a Node Pro device that is enrolled in TelemetryOS and managed through the administration interface. Connected screens receive content and application updates over the network, cache assets for offline playback, report health and playback telemetry, and can respond to data, schedules, and overrides. In TelemetryOS, device, content, and app settings determine what a connected screen shows and how it behaves.*

Vertical Integration

The core innovation of TelemetryOS where a single vendor controls hardware (Node Pro), OS (TelemetryOS Edge), runtime (TOS Player), and cloud orchestration, eliminating brittle seams that slow rollouts and create field failures.

PaaS (Platform as a Service)

TelemetryOS's managed cloud platform that handles fleet management, policy enforcement, updates, monitoring, and application deployment, providing enterprise-grade control without the complexity of custom infrastructure.

Edge Computing

Processing and data handling at the device level (Node Pro) rather than in the cloud, enabling offline operation, real-time responses, and reduced network dependency for critical functions.

API Token

A machine-readable credential (typically a long, random string) that an application sends with API requests to prove its identity and gain authorized access. It is used for authentication and authorization and commonly sent in the Authorization: Bearer HTTP header. The token may include scopes/permissions and an expiration time, and is treated as sensitive data — store securely and rotate if compromised.

Ask AI

A customer-facing feature that allows natural language queries against TelemetryOS documentation, content, and device management functions. Designed to simplify troubleshooting and onboarding.

CI/CD (Continuous Integration/Continuous Delivery) Pipeline

An automated set of processes that takes code changes from version control through build, test, and deployment so software can be delivered to users quickly, reliably, and repeatedly.

• Continuous Integration (CI) — developers frequently merge changes into a shared branch; automated builds and tests run to catch integration issues early.
• Continuous Delivery (CD) — every change is automatically prepared for release; deployments to staging or production are manual but repeatable.
• Continuous Deployment (also CD) — like Continuous Delivery but deployments to production are fully automated after passing pipeline checks.

Content Management System (CMS)

The core of TelemetryOS's platform, enabling users to create, schedule, and deploy connected screens content. The module within TelemetryOS for organizing, scheduling, and delivering signage playlists. Supports navigation via List and Map views, overrides, and staged downloads for reliable delivery.

Device Grouping

Organizing devices into logical groups for simplified content assignment and management.

Studio

TelemetryOS's visual composition tool where users create screen layouts combining applications, media, text, and other elements. Applications built with the SDK run within Studio pages.

Git-To-Screen

The runtime on TelemetryOS Edge that executes screen applications and media.

LMS (Large Model Service) Text

AI feature that integrates large language models into TelemetryOS workflows. This capability enables programmatic querying, transformation, and content generation within the platform.

Kiosk Mode

A device configuration that locks a screen to a single application or experience and prevents end-users from accessing the underlying OS, other apps, or device settings. TelemetryOS supports kiosk deployments through the CMS (app assignment, remote monitoring, logs, and fallback content), enabling secure, managed single-app experiences at scale.

Media Player

Software provided by TelemetryOS to run on customer-provided hardware for digital signage purposes. It handles content playback, scheduling, and communication with the TelemetryOS cloud.

Playlist

A sequential arrangement of content items (images, videos, apps, etc.) scheduled for playback on connected screens devices.

Provisioning

The secure, centralized process of enrolling a device into TelemetryOS. It replaces older "pairing" workflows and ensures consistent configuration, monitoring, and management at scale.

Provisioning Key

A short-lived, cryptographic token used to securely register and bind a new device to a TelemetryOS tenant during initial onboarding. It is used to authenticate and authorize a device during first-time setup to prevent unauthorized enrollment. It is a single-use or limited-use, time-limited (TTL), tenant- or group-scoped, and invalidated once consumed. The key is generated generated by an admin or API, delivered to the device (QR, USB, manual entry, etc.), used during provisioning and then revoked/expired. It is recommended to treat as a secret, keep TTL short, limit scope, audit issuance/consumption, and rotate/revoke when compromised.

Schedule

A set of rules dictating when and how content (e.g., playlists) will be displayed on specific devices or groups.

Software & Runtime

AI Scaffolding

TelemetryOS's framework for AI-assisted development that leverages AI to accelerate software development. Includes AI-assisted code generation, natural language-to-code conversion, content generation templates, and integration with tools like GitHub Copilot and OpenAI Codex.

Content Caching

The ability to store content locally on devices via a global Content Delivery Network (CDN), ensuring offline playback.

Custom WebApps

Web-based applications integrated with TelemetryOS, allowing custom workflows, signage solutions, and kiosk applications using APIs and web frameworks.

Device Management

Tools to manage devices at scale, including provisioning, monitoring, logging, and configuration in real time.

Data Residency

Compliance with regional data regulations by supporting local data storage and processing, ensuring sensitive information stays within geographic boundaries.

TOS Player

TOS player is TelemetryOS’s purpose-built screen endpoint: the Node Pro hardware running the TelemetryOS Edge OS with the TOS Player runtime.

Telemetry SDK (JavaScript SDK)

A modular development toolkit (@telemetryos/sdk) that enables developers to build interactive applications for connected screens using familiar web technologies. For SDK package details, see SDK Packages.

Application Components

TelemetryOS applications are composed of four distinct components. For complete component documentation, see Application Components.

Storage Scopes

The SDK provides intelligent data storage with four distinct scopes. For complete storage scope documentation, see Storage and Communication Scope.

Turnkey App Library

Pre-built apps for common use cases like news feeds, weather updates, RSS feeds, and more.

Low-Code Development

A development approach in TelemetryOS that allows users to build applications with minimal coding through templates, visual editors, and AI assistance, while still providing access to full SDK capabilities for advanced customization.

DevOps Discipline

The application of software development practices to screen deployments, including push-to-deploy workflows, instant preview, staged rollouts, one-click rollback, and built-in monitoring and alerts.

IoT & Data Fabric

TelemetryOS's built-in integration capabilities that enable screens to respond to real-time data and sensors through APIs, webhooks, MQTT, and serial connections without custom glue code.

Proof of Play

Analytics and logging that tracks when content is displayed on screens, providing verification for advertising campaigns, compliance requirements, and performance measurement.

Emergency Overrides

Priority content or alerts that interrupt normal playlists and applications, ensuring critical information (safety alerts, emergency notifications) is displayed immediately across all relevant screens.

Failsafe Content

Default playlists or applications that automatically activate when primary content fails to load or when devices lose connectivity, ensuring screens never display blank or error states.

Staged Rollouts

The ability to deploy application updates or content changes through progressive expansion, starting with a subset of devices before expanding to the full fleet, minimizing risk and enabling testing at scale.

Security and Compliance

Audit Logging

A detailed log of actions and changes made within the TelemetryOS platform for security and compliance purposes.

Permissions and Groups

A feature for managing access control across teams and user roles.

SOC 2 Compliance

A rigorous standard ensuring that TelemetryOS adheres to best practices for data security and privacy.

SAML Authentication

A single sign-on (SSO) protocol for secure, enterprise-grade authentication.

RBAC (Role-Based Access Control)

A security model that restricts system access based on user roles and permissions, ensuring users only access functions and data appropriate to their responsibilities.

SSO (Single Sign-On)

Authentication method that allows users to access multiple applications with one set of login credentials, improving security and user experience.

Data Residency

Compliance with regional data regulations by supporting local data storage and processing, ensuring sensitive information stays within geographic boundaries.

Network Policy

Security controls that govern how devices communicate with the TelemetryOS platform and external services, including firewall rules, VPN requirements, and traffic encryption.

Hardware

Node Pro

Telemetry's flagship media player device engineered for high performance, robust reliability, and deep integration with the TelemetryOS platform. A dedicated hardware endpoint designed for professional, 24/7 connected screens and screen applications.

For complete hardware specifications, see What is Node Pro?

Node Pro Requirement

TelemetryOS exclusively runs on Node Pro hardware, ensuring consistent performance, security, and support across all deployments. This standardization eliminates compatibility issues and provides enterprise-grade reliability.

Hardware Acceleration

Native GPU decoding and processing capabilities in TOS Player that dramatically reduce CPU utilization during 4K video playback and enable advanced features like computer vision models and real-time graphics.

Fanless Design

Node Pro's silent, passive cooling architecture that ensures continuous commercial operation without mechanical failure points, making it ideal for customer-facing installations.

Enterprise I/O

Comprehensive input/output capabilities in Node Pro including USB 3.2/2.0 ports, RS-232/485 serial connections, GPIO pins, cameras, sensors, and industrial controllers for direct hardware integration.

Browser Requirements

The TelemetryOS administration interface (app.telemetryos.com) requires a modern web browser with support for current web standards including WebSockets, WebRTC, and ES6 JavaScript.

Supported Browsers

Technical Requirements

The administration interface utilizes modern web APIs that require:

• JavaScript ES6+ support
• WebSocket connections for real-time updates
• LocalStorage for session management
• Service Workers for offline capabilities
• WebGL for advanced visualizations

Troubleshooting

If you experience issues with the administration interface:

1. Clear browser cache: Remove cached data from the last 24 hours
2. Disable extensions: Test in incognito/private mode
3. Check network: Ensure WebSocket connections aren't blocked
4. Update browser: Install the latest version

For persistent issues, use the in-app chat and provide your browser version and error details.

Current Regional Availability

In our initial release, TelemetryOS is available exclusively in the United States (US) region. All new accounts will be automatically directed to the US data center for storage and processing. This ensures consistent performance and compliance with our security standards during the launch phase.

Why US-Only for Now?

• Focused Launch: We're starting with the US to deliver the best possible experience and reliability.
• Scalable Foundation: This allows us to optimize our infrastructure before expanding globally.
• Security and Compliance: All data is handled with enterprise-grade security, regardless of region.

Important: Data residency selection is a one-time choice made during account creation and cannot be changed afterward. Please ensure the US region meets your needs at this time.

Upcoming Regions

We're actively working to expand data residency options to better serve our global users. The following regions are planned for future releases:

• Canada
• Europe
• United Kingdom
• APAC (Asia, Australia, New Zealand)

These regions will provide localized data storage while maintaining TelemetryOS's high standards for security, performance, and compliance.

Need a Specific Region?

If your organization requires data residency in a region not yet available, please use the in-app chat to discuss your needs and get updates on our rollout timeline.

If you have specific regional requirements, please reach out to ensure TelemetryOS fits your data residency needs as we expand.

Data Security Across Regions

Regardless of the region, TelemetryOS employs robust security measures:

• End-to-end encryption for data in transit and at rest
• Compliance with industry standards (e.g., SOC 2, GDPR where applicable)
• Regular security audits and updates

For more details on our security practices, see our Security and Compliance documentation.

Best Practice: Review your data residency requirements before creating your account. If you have questions, our support team is ready to assist.