Security

A screen in the room is never a key to your systems.

The screen shows a number. Everything that could spend money, read your data or change your systems stays somewhere else, behind controls we test on every change.

How your numbers reach the screen

Your cloud or APIRead-only access
MetriliteChecks every request
Your screenHolds no secrets

In detail

What we hold, what we never hold, and how each part is checked.

  • Your API keys, locked away

    Keys and tokens for your own APIs are stored encrypted in AWS Secrets Manager, written once and never shown again or logged. We read your endpoint with an HTTPS GET from a locked-down server that refuses private and internal addresses, and the screen receives only the values you picked.

  • Read-only billing access

    On AWS the connector runs in your own payer account with a billing-read role, and we never hold your keys. On Azure and Google Cloud a small function runs in your own subscription or project with its own read-only identity and sends us only your cost totals; we get no access to your tenant or project. Claude's cost API needs an Admin key and Anthropic has no read-only one, so we ask for a dedicated key you can revoke in the Anthropic Console at any time: we store it encrypted, only the Claude reader can open it, and our code calls only the cost and usage reports. Offboarding removes everything we created.

  • No secrets on the screen

    Each screen holds one narrow token that can only read its own status. It arrives over an encrypted device channel after you claim the screen, and rotating it revokes the old one at once.

  • An identity per screen, signed updates only

    Each screen makes its own private key on the chip and talks to the cloud over mutually authenticated TLS. Firmware is signed with a key held in a hardware security module; the screen checks the signature, refuses older images and rolls back a bad update by itself.

  • A console that keeps tenants apart

    Sessions last 60 minutes and signing out revokes them. Every request is checked against the account that owns the screen, with per-user rate limits. You can export or delete your data from the console.

  • Checked on every change

    Each release passes static analysis, dependency vulnerability scans, infrastructure policy checks and sanitizer-run firmware tests before it can ship. No third-party scripts or trackers run on this site.

Next, before general availability: secure boot and flash encryption on every screen, so the firmware and the keys cannot be read or replaced over USB.

Put your numbers in sight.

Create an account, connect a source, and claim your screen in minutes.