NextBeats

Open-source ambient music for focused work, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (MIT) lofi music player built with Next.js. Streams audio from YouTube channels through a retro TV-style interface with a built-in ambient sound mixer [README][1].
• Who it’s for: Developers, students, and remote workers who want a self-hosted, ad-free lofi station with custom channel support — and don’t want to depend on a third-party service staying online [1][README].
• Cost savings: The public lofi.cafe and similar services are free, so this isn’t about cutting a bill. The value is control: no ads, no tracking, no service going down, and the ability to add any YouTube stream you want [README].
• Key strength: YouTube integration means effectively unlimited lofi content without managing audio files. The ambient sound mixer (rain, cafe, fireplace, keyboard) runs independently from the music, so you can layer sounds precisely [README].
• Key weakness: The project has 163 GitHub stars and no documented third-party reviews beyond passing mentions in roundup posts. It’s a personal project, not a maintained product — meaning you’re betting on a small repo staying functional as YouTube’s embed behavior changes [1][2].

---

What is NextBeats

NextBeats is a self-hostable web application that turns your server into a personal lofi radio station. You open it in a browser, pick a channel (pre-loaded with Lofi Girl and similar streams), and it plays the corresponding YouTube livestream through a retro television-style interface [README]. On top of the music, you can layer ambient sound effects — rain, cafe noise, fireplace, keyboard typing, white noise, wind — each with its own independent volume control [README].

The project’s GitHub description calls it “a modern, customizable lofi music player built with Next.js and TypeScript. Perfect for coding, studying, or just chilling.” [README]. That is, unusually for open-source project descriptions, an accurate summary. It does not try to replace Spotify, Navidrome, or Jellyfin. It is specifically a lofi radio player with ambient sound layering.

The technical stack is Next.js + TypeScript + Tailwind CSS + shadcn/ui + React Player for YouTube playback [README]. Settings persist in localStorage, meaning your volume preferences, custom channels, and custom sound effects survive browser refreshes without needing a database or backend [README]. The live demo runs at https://nextbeats.vercel.app.

Marius Hosting, a Synology-focused homelab site that reviewed Docker containers for ambient sounds, listed NextBeats alongside Noisedash, Moodist, and Atmoify — the four tools they considered worth running on a NAS [1]. That placement tells you something about who actually uses this: it’s a homelab tool, not a product with a commercial roadmap.

---

Why people choose it

The use case is specific enough that there’s almost no competitive analysis to be done in the traditional sense. Nobody is migrating off Spotify Premium to NextBeats to save money. The people who deploy this are doing so for two distinct reasons.

Ambient sound layering. Free lofi streams like Lofi Girl on YouTube exist, but they don’t let you mix rain sounds at 40% volume over the music while keeping keyboard ASMR at 20%. NextBeats does that, in a browser, with no account required [README]. Marius Hosting specifically highlights this layering capability as the differentiator when listing it among the best ambient sound Docker containers for Synology [1].

Independence from third-party services. This is the homelab argument. If lofi.cafe goes down or gets acquired and adds ads, your workflow breaks. Self-hosting means you own the frontend; you just need YouTube’s embed API to keep working [README][1]. The trade-off is that your setup is now contingent on YouTube’s embed policies, which is arguably less reliable than a dedicated lofi service — but for people who already run a NAS or home server, adding one more Docker container to control their environment is a familiar pattern.

The Self-Host Weekly newsletter featured NextBeats in its December 2025 issue [2], which is the clearest signal that the broader self-hosting community is aware of it and considers it worth a mention. The project also appeared in a November 2024 roundup of new self-hosted software [3]. These are brief mentions rather than full reviews, but they confirm that the project has been circulating in homelab communities for over a year.

No in-depth third-party reviews of NextBeats were found for this article. The analysis below relies on the README, the live demo at https://nextbeats.vercel.app, and the community roundup mentions above.

---

Features

Based on the README and the live demo:

Music playback:

• YouTube integration via React Player — plays any YouTube stream, livestream, or video as audio [README]
• Pre-loaded with channels (Lofi Girl is the default) [README][website scrape]
• Channel switching via buttons in a TV-channel-style interface [README]
• Custom channel management: add any YouTube URL with a name, description, and creator field; channels persist in localStorage [README]

Ambient sound mixer:

• Six built-in sound effects: cafe ambience, keyboard typing, fireplace crackling, rain, white noise, wind [README]
• Independent volume control per effect — mix as many simultaneously as you want [README]
• Custom sound effects: add any YouTube URL as a sound source with its own volume control [README]
• All custom effects persist in localStorage [README]

