Application hosting

Hosting Navidrome

A self-hosted music server for a personal audio collection. Persistent library storage and correct file permissions matter as much as the application container.

Min vCPU
Not specified
Min memory
Not specified
Min storage
Not specified

Understand the setup

Check runtime, storage and installation requirements before choosing a server.

See requirements

Budget your resources

Allow room for the operating system, database and your actual workload.

Open resource planner

Build your shortlist

Compare plan details and review which requirements still need checking.

Explore plans

Must have

Installation requirements

  • Docker and an image matching the host architecture.
  • Writable /data and readable music directories for the configured container user.

Recommended

Planning guidance

No further general recommendations are published for this version.

Capacity depends on your workload

No fixed CPU or RAM minimum is established by this guide. Library size and simultaneous playback need separate capacity planning.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Docker Compose
  • Docker container

The host must provide

Runtime

Official Navidrome image
Linux AMD64 and supported ARM platforms

Storage

Persistent data

Persist /data for the database and cache. Mount the music library read-only when using the documented Compose setup.

Step by step

Plan a Navidrome deployment

  1. Mount the library

    Map your data and music directories and choose a matching UID:GID.

    Official instructions
  2. Check access

    Confirm the data directory is writable and the music library is readable before opening the service.

    Official instructions

Security

Before you go public

  • Run with appropriate user permissions instead of root.
  • Protect remote access and retain backups.

Cost

Beyond the server price

  • Allow for music storage, backups and transfer; no playback benchmark is assumed.

Matching plans

Explore hosting options

OVHcloud

OVHcloud VPS-4 (US)

8 vCPU
24 GB RAM
200 GB Storage
— Transfer
  • Virtual Core
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Scaleway

Scaleway DEV1-S (Paris)

2 vCPU
2 GB RAM
— Storage
— Transfer
  • Shared vCPU (AMD EPYC)
  • Dynamic Local SSD or Block (bi...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
SiteGround

SiteGround Jump Start Managed Cloud VPS

4 vCPU
8 GB RAM
40 GB Storage
5 TB Transfer
  • Dedicated CPU (Google Cloud)
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
SiteGround

SiteGround StartUp Managed WordPress

10 GB Storage
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vercel

Hobby

Deployment
Application platform
Billing scope
Subscription plus applicable plan limits
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vercel

Pro

Included usage credit
20 USD/month
Deployment
Application platform
Billing scope
Subscription plus metered usage
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 1 vCPU / 0.5 GB

1 vCPU
0.5 GB RAM
10 GB Storage
500 GB Transfer
  • Shared vCPU (previous-generati...
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 1 vCPU / 1 GB

1 vCPU
1 GB RAM
25 GB Storage
1 TB Transfer
  • Shared vCPU
  • Standard SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 1 vCPU / 2 GB

1 vCPU
2 GB RAM
55 GB Storage
2 TB Transfer
  • Shared vCPU (previous-generati...
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 16 vCPU / 64 GB

16 vCPU
64 GB RAM
1,280 GB Storage
10 TB Transfer
  • Shared vCPU (previous-generati...
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 2 vCPU / 2 GB

2 vCPU
2 GB RAM
65 GB Storage
3 TB Transfer
  • Shared vCPU (previous-generati...
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.
Vultr

Vultr Cloud Compute · 2 vCPU / 4 GB

2 vCPU
4 GB RAM
80 GB Storage
3 TB Transfer
  • Shared vCPU (previous-generati...
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker and an image matching the host architecture.This prerequisite has no comparable published plan field.
  • Writable /data and readable music directories for the configured container user.This prerequisite has no comparable published plan field.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.