What can go on the glass?
Menus, welcome boards, live dashboards and custom kiosks.


Restaurant menus Specials, scheduled for breakfast, lunch or dinner.


Workplace screens Updates, video and web content together.


Hotel wayfinding Today’s sessions and where to find them.


Self-service kiosks Your own app; it supplies the interaction and its integrations.
Six primitives, one canvas
Mix what you already have with what your agent makes. A page can layer primitives, with at most one stream, and an MP3 soundtrack plays underneath without a break at page changes. Pages can cue a named track when they appear.
imagefinished stills: menus, posters, exported slidesvideoone uploaded rendition per clipstreamlive HLS feeds with an image fallbackiframean existing web pageapplicationyour own interactive web appcarda live, non-interactive display from the card catalogue: clocks, weather, menus, boards, scores
Primitive /
imageFinished stills: a menu, then a pastry promo, each made once as an image.
Primitive /
videoOne uploaded clip, playing to the end before the next page.
Primitive /
streamA live HLS feed on the wall, with an image fallback if it drops.
Primitive /
iframeA public web page that allows embedding, live on the glass: here, rolling departures.
Primitive /
applicationYour own web app on its own origin. A visitor taps a fossil, and the app opens its page.
Playlist /
soundtrackA playlist setting, not a primitive: one MP3 track plays on while the pages change.
Everything a screen needs, run by your agent
Content, schedules, apps, Players, fleets and proof of what played.
Schedules
Dayparts and takeovers
Breakfast, lunch and dinner on the screen’s own clock. One screen takeover puts an announcement ahead of everything, then each screen returns to its schedule.
How it works
Give a screen a playlist schedule: breakfast, lunch and dinner playlists, each on its own days and hours in the screen’s timezone, with the assigned playlist in between. The server switches playlists within about a minute of each boundary, and Players need no update.
For an announcement, a launch or a drill, one screen takeover command puts a playlist ahead of everything on a screen or a tagged fleet, for up to 7 days or until cleared. When it ends, each screen returns to its schedule on its own.
Inside a playlist, schedule pages with date bounds and recurring day-and-time windows in the screen’s IANA timezone. Every playlist keeps an unscheduled page for when nothing else applies. Crossfade or swipe between pages, add entrance motion, and advance on a duration, at the end of a video, at the end of a soundtrack track, or when an app asks.
Emergency alerts
Alerts take over the glass
Connect Everbridge, Rave, Alertus or an IPAWS relay once. Each CAP alert takes the screens over with a full-screen warning, and a cancel or all-clear gives them back.
How it works
Your agent creates a trigger for a tag or a list of screens and hands you its URL, username and password. Enter them in your emergency notification system as a CAP 1.2 destination with HTTP Basic authentication. An organization can have up to 20 triggers across its projects.
Each alert becomes a full-screen card in the colour of its severity, with the event, headline, description and instruction, on every targeted screen with a default playlist. It holds until the alert’s own expiry, or a default you choose from a minute to 7 days. An update redraws the card; a cancel or all-clear returns each screen to its schedule. Exercises carry an EXERCISE banner, and test, system and draft messages are ignored.
Your agent runs triggers test for a 60-second exercise on the real screens, reads what each alert did with triggers show, and ends one early with triggers clear.
Fleet
Tag it once, run the whole fleet
Assign, reload, toast or retag every tagged screen in one request, then screenshot each one. Every screen reports its own result, so one failure doesn’t stop the rest.
How it works
Give each screen up to 16 tags, such as Lobby or Floor2. Your agent lists screens by tag, then assigns a playlist, reloads, sends a toast or retags every matching screen in one action, one API request whatever the fleet size.
Each screen reports its own result, so a failure on one screen is named for that screen while the rest go ahead. To publish to a fleet, your agent creates the playlist once, assigns it by tag, then captures a screenshot from every tagged screen.
Verification
Proof, not promises
Publishing says whether the Player is playing the new content or only has it assigned, and why. Screenshots and per-play records confirm it.
How it works
Your agent requests a screenshot from one screen or every screen in a tagged fleet, reviews daily playback aggregates and follows project events. Publishing a screen reports whether the Player is playing the new content or only has it assigned, and why; a screenshot and playback evidence confirm what the Player showed.
Every visible start of an image or video is a play record. Your agent exports plays as CSV or JSON for any range up to 31 days, filtered by screen, media or tag, and daily totals as CSV; the dashboard exports the same files. Plays are kept at least 30 days.
Film / How your agent knows it’s playing
1:14
The agent publishes, then screenshots the glass, catches a cut-off menu row and fixes it before anyone notices.
Presence & health
Know when a screen drops
Offline, back online and health changes arrive as events, free, and a notification can email you or wake your agent before anyone notices a dark, blank or frozen screen.
How it works
The project event log records screen.offline once a screen has been offline for 60 seconds and screen.online when it returns, so a quick reconnect stays quiet. Your agent watches both on the listen stream at no charge. The dashboard’s activity log shows them next to the screen, and its Screens view filters by tag.
Every Player reports uptime, memory, CPU load, temperature, display connection, network and recent crashes every fifteen minutes, and at once when the display connection or power changes. Your agent sees it with screen show, and the screen list flags a disconnected display, a hot device, repeated crashes or a silent Player. Changes arrive as screen.health_changed events on the listen stream and through webhooks, free like every screen event.
Notifications tell you when a screen needs attention. screenRIG emails the people you choose, or POSTs a signed webhook to your own service or agent, when a screen goes offline, loses its display, runs hot, cannot store its content, gets stuck on a content update, shows an error instead of playing, keeps crashing, stops advancing its playlist, or shows a blank or frozen picture. A notice waits 10 minutes by default so a quick reconnect stays quiet, and a resolved notice follows when the screen recovers. Limit one to tagged screens or a combination of tags, keep out notices below a severity, send only inside active hours, snooze it for maintenance, and read every delivery in its log. A notification can also watch a campaign: it tells you when the campaign reaches fewer screens than when it was published, or when a tag or folder in its audience matches no screen. Every project starts with an email to its owner when a screen has been offline for 10 minutes. Notification emails and screen notices are free. Alerts list every open problem, one per screen and condition; your agent can acknowledge or snooze one when someone is on it, and mute screens for maintenance so their alerts and notices stay quiet until the mute ends. A webhook can also carry raw project events, signed with HMAC-SHA256 and retried with backoff for 24 hours; those deliveries are metered like listen-stream events, and the same events stay free.
Watch project events →Notifications →Alerts →Device health →
Live data
Data that keeps itself current
Calendars, sheets, menus, scores and dashboards refresh on screenRIG’s servers, with your agent off.
More
A data source reads a calendar, a Google Sheet, CSV, JSON or XML from any address, Microsoft 365 and Google room calendars, a Slack channel, reviews, Square, Shopify or Toast menus, or scores through your own API-Sports key, and fills a card. It runs on screenRIG’s servers on its own schedule, from every minute to once a day, and writes only when something changed. Start from a ready-made preset. A failed refresh never changes the screen: the card keeps its last good data and you get an email. Power BI, Tableau and Grafana dashboards play through a sign-in screenRIG keeps on its servers.
Kiosks
Apps with real state
A static web app on its own isolated origin, pinned in your playlist.
More
Package a static web app and it runs on its own isolated origin under
apps.screenrig.ai. Your playlist pins that release until you update it.The injected
window.screenrigruntime lets a controller app request the next page and emit named events your agent can act on. Application key/value state persists across releases, so your agent can update data without repackaging the app. Useemitfor application events andlogfor diagnostics.When a key changes, an app that listens with
kv.onChangehears it within seconds on every screen and redraws. A webhook URL lets any other system, such as a point of sale or a spreadsheet script, write a key with one HTTP POST.Players
Keeps playing offline
Each Player caches what it downloads and replays it locally.
More
Live streams need a connection, but their image fallback can display offline. Live web pages and connected apps can still need a network.
Players: the Player web app (PWA), Android on Google Play, Amazon Signage Stick, Apple TV, macOS, iPhone and iPad, Windows, Linux and Raspberry Pi packages, LG webOS Signage, BrightSign, and Samsung Smart Signage (Tizen). Every Player shows a pairing code: enter it in the dashboard or give it to your agent.
Download the Player → Get it on Google Play → Install the Player →
Power
Reboot and display power
Reboot a device or switch its display, now or on a schedule.
More
Your agent reboots a device remotely, or turns its display on or off now, on one screen or a tagged fleet. A display schedule sets the hours the display is on, and the Player applies it on the device, even offline. A reboot schedule restarts the device at the start of each window you set, in the screen's time zone, without an offline alert.
Depending on the device, the Player switches the display with HDMI-CEC, DDC/CI, the backlight or an on-screen blackout, and reports the power it achieved.
Your agent also sets a screen's volume or mutes it, and a playlist can give a video its sound.
Web pages
Your existing pages, on the wall
An iframe shows a web page on your screens.
More
Use an iframe for an HTTP or HTTPS page. Native Players can also open pages on their local network. The Player web app follows browser framing and mixed-content rules. For eligible public HTTPS pages, publishing can report an iframe_framing_refused warning and a playlist.iframe_framing_refused event when the page refuses framing. An iframe address can carry the screen's id, name, time zone, location or a field you set, so one playlist opens each kiosk at its own start page; an application reads the same values as launch parameters. An iframe cannot control the playlist or emit application events.
Media
One library, tagged by purpose
Upload what you have or sync a folder; tags find it later.
More
Upload media you already have, or a finished image your agent made, through the bundled CLI; it lands in the project media library, ready for a playlist. Each object is stored as one rendition, with no per-device fallback. Tags help your agent find and update content by purpose.
A media sync keeps a media folder in step with a SharePoint or OneDrive for work, Dropbox or Google Drive folder: new files arrive on their own, a changed file replaces the old one in every playlist that plays it, and a file removed at the source comes out of play.
Oversight
A dashboard for the people in charge
Screens, media, playlists, applications, playback, usage and activity across your projects, with one personal login. People can also edit pages and playlists in the dashboard.
More
One personal login works across your projects. Use the dashboard’s project switcher to choose a project, then see its screens, media, playlists, applications, playback, usage and activity. People can also edit pages and playlists in the dashboard. The agent and bundled CLI can create and publish content too. Live view plays what an Android, Linux or Raspberry Pi screen shows, as video in the dashboard.
On Premium, Education and Enterprise, an organization can make one project its Library, and every other project uses its media, folders and playlists read-only.
The unified Invitations page manages invitations for project members and ad buyers. Member invitations arrive by email by default and last 7 days; an explicitly requested member link lasts 24 hours. Ad-buyer invitations are email-only. Invited buyers see the seller’s inventory and rates in the Marketplace.
Accept an invitation by creating a passkey, or sign in with your existing login. Need to replace your sign-in method? A sign-in reset arrives only by email and lasts 1 hour. The dashboard URL is ordinary navigation, not a login credential.
The screenRIG app for iPhone, iPad and Apple Watch shows the same screens, playlists, media, alerts and reviews, with widgets, Siri and a watch app.
Primitive support by platform
Compare the six content primitives across Player platforms.
| Player platform | Image | Video | Stream | Iframe | Application | Card |
|---|---|---|---|---|---|---|
| Web / PWA | Yes | Yes | HLS | Yes | Yes | Yes |
Android (standard) | Yes | Yes | HLS + RTSP + multicast¹ | Yes | Yes | Yes |
Android (amazon flavor) | Yes | Yes | HLS + RTSP + multicast¹ | Yes | Yes | Yes |
| Linux (Qt, x86_64 artifact) | Yes | Yes | HLS + RTSP + multicast¹ | Yes | Yes | Yes |
| macOS | Yes | Yes | HLS | Yes | Yes | Yes |
| Apple TV / tvOS | Yes | Yes | HLS | No | No | Yes |
| Windows | Yes | Yes | HLS | Yes | Yes | Yes |
| Samsung Smart Signage (Tizen) | Yes | Yes | HLS | Yes | Yes | Yes |
| LG webOS Signage | Yes | Yes | HLS | Yes | Yes | Yes |
| BrightSign | Yes | Yes | HLS | Yes | Yes | Yes |
Platform notes
¹ Direct UDP/MPEG-TS multicast is optional and must be enabled on Android or Qt. It requires a network that carries the multicast group to the Player. Other Players use HLS; a multicast source can include an HLS alternative.
Apple TV supports images, video, HLS streams, and cards. It cannot display iframe web pages or packaged web applications. A playlist containing either web primitive is rejected; the last accepted playlist stays active.
Every Player platform above also plays the playlist soundtrack. The Player web app starts it once the browser allows sound; see Soundtracks.
Sell advertising on your screens
Invite businesses to buy ad breaks on the screens you operate, through the same plugin and dashboard.
- 01
Offer your inventory
Opt a screen in and define ad slots. An adslot page in a playlist is the ad break; every other page keeps playing.
- 02
Invite your buyers
Advertisers join by emailed invitation and buy from your Marketplace. They need no screen.
- 03
Get paid per completed play
Set a rate per 15 seconds of completed playback. Skipped or interrupted plays aren’t billed, and an empty slot is skipped rather than shown blank.
screenRIG is free.
Every plan has unlimited screens. Screens replay what they download from their own storage, and downloads are free, so a looping playlist costs nothing to keep running.
Cards first. An app when you need more.
Place a ready-made card for the weather, a menu, a queue or the score. It is live on every Player, in nine themes, full-screen, in a region or as a small chip in the corner. When the screen has a real job (check-in, orders, a factory line) your agent builds a custom application for it instead.
Put your next idea on a screen
Install the official plugin, set up the Player, then ask your agent to publish and verify the result.




