Deploy and Host Koito on Railway

Koito is a fast, modern, and themeable ListenBrainz-compatible music scrobbler and analytics server written in Go. Designed for self-hosters who want full ownership of their listening history and insights into their habits, Koito features automatic metadata and artwork enrichment, customizable themes, data imports from Last.fm, Spotify, ListenBrainz, and Maloja, and built-in scrobble relaying.

About Hosting Koito

This template deploys Koito (gabehf/koito:latest) with an embedded SQLite database and a persistent volume mounted at /etc/koito to store your listening history, cached artist and album artwork, and data import folders across container restarts.

Deployment Tips & Configuration

Initial Admin Credentials: On first boot, Koito creates an administrator account using KOITO_DEFAULT_USERNAME (default: admin) and KOITO_DEFAULT_PASSWORD (default: changeme). You can customize these variables on the deployment screen before first startup, or change them immediately after logging in by clicking the Settings icon (or pressing \) and opening the Account tab.
Generating Your Scrobble API Key: After logging in, open Settings (\) and navigate to the API Keys tab to copy your auto-generated API token.
Connecting Music Servers & Scrobblers: Point any ListenBrainz-compatible application (such as Navidrome, Symfonium, Pano Scrobbler, or WebScrobbler) to https:///apis/listenbrainz/1 and provide your Koito API key as the token.
Privacy & Login Gate: By default, your Koito dashboard is publicly viewable in read-only mode (KOITO_LOGIN_GATE="false"). Set KOITO_LOGIN_GATE="true" in your service variables if you want to require authentication before displaying any listening statistics.
Advanced Configuration: To configure additional options such as Last.fm or Subsonic artist image fetching, ListenBrainz scrobble relaying, or forced timezones, refer to the Koito Configuration Reference and add the desired variables in Railway's Variables tab.
Backups: Because Koito stores its SQLite database and image cache inside /etc/koito, you can protect your entire instance using Railway's native Volume Backups.

Note: This is a community-made template and therefore not officially supported by the Koito developer. Please direct template-specific help requests to the Railway thread for the template.

Common Use Cases

Self-Hosted Music Analytics: Track your top artists, albums, tracks, and listening trends over custom time ranges with a responsive, themeable interface.
Universal ListenBrainz Receiver: Collect scrobbles directly from Navidrome, Symfonium, Plexamp, Multi-Scrobbler, Pano Scrobbler, and WebScrobbler.
Scrobble Relaying: Use Koito as your primary scrobble receiver while automatically forwarding plays to official ListenBrainz or another compatible server.
Historical Data Consolidation: Import and merge historical listening exports from Spotify, Last.fm, Maloja, and ListenBrainz into a single unified database.

Dependencies for Koito Hosting

Koito (gabehf/koito:latest): Single-container Go server and web UI with an embedded SQLite database and a persistent volume mounted at /etc/koito.

Deployment Dependencies

Why Deploy Koito on Railway?

Deploying Koito on Railway provisions the container, persistent SQLite and artwork storage volume, and public HTTPS endpoint for ListenBrainz scrobbling in a single click, giving you a fast, always-on music analytics dashboard without managing reverse proxies or local server uptime.