Self-hosted service
remvze/moodist avatar
remvze/moodist

Moodist ships as static files behind Caddy, with the audio on someone else's licence

Ambient sounds for focus and calm.

3,960 stars340 forksTypeScriptMIT

At a glance

What is it?
Moodist is an ambient sound application built with Astro and React: eighty four curated sounds you layer into mixes, generators for binaural and isochronic tones, and a set of focus tools. The published Docker image compiles the site on the build machine and serves the result from Caddy on port 8080, and some of the audio carries third party licences rather than the project's own.
Who is it for?
Moodist suits someone who wants a self hosted focus timer they control, on hardware and on a domain they own, rather than a hosted soundscape service. It does not suit anyone who needs the audio to be permissively licensed as a whole, because part of the sound library comes from third parties under separate terms.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 49 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • remvze/moodist3,960 ★ · +114
Star history
Repository2026-09-242026-11-15
remvze/moodist3.8k4k

114 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Eighty four sounds, layered rather than queued

The feature list starts with the count, which is the number people search on: eighty four curated ambient sounds that can be layered into custom soundscapes. Layered is the operative word, since it means several sounds play at once at independent levels rather than one track replacing another, which is what makes the difference between rain and rain on a roof. Two details around playback are worth noting. Transitions fade rather than cut, on play, on stop and when the sleep timer shuts the mix down, so a timer does not end with a click. And a mix is shareable as a URL with one click import, so the artefact you configure is a link rather than an export file. Presets sit on top of that, with save, rename, delete and instant reapply, which is the difference between a mixer and a scratchpad.

Two tone generators and a productivity strip share the same window

The second half of the feature list is the part that separates Moodist from a sound board. There are built-in generators for binaural beats and for isochronic tones, both of which are frequency based effects rather than recordings, so they run indefinitely without a loop point. Alongside them are tools that have nothing to do with audio: a breathing exercise, a Pomodoro timer, a countdown, a to do list and a notepad. That is an unusual combination for a focus application, and it explains the two dependencies in the manifest that are not audio related, a YouTube React component for embedded media and a confetti library. The application is also installable as a progressive web app with offline caching, so the mix keeps working without a network, which is the point of an ambient application.

The image compiles on the host and serves from Caddy

The container file is short and the comment at the top explains the design decision: the Astro output is static, so the build runs on the runner's own architecture rather than cross compiling. The build stage is a slim Node 24 Alpine image, installs the package manager globally, copies only the manifest, the lock file and the workspace manifest before installing with a frozen lock file, then copies the rest of the source and runs the build. The runtime stage is not Node at all, it is the Caddy image, with the Caddyfile copied into place and the built site copied into the web root. Only port 8080 is exposed, which is the port the README tells you to open. So the published image contains a web server and a directory of files, with no application runtime inside it.

Two self-hosting paths are documented, both landing on port 8080

The self-hosting section gives a single container command:

bash
docker run -d \
  --name moodist \
  -p 8080:8080 \
  ghcr.io/remvze/moodist:latest

and a compose alternative, with the compose file said to be included at the project root and started with the standard up command in detached mode. Both routes end at the same address, a localhost URL on port 8080, which is the only place the port number appears outside the container definition. The compose file itself is five settings: the service name, the image reference, a logging option capping a single log file at one gigabyte, a restart policy of always, and the port mapping. The logging cap is the only non default choice, and it is the kind of setting that exists because a long running audio server is chatty in a way a static site is not.

The compose file names no tag, so it tracks whatever the default is

One detail in that compose file is a real operational choice rather than a default. The documented single container command pins the image to the latest tag explicitly, while the compose file names the image without one. Without a tag, the reference resolves to the default tag rather than to a version you chose, so the two documented paths do not behave identically when a new build is published. The compose file also declares a version key at the top, which is the older compose schema and is ignored by current tooling that infers the schema from the content. Neither is wrong, but a self hoster who wants the documented behaviour should add a tag to the compose reference or accept that upgrades arrive on a restart rather than on a pull.

The toolchain mixes Astro 7, React 19 and three commit conventions

The manifest is where the framework choices are visible. Astro is pinned at a version seven release with the React integration and a workbox based progressive web app integration, React and its DOM renderer are on version nineteen, state is a small store library, and audio playback is handled by Howler with its type declarations installed alongside it. Tooling is split three ways and it is worth noticing that all three coexist. Biome does checking, linting and formatting, with separate commands for each. Husky runs on prepare with lint staged configuration at the root. And commit conventions are defined twice over: a commitlint configuration, a commitizen configuration with the conventional changelog preset, and a standard version configuration, with the release script skipping the verify hook and three scripts overriding the release as major, minor or patch.

Part of the audio is licensed by someone else

The licence section is split in two, and the second half is the one that matters if you plan to redistribute the application. The project itself is MIT. Then a third party assets heading states that some of the sounds are sourced from external providers and are subject to different licences, naming two of them: the Pixabay content licence, and the public domain dedication for Creative Commons Zero. Neither is MIT, and the MIT grant covers the code rather than the audio. For someone running the container for themselves this is academic, since the terms are about redistribution rather than use, but it becomes the first question if you repackage the image, redistribute the built site, or use the sounds in a video. The repository has a dedicated licence file and a changelog, and there is no GitHub release history behind the version.

Version 3.1.1 lives in the manifest, not in a release

The last piece of the version story is that the package is at 3.1.1 while the repository has no published releases at all, so there is no tag to install and no changelog entry on the hosting side. The project does keep a change log file at the root, and the release scripts in the manifest are what would write it, driven by the conventional changelog tool with a skip on the verify hook. The last push to the default branch main is dated 2026-09-27 and the repository is not archived. Funding is handled in the two usual ways for a project at this scale, a star request in the readme and a donation link, and the readme closes by pointing contributors at a contribution file rather than describing a process.

Editorial conclusion

Moodist suits someone who wants a self hosted focus timer they control, on hardware and on a domain they own, rather than a hosted soundscape service. It does not suit anyone who needs the audio to be permissively licensed as a whole, because part of the sound library comes from third parties under separate terms. Before deploying, read the third party assets section so you know which files are not covered by the project licence, and pin an image tag in your compose file rather than relying on the default.

Frequently asked questions

What is Moodist?

An ambient sound application for focus and calm, offering 84 curated sounds you layer into custom soundscapes with fading transitions and a sleep timer. It also includes binaural beat and isochronic tone generators, plus breathing, Pomodoro, countdown, to do and notepad tools, and it installs as a progressive web app with offline caching.

How do I self-host Moodist?

Either run the published container, mapping port 8080 and opening localhost on that port, or use the compose file included at the project root and bring it up in detached mode. The image is built on a slim Node image and served by Caddy, so only port 8080 is exposed.

Can I redistribute the sounds in Moodist?

Not under the project licence alone. The code is MIT, but some of the sounds come from third party providers under different terms, with the Pixabay content licence and a Creative Commons Zero public domain dedication both named. Check those terms before repackaging the image or the built site.

How are Moodist mixes shared?

As a URL, with one click import on the other side. Presets can also be saved, renamed, deleted and reapplied instantly, and a mix fades in and out on play and stop and when the sleep timer stops it.

Official sources

  1. Issues
  2. License: MIT
  3. Project website
  4. README
  5. remvze/moodist on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/remvze-moodist.svg)](https://hysenlabs.com/projects/remvze-moodist)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/remvze-moodist.svg)](https://hysenlabs.com/projects/remvze-moodist)

Was this useful?