mStream Hosting

How mStream works

mStream scans configured music folders, reads audio metadata, and presents the collection through a responsive browser player. Users can search the library, build playlists, queue tracks, use Auto DJ, inspect lyrics where available, and stream supported audio to connected devices. Optional mobile clients can connect to the same server.

The project also documents transcoding, uploads, waveform generation, discovery, federation, DLNA, and other optional functions. Availability depends on the container build, media format, browser, client, and configuration. The hosted page therefore focuses on the personal streaming workflow and does not promise every optional integration or local-device feature.

Key mStream features

Media files remain the main capacity driver. Audio format, bitrate, artwork, waveform data, playlists, scan indexes, uploads, and simultaneous listeners all contribute to resource use. Transcoding requires additional processing when a client cannot play a stored file directly, while ordinary direct streaming is generally lighter.

mStream supplies the server software but not a music catalogue, streaming licence, mobile-store account, metadata guarantee, or rights to upload and share recordings. Users must provide lawful media and compatible clients. Application email is disabled, though the core playback workflow does not depend on outbound messages.

Who uses mStream

Collectors stream albums stored in their own folders, families share a household library, and music enthusiasts create playlists that are available from several browsers. A small organisation can use it for audio it owns or is authorised to distribute to a controlled audience.

It is less suitable for people who expect a commercial catalogue, artist licensing, recommendation service backed by a global provider, offline rights management, or a fully supported device ecosystem. Those functions belong to subscription music platforms rather than a personal library server.

Self-hosting mStream: requirements and cost

mStream demand is shaped by library size, metadata scans, artwork, waveforms, uploads, concurrent listeners, audio bitrate, search activity, and any transcoding. mStream has PostgreSQL and MariaDB marked Not required in the catalogue. Storage becomes the practical constraint because the music collection and generated library data consume the hosted allocation. mStream is marked storage-driven in the plan mapping, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 provides more room for a large working set.

On AvaHost, mStream uses Plan 1 at €2. The hosted mStream package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. No music, content licence, metadata subscription, mobile application entitlement, downloader account, or external discovery service is included. Users must upload authorised media, connect compatible clients, and monitor storage. Optional integrations can change independently and remain outside AvaHost’s service responsibility.