Luma

Purpose

Luma brings the broadcast workflow into one user portal. It allows signed-in users to go live, preserve broadcasts as recordings, create clips, review their media library, and archive eligible recordings to their own connected YouTube channel.

Luma is designed so users manage content and account connections that belong to them. The dashboard is becoming a public-facing Luma portal where each user can access their own streams, recordings, clips, playback history, and archive settings.

What Luma Does

• Provides live streaming accounts and stream keys for signed-in users.
• Records live broadcasts and checks completed files before they are published or archived.
• Creates clips, previews, metadata, and media history from user content.
• Supports playback and review of recordings, clips, and media entries.
• Shows status and diagnostics for the user's streaming and recording workflow.
• Optionally uploads eligible recordings to the connected user's YouTube channel.

Why Luma Requests YouTube Access

YouTube access is optional and is requested only when a signed-in user chooses to connect YouTube archiving. Luma requests youtube.upload so it can upload selected or automatically eligible recordings to the connected channel. Luma requests youtube.readonly only to identify and verify the connected YouTube channel shown in the Luma portal.

Luma does not use YouTube access for advertising, tracking, profiling, resale, or unrelated services. Users can disconnect YouTube in Luma settings or revoke access from their Google Account.

Data Handling

Luma is self-hosted. Jellyfin, Redis, MediaMTX, Caddy, Docker metrics, and configured storage are local components of the same deployment. Data moving between those components is internal processing, not third-party sharing. The only external transfer built into this feature set is a user-authorized upload to Google and YouTube for YouTube archiving.