• Connect your repo — or just upload a zip. Link your GitHub repository for automatic builds on every push, or simply upload a zip file for simpler workflows. GitHub is recommended for advanced use cases — use different branches to deploy to QA devices from develop and production devices from main.
• Push a commit. We build it. Every push triggers a cloud build. Real-time build log streaming shows you exactly what's happening. Build artifacts are stored, versioned, and ready for deployment — no build servers on your side.
• Automatic deployment to devices. New builds deploy to every assigned screen automatically. Target specific device groups, run staged rollouts to a subset first, or hold for manual approval. You control the rollout strategy.
• One-click rollback to any version. Every build is versioned and stored. Roll back to any previous version instantly — no redeployment, no rebuild. Zero-downtime rollback across your entire fleet.

Advanced Workflows

• Branch deployments for QA and production. Map Git branches to device groups. QA screens track the develop branch, production screens track main. Each environment builds and deploys independently — test on real hardware before promoting to production.
• CLI publish for advanced workflows. tos publish from the command line or an AI agent — version bump, archive, upload, cloud build, and deploy in one command. Integrate into any automation pipeline.