Skip to content
- The media server runs on the venue’s own network and works offline. It sends nothing to the internet by
default. Optional outbound traffic: cloud token verification keys (JWKS, cached on disk) when the installation is
linked to the cloud, cue actions to OSC / HTTP destinations on the configured allow-list (default: private
networks only), and gateways / drivers you enable.
- Stored data (under
/var/lib/freedome): venues, calibration, shows, media you upload, API key hashes (argon2 —
secrets are never stored), user accounts with password hashes, session refresh-token hashes, an audit log of
administrative actions (who, what, when), scenario key-value data. Camera frames uploaded for calibration are stored
as blobs of the calibration job and can be deleted with it.
- Logs go to the system journal. Tokens and secrets are never logged (only key ids).
GET /api/v1/system/config
redacts secrets.
- Connected client apps may register device capabilities and post sensor telemetry (
/api/v1/clients) only when the
app does so explicitly; this data stays on the server.
- Removing the package with
purge deletes configuration and keys; FREEDOME_PURGE_DATA=1 also deletes the data.