Plex-quality UI layer for Jellyfin self-hosters

What to build

A polished, drop-in Plex-style web UI skin for Jellyfin, shipped as a Docker container or reverse-proxy layer that sits in front of an existing Jellyfin server and replaces its default interface with a near-pixel-match of Plex's browse/watch experience.

Jellyfin has the open, paywall-free backend self-hosters want, but its stock UI lags Plex's polish — a faithful Plex-style client closes that gap and taps a community actively trying to leave Plex over licensing and telemetry changes.

Demand

Self-hosted media server users (r/jellyfin, r/PleX, r/selfhosted) who want Plex's look and remote-access convenience without Plex's account requirements, telemetry, or paywalled remote streaming are the core audience, and the recent wave of Plex policy and pricing changes has pushed more of them to evaluate Jellyfin right now.

• Hacker NewsNews

  Show HN: A faithful recreation of the Plex UI for Jellyfin — 4 points, 0 comments on HN. Poster notes: 'My biggest issue with Jellyfin was always the UI, s[o I built this]'.

• Reddit r/jellyfin / r/PleXAnalysis

  Recurring threads comparing Jellyfin and Plex UIs cite Jellyfin's interface as the main adoption blocker for users migrating away from Plex, especially after Plex remote-access and pricing changes.

Stack

• Vue.js or React (frontend skin)
• Jellyfin REST API / SDK
• Docker
• Nginx or Caddy (reverse proxy to Jellyfin backend)
• Traefik (optional, for hosted multi-tenant proxying)

Solo + AI difficulty

The hard part is pixel-accurate UI replication and keeping up with Jellyfin API changes across versions, not the core architecture; a reverse-proxy skin with a handful of core screens (home, library browse, player) is a realistic 2-4 week MVP for one developer using AI to generate the UI components, with ongoing maintenance burden as both Plex's look and Jellyfin's API evolve.

Entry threshold

Low barrier: the core UI already exists as an open-source LLM-built reimplementation, so a solo builder mainly needs to productize it (installer, auth, hosting, support) rather than build it from scratch; main effort is polish, packaging and trust-building with a privacy-conscious self-hosting audience.

Window

6-12 months

Where to find first users

• r/jellyfin
• r/selfhosted
• r/PleX
• Show HN follow-up post once the project has more polish
• Jellyfin community Discord/forum

Competitors

• Streamyfin

Counter-signals & risks

• Jellyfin and its open-source community could absorb or natively integrate a popular Plex-style skin as a theme/plugin, eliminating the need for a separate commercial add-on.

• Self-hosted/privacy-motivated users who choose Jellyfin specifically to avoid paywalls and telemetry may resist paying for a hosted convenience tier, limiting monetization.

• Replicating Plex's UI closely could raise design/trademark/copyright concerns from Plex, creating legal risk for a monetized product.