# Build brief — a focused alternative to YouTube Music Premium

> **Verdict:** Not faithfully · **Buildability:** 6/100 · **Category:** Audio
> **Source:** https://www.canitbevibecoded.com/youtube-music-premium
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from YouTube Music Premium. Verify current pricing and capabilities before acting.

## Context

**YouTube Music Premium** — Organize and stream user-owned audio without accessing YouTube's licensed catalog. It currently costs $10.99/mo.

A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For YouTube Music Premium, organize and stream user-owned audio without accessing YouTube's licensed catalog. The hard boundary is youtube catalog, videos, rights, recommendations, identity, and global delivery, plus licensed content, rights, and distribution network.

This brief describes a focused, single-operator replacement for the part of YouTube Music Premium that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Organize and stream legally owned or user-created audio, analyze local files, and provide a private playback workflow without accessing YouTube's licensed catalog.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Legally owned local audio files.
- Ffmpeg.
- Local storage.
- Optional audio-analysis models.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build a closest honest personal substitute for YouTube Music Premium in an empty repository.
Use Python 3.12, FastAPI, SQLite, ffmpeg, and a local web interface; do not offer alternative stacks.
The core loop is: organize and stream legally owned or user-created audio, analyze local files, and provide a private playback workflow without accessing YouTube's licensed catalog.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Index only user-selected folders and preserve source audio without modification.
Read tags and artwork, calculate loudness and waveform data, and detect exact duplicates by hash.
Provide albums, artists, playlists, search, queue, favorites, and resumable local playback.
Add optional creator tools for trim, normalize, split stems through a local model, and export new files.
Keep all rights and source information attached to imported tracks and display it during export.
Document that the application does not provide music, licensing, distribution, or royalty collection.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out copyrighted catalog acquisition or sharing.
Deliberately leave out streaming-service circumvention.
Deliberately leave out royalty accounting, label distribution, and global content delivery.
Finish by running the tests and listing the exact commands used.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- YouTube catalog, videos, rights, recommendations, identity, and global delivery.
- Licensed music catalog.
- Royalty and distribution relationships.
- Global streaming infrastructure.
- Licensed content and distribution rights are not reproducible with an LLM.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Navidrome](https://github.com/navidrome/navidrome) — Active open-source personal music server for legally owned libraries

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/youtube-music-premium