Local authority
Your server owns library records, users, watch state, settings, and access decisions.
Privacy
Private by design.
Your data belongs to you. Pixel Brite runs from your server, with files, users, watch progress, and sharing decisions kept with the system you operate.
Trust model
The server keeps the sensitive parts.
You run the server. It authenticates users, stores library state, and keeps owner controls around access and sharing.
Optional connections
Metadata, artwork, imports, app distribution, and platform services support the product separate from your media files.
Owner control
You decide who gets access, which devices remain trusted, and when sharing links are revoked.
Plain language
Optional services support the experience without taking over your library.
Metadata, artwork, relays, app distribution, and platform services may support the product. Your media files and owner-controlled library state remain with your server.
What stays yours
The sensitive parts stay with the server owner.
Media files, users, watch state, access, backups, and migration stay under owner control.
- Media files stay in storage you choose.
- Watch progress and membership state are server-controlled.
- Temporary share links can be revoked.
- Trusted-device state can be removed.
- Backups and migration stay under operator control.