Browser VIEW
The universal display runs in a browser without installation. A display code, GuestCode or guest link opens only its assigned VIEW area. Control and display use separate sessions. Concurrent browser displays are counted through short-lived server-side leases.
Chromecast
After creating a display code, an ADMIN device can select a registered Custom Web Receiver. The receiver renders the display itself; no video of the control interface is transmitted. A Cast App ID, receiver registration and a compatible device are required.
Versioned HTTP API
API tokens are bound to a project and an ADMIN area. Read and control permissions are assigned separately. Write actions require the expected state version and an idempotency key. Version 1 covers timer state and control actions; complete external plan management is not included.
Bitfocus Companion and Stream Deck
The base Companion module provides actions, variables, feedbacks and presets. The buttons and functions in use are configured in Companion. The API client and module contract are covered by automated tests; final acceptance with representative Stream Deck hardware remains open.
Verification limits
Browser VIEW and software contracts have been tested locally. Chromecast requires a receiver ID registered for production. Stream Deck requires Companion and physical hardware. Separate server-side counting of a Cast receiver in addition to the sending browser session remains open.