Deployment Model

TelemetryOS uses a Git-to-Screen deployment model designed to feel natural for development teams already using Git. Code lives in version control. Pushes trigger builds. Builds produce deployable artifacts. Artifacts reach devices through playlists.

How It Works

Developer pushes code → GitHub/Git repository
     ↓
TelemetryOS build servers compile the application
     ↓
Build artifacts packaged and versioned
     ↓
Artifacts distributed to devices via playlists
     ↓
Devices download and run the application locally

After registration in Studio, TelemetryOS clones the repository, installs dependencies, runs the build command, and packages the output. The first version is immediately available for deployment. Subsequent pushes to the connected branch trigger new builds automatically. Builds typically complete in one to three minutes.

Reaching Devices

Applications reach devices through playlists. In the Studio page editor, add the application to a playlist page and configure its instance settings in the sidebar. Assign the playlist to devices or device groups, and the content appears on screen.

Version Management

Studio maintains a complete version history for each application. Every successful build produces a new version. You can:

• Deploy specific versions to different device groups (production devices on a stable release, test devices on the latest build)
• Compare what changed between versions
• Roll back to any previous version with a single click — the change propagates to devices within seconds

Environment Branching

The Git-based workflow supports environment separation naturally. Connect a develop branch to test devices, a staging branch to QA displays, and main to production. Each environment is a separate application definition in Studio pointed at a different branch of the same repository.

This means the same branching strategies used for web applications work here. Feature branches let developers test in isolation before merging. Semantic versioning tracks what's running where.

Rollback

Rollback is immediate — select a previous version in Studio and it propagates to devices within seconds. There's no manual file copying, USB drives, or device-by-device updates.

Connection Methods

GitHub Repository is the recommended approach. Authorize the TelemetryOS GitHub App, select a repository and branch, and the platform auto-detects build settings from telemetry.config.json. Every push triggers a build automatically.

Git Repository works with any Git provider — GitLab, Bitbucket, or self-hosted. Provide the HTTPS URL and authentication credentials for private repositories.

ZIP Upload is available for quick testing or environments without source control.

For the full deployment walkthrough, see Deploying.