JLTamp Server

A self-hosted music server and the backend for the JLTamp apps.
Your library, your accounts, your listening data — on hardware you control.

_{Screenshots show a demo library of freely licensed music.}

JLTamp Server scans the music you already own and streams it to the JLTamp app on Android and iOS, to Android Auto and CarPlay, to Chromecast, and to any browser through the bundled web player. It is multi-user, runs in a single Docker container with SQLite, and needs no external account or cloud service.

[!NOTE] JLTamp does not provide, host or distribute music. It plays files from your own server, and mounts them read-only.

Live demo: demo.jltamp.nl (user demo, password demo). Resets every night. Details and music credits in docs/DEMO.md.

Contents

• Highlights
• Architecture
• Quick start
• Connecting the app · Subsonic clients
• Optional components
• Configuration
• Operations
• Security and privacy
• Repository layout
• License

Highlights

Architecture

            ┌───────────────────────────── your network ─────────────────────────────┐
            │                                                                        │
 JLTamp app ├──►  JLTamp Server (this repo, Docker)  ──── read-only ────►  /music     │
 web player │      • FastAPI + SQLite in /data          (local disk, USB or NAS)     │
 Chromecast │      • bundled web UI at /                                             │
 CarPlay /  │      • HLS radio, transcoding (ffmpeg)                                 │
 Android    │                │                                                       │
 Auto       │                ├──► AI engine (ai/, optional)                          │
            │                ├──► Ollama / Piper / Demucs (optional, on the host)    │
            │                └──► Home Assistant (optional)                          │
            └────────────────────────────────────────────────────────────────────────┘

Everything optional is off until you configure it, and the app hides features the server does not offer.

Quick start

Requirements: Docker, and a folder of music the host can read. Images are published for linux/amd64 and linux/arm64 (PC, NAS, Raspberry Pi, Apple silicon) at ghcr.io/jltelectronics/jltamp-server.

1. Start the container, pointing the first volume at your music. Keep the :ro suffix; the server never needs to write to your library.

docker run -d --name jltamp-server --restart unless-stopped \
  -p 32400:32400 \
  -v /path/to/your/music:/music:ro \
  -v jltamp-data:/data \
  ghcr.io/jltelectronics/jltamp-server:latest

2. Or use Compose. Download docker-compose.yml, set your music path in volumes, and run:

docker compose up -d

To build the image yourself instead, clone the repository and replace the image: line in docker-compose.yml with build: ..

3. Create the admin account. Open http://localhost:32400. On first run the bundled web app shows a setup wizard for the owner account. If you set JLTAMP_PASSWORD instead, sign in with that.

4. Add a library. In Settings → Libraries, select one or more folders in the folder browser and start a scan. Your music then appears in the web player and in the apps.

All writable state lives in the jltamp-data volume and survives rebuilds.

Unraid and CasaOS

Unraid: download the template once from the Unraid terminal, then pick JLTamp-Server under Docker → Add Container → Template:

wget -O /boot/config/plugins/dockerMan/templates-user/my-JLTamp-Server.xml \
  https://raw.githubusercontent.com/JLTelectronics/JLTamp-server/main/deploy/unraid/jltamp-server.xml

Set the music share (read-only) and the appdata path, and choose another host port if Plex already uses 32400.

CasaOS: App Store → Custom Install → Import, and paste deploy/casaos/docker-compose.yml. It expects your music in /DATA/Media/Music; change that path if yours lives elsewhere.

If the library stays empty on CasaOS:

1. Point /music at your music. Only the folder mounted as /music is visible to JLTamp. If your music is somewhere else, for example on a USB drive under /media/..., open the JLTamp app settings in CasaOS, set the host path of the /music volume to that folder and save.
2. Add a library. JLTamp does not scan on its own. In Settings → Libraries, pick /music (or a folder inside it) in the folder browser, not the host path, and start a scan.
3. Check the folder browser. If /music is empty there, the volume in step 1 still points at the wrong folder.

Using a NAS

Mount the share (SMB, NFS or CIFS) on the host and pass the mount point as the /music volume. The folder browser is confined to the music mount and cannot reach the rest of the filesystem.

Settings → Libraries → Discover NAS lists file-share devices found over mDNS to help you find the address to mount. Discovery generally needs network_mode: host, because Docker's default bridge network blocks mDNS.

Connecting the app

Install JLTamp from Google Play or the App Store (iOS and iPadOS 16.4 or later), choose Connect your own server, and enter its address — for example http://192.168.1.10:32400 on your LAN, or your HTTPS address behind a reverse proxy. The app can also connect to an existing Plex server.

Subsonic clients

The server also speaks the Subsonic API (1.16.1, with the OpenSubsonic extensions formPost, songLyrics and apiKeyAuthentication), so existing clients such as Symfonium, Feishin, Substreamer, play:Sub, DSub or Tempo work too.

In the JLTamp app, open Settings → Subsonic apps and create an app password. Then enter in your client:

The app password is separate from your account password because most clients log in with a salted hash that the server can only verify against a stored secret. Clients that send the password itself also accept your normal password. A star on a track is a like in Liked Songs, so it shows up in the JLTamp app as well. Library access, playlists and history follow the same rules as the app. Administrators can switch the API off under Admin → Server.

Optional components

Configuration

All settings are environment variables; see .env.example and docker-compose.yml. Most feature switches can also be changed at runtime in Admin, which takes precedence over the environment.

Core

Accounts

Features

Operations

• Updating: docker compose pull && docker compose up -d (or git pull and --build if you build it yourself). Database migrations run automatically at start-up. :latest follows releases; :edge follows main.
• Backups: nightly SQLite backups are written to /data/backups (on by default, retention configurable in Admin). Back up the jltamp-data volume as a whole for artwork and caches too.
• Monitoring: Admin → Overview shows service health, disk usage, connected devices, active sessions and recent crash reports from the apps.
• Maintenance mode: regular users see a maintenance screen while administrators keep full access.
• Remote access: keep the server on your LAN and use a VPN such as Tailscale, or publish it behind a reverse proxy with HTTPS (Caddy, nginx). Do not expose the raw port to the internet.

Security and privacy

• The music mount is read-only; the server writes only to /data.
• Passwords are hashed; every device gets its own revocable token.
• Library access is granted per user, and artwork is access-checked, so users cannot fetch covers from libraries or playlists they cannot see.
• The folder browser is confined to the music mount.
• No telemetry and no external sign-in. Outbound requests are limited to artwork and metadata lookups, plus the services you configure yourself.
• A template privacy policy is served at /privacy (app/static/privacy.html); add your own contact details before you publish the server.

Please report security issues privately to the maintainers rather than in a public issue.

Repository layout

app/          FastAPI server: routers, scanner, radio, karaoke, static pages
ai/           optional AI engine (separate service, own README)
web/          prebuilt web player, served at /
docs/         images used in this README
deploy/       Unraid template and CasaOS app
Dockerfile    single-container image (python:3.12-slim + ffmpeg)
docker-compose.yml

License

Released under the GNU General Public License v3.0 or later. © 2026 JLT Electronics.

The JLTamp name and logo are not covered by the license; they remain the property of JLT Electronics. See TRADEMARKS.md.