Interface and customization:

• Retro TV-style visual design [README]
• Theme customization — multiple visual themes available [README]
• Responsive design — works on mobile, though programmatic volume control is disabled on iOS and Android due to browser security restrictions (physical device volume buttons required) [README]

Self-hosting:

• Docker support with a Dockerfile included in the repo [README]
• Standard Next.js deployment: clone, npm install, npm run dev or npm run build [README]
• No database required — all state in localStorage [README]
• No API keys required out of the box — YouTube embeds work without authentication

What’s missing:

• No user accounts — everything is per-browser
• No playlist management beyond YouTube URLs
• No scrobbling to Last.fm or Listenbrainz
• No offline support — requires YouTube access at all times
• No backend — means no sync across devices

---

Pricing: SaaS vs self-hosted math

This category is different from most tools reviewed here because the free alternatives are genuinely free web services, not paid SaaS products.

NextBeats self-hosted:

• Software: $0 (MIT license) [README]
• Hosting: $0 if you run it on an existing home server, NAS, or Synology [1]; ~$5/month on a minimal VPS if that’s your only use for it
• Domain and HTTPS: optional — you can run it on a local IP with Docker and access it from within your network

Alternatives pricing:

• lofi.cafe, musicforprogramming.net, similar web services: $0, but you don’t control them
• Moodist (also self-hostable): $0, MIT, over 70 built-in sounds [1] — no YouTube dependency
• Atmoify (self-hostable): $0, YouTube-based audio + timers + sound profiles [1]
• Noisedash (self-hostable): $0, generative ambient sounds with audio processing tools [1]
• Spotify Premium for the “focus music” use case: $11.99/month

The honest savings calculation: if you’re paying for Spotify to use focus playlists, you could switch to NextBeats and save $11.99/month. That’s a narrow case. Most people who find this tool are already using free alternatives and want customization or self-hosting for its own sake, not cost reduction.

---

Deployment reality check

NextBeats is among the simpler self-hosted tools to deploy.

Node.js path:

git clone https://github.com/btahir/next-beats.git
cd next-beats
npm install
npm run build
npm start

That’s it. No database, no Redis, no SMTP. You need Node.js v16 or higher [README].

Docker path:

docker build -t next-beats .
docker run -p 3000:3000 next-beats

For Synology NAS users, Marius Hosting has a dedicated installation guide for NextBeats [1], which makes it accessible even for users who haven’t set up Docker containers from scratch before.

What can go sideways:

• YouTube dependency. The entire product stops working if YouTube blocks the embed on your server’s IP, changes their embed API, or restricts a specific stream. This is a real risk that the README doesn’t address. Moodist and Noisedash use actual audio files rather than YouTube streams — that makes them more resilient to this failure mode [1].
• Mobile volume control. iOS and Android browsers block programmatic volume control as a security measure. You can use NextBeats on mobile, but you’ll need to use your device’s physical volume buttons — the in-app sliders won’t function for the main music track [README].
• localStorage-only state. Your custom channels and sound settings live in the browser that set them up. If you access NextBeats from another device or browser, you start fresh. There’s no account system, no export/import of settings.
• Maintenance uncertainty. The project has 163 GitHub stars and is maintained by a single developer (GitHub user btahir, also behind You-TLDR) [README]. There’s no issue tracker activity data available to assess how actively bugs get fixed.

Realistic deployment time: 10–20 minutes on an existing Docker host. For a new Synology NAS with no Docker experience, follow Marius Hosting’s guide and budget 1–2 hours.

---

Pros and cons

Pros

• Zero-config self-hosting. No database, no message queue, no SMTP server. Clone, build, run — that’s the entire setup [README].
• MIT license. Use it, fork it, modify it, embed it in something else. No commercial restrictions [README].
• Sound layering is genuinely useful. The ability to mix cafe + rain + keyboard sounds at independent volumes over a lofi stream, with that configuration persisting in localStorage, is the one feature that separates this from just opening YouTube [README].
• Custom channels and effects. Any YouTube URL works — you’re not locked to a curated list. If your favorite obscure jazz stream gets added to YouTube, it’s one click to add it [README].
• No account required. Open the URL, it works. No registration, no email verification, no onboarding [README].
• Recognized in the homelab community. Featured in Self-Host Weekly and listed by Marius Hosting as a top ambient sound container for Synology [1][2][3].

Cons

