Choose the right architecture
XTV Graphics supports multiple architectures depending on workflow, broadcast requirements, and IT policies. Every option keeps data and media on separate channels for control, performance, and security.
In addition to on-air graphics delivery, XTV can also feed website content and digital channels so the same dataset powers web and broadcast.
Available options include XTV CDN, data-only exports to Google Drive, customer object storage + customer CDN (e.g., R2/Cloudflare), and on-prem XTV Station for local sync.
Baseline architecture (XTV CDN)
Data is served by public endpoints protected with API keys. Media is delivered by the XTV CDN using opaque UUID filenames. Fast to deploy and easy to operate.
- Data served by XTV Server public endpoints (API key)
- Media delivered by XTV CDN with opaque UUIDs
- Best for cloud-first workflows and quick go-live
Broadcast-oriented architecture (XTV Station + customer R2)
In this setup, data is replicated to the customer's object storage (e.g., S3/R2). Images remain in the customer's domain, which supports policies like right to be forgotten or copyright.
Images can be served via the customer CDN or kept in storage; XTV Station connects and syncs data and media locally.
- XTV Station syncs data and media on-prem
- Customer object storage (R2) and customer CDN
- Built for low latency and high resilience
Data-only export (Google Drive)
Data (blue) is mirrored locally via Google Drive while media (red) is still served by the XTV CDN with UUID filenames.
Auto-sync triggers when the active program changes or when outputs for the active or default program are updated.
- Data mirrored locally via Google Drive
- Media delivered by XTV CDN with opaque UUIDs
- Auto-sync on program changes and output updates
- Useful when you need local data files