Can I vibecode Netflix?

NOT REALLY · don't bother

price $19.99/moyou'd save $239.88/yrbuild time a weekendcategory 🎬 audio & videoreplaced by 0 people

You can absolutely build a Netflix, the software part is the easy part. A video catalog, transcoding pipeline, adaptive streaming player, watch progress, and profiles is a genuinely fun weekend of work, and self-hosted media servers already prove it. What you cannot build is the thing you were actually paying for: thousands of hours of licensed content plus originals you legally cannot obtain. A media server pointed at an empty disk is a very nice empty shelf. The honest DIY move is Jellyfin or a hand-rolled version of it over media you already own, which changes what the product is rather than replacing it.

the prompt

Build a self-hosted personal media streaming server and web player. Single project, runs on my own machine, no accounts service, no cloud, no telemetry.

Stack, no substitutions:
- Node.js with TypeScript, Fastify for the API
- SQLite via better-sqlite3 for the library database
- React with Vite for the frontend, plain CSS, no component library
- ffmpeg and ffprobe invoked as child processes
- hls.js in the browser for playback

What it does:
1. Reads MEDIA_ROOT from .env and recursively scans it for video files (mp4, mkv, avi, mov). Parses filenames into title, year, and optional season/episode.
2. Runs ffprobe on each file to record duration, resolution, codecs, and audio tracks.
3. Optionally enriches each title with metadata and poster art from the TMDB API using TMDB_API_KEY from .env. If the key is missing, skip enrichment gracefully and show a generated placeholder poster.
4. Serves a library browse UI: poster grid, search, filter by movie vs series, series drilldown to seasons and episodes.
5. Plays video at /watch/:id. If the source is browser-friendly h264/aac, stream it directly with HTTP range support. Otherwise transcode on the fly to HLS with ffmpeg, segmenting into a cache directory, and serve the playlist to hls.js. Reuse cached segments on repeat plays.
6. Tracks watch progress per profile. Local profiles are just names in SQLite, no passwords, no auth provider. Resume where you left off, mark watched at 90 percent, and show a Continue Watching row.
7. Extracts embedded subtitle tracks with ffmpeg, converts to WebVTT, and exposes them as selectable tracks in the player.
8. A CLI command "npm run scan" for rescanning, plus a watcher that picks up new files while running.

Explicitly out of scope: any content acquisition, downloading, scraping, or DRM. No native mobile or TV apps. No recommendation engine beyond a recently-added row. No multi-user auth or public internet exposure; bind to localhost by default and document that exposing it is my problem.

Deliver a README with setup steps, a .env.example listing MEDIA_ROOT, TMDB_API_KEY, PORT, and TRANSCODE_CACHE_DIR, and seed the database on first run. Keep the whole thing runnable with npm install then npm run dev.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

Nobody subscribes for the UI, they subscribe for the shelf. Netflix spends billions a year producing and licensing things you cannot buy, torrent legally, or approximate, and then delivers them at a bitrate that holds up on a TV over a mediocre connection through apps that already exist on the hardware in your living room. A self-hosted player solves playback, which was never the bottleneck. The moment your build needs content, you are either buying discs, buying digital copies, or committing crimes, and none of those are cheaper or more convenient than the subscription.

what you lose

xThe entire catalog: licensed films, TV, and originals you cannot legally acquire

xGlobal CDN delivery that does not stutter on hotel wifi

xNative apps on every TV, console, phone, and streaming stick

xDownloads with DRM, offline playback, and multi-device sync that just works

xRecommendations built on hundreds of millions of viewing histories

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced Netflix ($19.99/mo) with one prompt"