Private source boundary
Provider credentials and private media sources stay on trusted servers instead of being exposed to the browser.
Product
One protected path from your app to the player.
Unpirator sits between your authorization decision and media delivery. Your app keeps control of users and content; the playback layer handles short-lived protected access.
Protected playback path active
1
Your application
2
Authorization boundary
3
Protected session
4
Media gateway
Signed playback sessions
Access is short-lived, scoped and revocable instead of becoming a reusable public media link.
Viewer accountability
Protected playback always binds the authenticated viewer email to a stable application device ID; plan-enabled watermarking can display that trusted identity during playback.
Device controls
Track, limit, block or revoke devices when the purchased plan includes those capabilities.
Concurrency limits
Control simultaneous playback when concurrent-stream enforcement is enabled for the customer plan.
Playback visibility
Inspect active and recent sessions, usage and security events from the customer workspace.
How it works
The browser is never the trust boundary.
The protected path starts from your own backend decision and stays server-led until the media gateway authorizes delivery.
01
Your app loads the video
Your database remains the source of truth for content and the viewer's entitlement to watch it.
02
Your server authorizes the viewer
Your backend authenticates the viewer, resolves their email from trusted server-side auth state and checks access before Unpirator creates playback.
03
Unpirator creates protected access
The concrete protection features enabled by the customer's plan are applied to the playback session.
04
The gateway delivers media
The browser receives short-lived protected playback instead of provider credentials or a permanent private source URL.
Where it fits
Different products. Same boundary.
Education platforms
Membership products
Premium communities
Internal training