Live data on your screens, kept current

Give your agent the address, the key or the calendar once. screenRIG reads it on a schedule, from every minute to once a day, and writes to the screen only when something changed. Each source runs on screenRIG's servers with your own access, so your agent does not have to stay on.

Public data needs no account: screenRIG fetches and caches it, and each app shows the credit its source asks for. Data sources has every setting.

Give a system an app's webhook address, and the screen changes within seconds of the event. GitHub, Slack, Linear, Vercel and Asana sign what they send, and screenRIG checks each signature before anything reaches a screen. Any other service that signs its posts with a shared secret works the same way.

Your agent's apps are your content. Anything your agent can read with its own access, such as your email, documents, help desk or CRM, it can put on a screen. If your agent runs on a schedule, ask once and it updates the app at the pace the data moves. Each update carries an expiry, so a missed run never leaves old numbers up: the app clears, and you get an email.

1. You

   Every morning at 8, put yesterday's new support tickets and the three oldest open ones on the support team's TV.

2. Agent

   Scheduled. I'll read the help desk at 8 every morning and update the board. Each update lasts 36 hours, so if a run is missed the board clears instead of showing old numbers, and you get an email.

A failed refresh never changes the screen. The app keeps its last good data for the period you choose, from a minute to a week, then clears on every screen, offline ones included, and the page you set as a fallback plays in its place. You get an email when a refresh fails and again when the data runs out, and the Data sources page in the dashboard shows which source is failing.

Power BI, Tableau and Grafana dashboards play on your screens through an account screenRIG keeps on its servers, so a screen never shows a sign-in page. A dashboard behind any other sign-in plays as a picture: screenRIG signs in with a read-only account, including the code from an authenticator app, and refreshes the picture on a schedule. The dashboard guide shows another way: your agent reads the numbers and draws them big.

Point a sync at a SharePoint or OneDrive for work folder, or a Canva design, and your media library follows it. 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.

Does my agent need to stay running?

No. Sources, public data and webhooks run on screenRIG's servers, so your screens stay current while your agent is off. Your agent sets them up, and the dashboard shows the state of each one.

How often does the data refresh?

Each source has its own schedule, from every minute to once a day: a Slack channel every minute, calendars every 5 minutes, Google reviews every 6 hours. Pushed data arrives within seconds. A refresh that finds nothing new writes nothing, so your screens are not woken for it.

Where are my keys kept?

Sealed on screenRIG's servers. A key is shown back only as a hint and never appears in a log, an error or the project's event log. Use a read-only key wherever the service offers one.

Can it read our own system?

Yes. A source reads any web address that answers with JSON, CSV or XML: GET or POST, GraphQL, headers, API keys, OAuth client credentials and results that come in pages. Your agent maps the answer onto an app and previews it before anything reaches a screen.

Can each screen show different data?

Yes. One sheet or feed can hold a row for each screen, such as each store's prices or each room's next event, and every screen shows only its own row. One playlist serves them all.

What does it cost?

screenRIG is free. Pay only if you want more. Syncs are free, and what a source writes counts toward storage like any other data. See pricing.

Start free, pair a screen, and ask your agent for the data you want on it.