EnvironmentDisposable Proxmox LXC
Tested Proxmox deployment
Keep the Proxmox host clean and the media server replaceable.
Finetic’s maintained Compose stack was tested inside a disposable Proxmox LXC. The recommended boundary is a dedicated guest with explicit storage, networking and device access—not application packages installed directly onto the Proxmox host.
Pull the signed imageCompiled x64 or ARM64 server
CompleteStart PostgreSQLHealth-checked persistent database
Healthy03
Mount media read-onlyKeep existing libraries in place
Ready04
Start the 30-day trialOpen the graphical first-run wizard
Next- Server
- Public pre-release evaluation through Docker Compose
- Web client
- Available with the server
- Fire TV & Android
- Supervised device testing
- Paid launch
- Pricing and final terms pending
DatabasePostgreSQL restored
MediaRead-only tested
LifecycleReplacement tested
From source facts to a dependable system.
Each guide connects the visible outcome to the playback, infrastructure and recovery decisions underneath it.
Choose a guest boundary deliberately
A small Linux VM provides the strongest isolation and the simplest Docker support. An LXC can use fewer resources, but nesting, UID mapping and GPU delegation require more care. In either case, leave the Proxmox host responsible for virtualisation and storage rather than turning it into the application runtime.
Mount media without making Finetic its owner
Expose media to the guest at a stable path, then bind it read-only into the Finetic container. Keep PostgreSQL, configuration, artwork, cache and backups on persistent guest storage. Confirm the guest can traverse every parent directory before starting the first scan.
Delegate hardware only when needed
Intel or AMD video devices must be visible to the guest before Docker can map /dev/dri. NVIDIA requires a compatible host driver strategy and container runtime inside the guest. Record device groups and validate a real encode/decode path; the presence of a device node does not prove tone mapping or subtitle burn-in works.
Use Proxmox and Finetic backups for different layers
A guest snapshot is useful before infrastructure changes, while Finetic’s backup captures application and database state in a product-aware form. Keep at least one backup outside the guest and test restoration after recreating the containers.
Evidence from the disposable deployment
On 20 July 2026, the public stack was exercised with Docker Engine 26.1.5 and Compose 2.26.1 in a disposable Proxmox LXC. Testing covered PostgreSQL-dependent startup, health checks, runtime UID/GID, read-only media, signed trial activation, application replacement and complete PostgreSQL plus persistent-volume restoration after container and volume deletion.
Product evidence
The tested container becomes the same complete server.
The disposable Proxmox test exercised startup, persistence, activation, replacement and restoration before this deployment guidance was published.
Practical self-hosting guides
Move from the playback decision to the hardware, public route and recovery boundary behind it.
MigrationMove safely from Jellyfin
See the tested dry-run, matching, activation and per-user state transfer workflow.
Read guide PlaybackDirect Play vs remux vs transcodingUnderstand what each path changes and why files that look compatible may still need conversion.
Read guide EvidenceBenchmark playback honestlyMeasure first frame, seeks, delivery paths and failures without hiding inconvenient results.
Read guide HardwareChoose media-server hardwareSize CPU, GPU, memory, storage and networking around real simultaneous workloads.
Read guide ProxmoxDeploy inside a dedicated guestUse tested Compose, persistent state, read-only media and explicit GPU delegation.
You are here UnraidMap Finetic onto UnraidTranslate appdata, media shares, identities and GPU devices without overstating certification.
Read guide TrueNAS SCALESeparate storage from runtimePlan datasets, PostgreSQL persistence, cache and backups through the public container contract.
Read guide Remote accessVerify the complete public routeConnect DNS, HTTPS, NAT, byte ranges, HLS and WebSockets without exposing management services.
Read guide SecurityProtect a self-hosted media serverUse explicit accounts, bounded sharing, verified updates, safe diagnostics and tested recovery.
Read guideComplete 30-day evaluation
See whether Finetic earns a place in your home.
Install the compiled server with Docker Compose and evaluate every server feature. No card, automatic charge or source-repository access is required.