Self-host Kima
v1.11.0Music, podcast and audiobook server with vibe matching
docker run -d --name kima -p 3030:3030 -v /path/to/your/music:/music -v kima_data:/data chevron7locked/kima:latest- Stars
- 1 294
- RAM
- each audio analysis worker needs about 1 to 1.5 GB, up to 2 to 3 GB at peak; the example Compose file limits the container to 6 GB
- Ports
- 3030 (Web app; the only port you publish (it passes /api requests to the API server)), 3006 (API server, inside the all-in-one image; published by the split stack)
chevron7locked/kimaWhat is Kima?
Kima is a DIY music server: you hand it a folder of songs and get browser playback on desktop and phone, plus podcasts and audiobooks. Every file Kima reads in the common lossless and lossy formats is identified via MusicBrainz tags, album tracklists and AcoustID fingerprints, and lyrics come from the tags or LRCLIB. Its signature piece is the vibe engine, which rates each track on three axes — a CLAP sound embedding, audio-derived feel (valence and arousal, calibrated against your whole collection) and the artist's MusicBrainz genres. That single similarity score powers recommendations, Song Path transitions, Blend playlists, mood mixes and a 3D map of the library. Music acquisition is first class: album requests go to Lidarr, Soulseek search and downloads work built-in or through slskd, weekly discovery playlists pull music you do not own, and playlists can be imported from Spotify, Deezer, YouTube, SoundCloud, Bandcamp, Mixcloud or an M3U file. Audiobooks stream from a linked Audiobookshelf server with positions synced back, plays can scrobble to your own ListenBrainz account, and ordinary Subsonic clients connect through the OpenSubsonic API with revocable per-device tokens. Several accounts are supported, the first one being admin, with optional 2FA, public playlist share links and listening statistics. Operationally it is a single container bundling the web app, API, Postgres, Redis and both analyzers behind port 3030, with everything else in /data; optional NVIDIA GPU switches speed up enrichment. There is no telemetry, the iOS app is only promised, and the project is young (its first releases date from late 2025) but ships stable 1.x updates regularly.
Should you self-host Kima?
Kima scores 55/100 on selfhost.directory (how scoring works) and ranks #42 of 118 in Media Server. It has 1 294 GitHub stars.
It shipped 10 stable releases in the past year. The latest, v1.11.0, came out on 12 October 2026. New versions land roughly every 2 weeks.
Setup is easy: most people get it running in one sitting. An official Docker image is available. It is GPL-3.0-licensed and written mostly in Typescript.
Its closest alternative on selfhost.directory is Jellyfin (88/100, 58 744 stars). It scores higher overall, so compare the two before you pick. See Kima vs Jellyfin side by side.
Features
- AI vibe-based matching
- Audiobook support
- ListenBrainz scrobbling
- Listening statistics
- Multi-user accounts
- Music discovery and downloading
- NVIDIA GPU acceleration
- On-the-fly transcoding
- OpenSubsonic API
- Playlists with sharing and import
- Podcast playback
- Song Path and Blend playlists
- TV layout
- Vibe map of the library
Kima README
More in Audiobooks
AudiobookshelfOpen-source, self-hosted media server for audiobooks and podcasts with on-the-fly audio streaming, progress syncing and podcast auto-downloads.
Calibre WebOpen-source, self-hosted front-end for browsing, reading, converting and sharing ebooks from a Calibre database, with OPDS access and per-user permissions.
ebook2audiobook---LegacySelf-hosted, open-source converter that turns ebooks and PDFs into audiobooks using multiple TTS engines, voice cloning, OCR and 1158 languages.










0 comments