• YouTube dependency is a structural weakness. If YouTube embeds break — whether due to policy changes, regional blocks, or the stream creator’s settings — the entire tool fails silently. Audio-file-based alternatives like Moodist are immune to this [1].
• Single-browser state. localStorage means your setup doesn’t follow you across devices. For a tool meant to enhance focus during work, losing your carefully tuned sound mix when you switch from desktop to laptop is annoying [README].
• No mobile volume control. On iOS and Android, the app renders correctly but the volume sliders don’t work for the music track — a browser limitation the README acknowledges but can’t fix [README].
• 163 GitHub stars, one maintainer. Not a criticism of quality, but a realistic assessment of longevity risk. Compare to Moodist, which has a larger community and doesn’t depend on YouTube embeds [1].
• No third-party in-depth reviews exist. The only third-party mentions are passing references in homelab newsletters and roundup posts [1][2][3]. This is a thin evidence base for something you’re putting in your homelab stack.
• No sync, no export. Your configuration lives in one browser. There’s no way to back it up or move it.

---

Who should use this / who shouldn’t

Use NextBeats if:

• You already run a home server or NAS and want a self-hosted lofi player as a Docker container alongside your other services.
• The specific combination of YouTube-based music + layered ambient sounds is exactly what you want — this combination isn’t available in simpler tools like Noisedash or Moodist.
• You want to customize your channels without being locked to a curated playlist.
• You want an MIT-licensed codebase you can fork and modify.

Skip it (try Moodist instead) if:

• You want ambient sounds without a YouTube dependency — Moodist ships 70+ sounds as actual audio files and has a cleaner, more polished UI [1].
• You want an actively maintained project with a visible community.

Skip it (try Atmoify instead) if:

• You need timer functionality alongside your ambient audio — Atmoify adds focus timers and sleep timers, and lets you save named “sound profiles” [1].

Skip it (stay on lofi.cafe) if:

• You don’t already have a home server and would be deploying just for this. Setting up a VPS purely to avoid lofi.cafe’s dependency isn’t worth the ongoing maintenance.

Skip it (use Navidrome or Jellyfin instead) if:

• You have a music library you want to stream. NextBeats is a lofi radio player, not a music server. Navidrome and Jellyfin serve your files; NextBeats serves YouTube embeds.

---

Alternatives worth considering

Moodist — The closest direct competitor in the self-hosted ambient sound space. Over 70 built-in sounds stored as actual audio files (no YouTube dependency), more polished design, more active community. Better pick if you don’t specifically need the YouTube lofi stream integration [1].

Atmoify — Similar to NextBeats in using YouTube for audio, but adds focus timers, sleep timers, and the ability to save and load named sound profiles. More fully-featured for structured work sessions [1].

Noisedash — Generative ambient noise tool with audio processing (filters, LFOs, effects). More technical than NextBeats — aimed at users who want to synthesize soundscapes rather than stream lofi YouTube channels [1].

lofi.cafe, musicforprogramming.net — Free web services with zero setup. The argument against them is purely about control and customization, not cost.

Navidrome — If the goal is music streaming generally, not specifically lofi with ambient sound layering, Navidrome is the self-hosted Spotify alternative: serves your own music library, has native apps and Subsonic API compatibility, and is actively maintained with a large community.

---

Bottom line

NextBeats fills a specific niche: a self-hosted lofi music player where you can layer ambient sounds at independent volumes, add any YouTube stream as a custom channel, and run the whole thing as a Docker container with no database or backend setup. For homelab users who already have a NAS or server running, deploying it costs nothing beyond five minutes of Docker commands, and Marius Hosting’s Synology guide makes it accessible even for non-technical users [1].

The honest caveats are real: YouTube embedding is the entire infrastructure, and if that breaks, so does the tool. The 163-star GitHub repo with a single maintainer is not a project to bet your productivity setup on without a backup plan. And for pure ambient sounds without YouTube dependency, Moodist is simply a better tool.

But if you want exactly what NextBeats does — retro TV interface, YouTube-based lofi streams, layered ambient sound mixing, everything saved locally, zero accounts — nothing else in the self-hosted space combines all of it the same way. It’s a small, well-scoped project that does its one thing cleanly.

---

Sources

1. Marius Hosting — “Synology: Best Docker Containers For Ambient Sounds”. https://mariushosting.com/synology-best-docker-containers-for-ambient-sounds/
2. Ethan Sholly, selfh.st — “Self-Host Weekly (19 December 2025)”. https://selfh.st/weekly/2025-12-19/
3. Ethan Sholly, selfh.st — “This Week in Self-Hosted (22 November 2024)”. https://selfh.st/weekly/2024-11-22/

Primary sources:

• GitHub repository and README: https://github.com/btahir/next-beats (163 stars, MIT license)
• Live demo: https://nextbeats.vercel.app