System requirements
Review Finetic server requirements for Linux, CPU, memory, PostgreSQL, FFmpeg, storage, networking and hardware acceleration.
Supported server shape#
The current production architecture targets a dedicated or virtualised 64-bit Linux host using either x64 or ARM64. Customer releases are compiled production artefacts managed as an unprivileged system service.
| Component | Current requirement |
|---|---|
| Operating system | Supported 64-bit Linux distribution |
| Runtime | Node.js 24–26 in the managed build environment |
| Database | PostgreSQL 15 or newer |
| Media tools | FFmpeg and FFprobe compatible with the release |
| Memory | 4 GB practical minimum; more for concurrent transcodes |
| CPU | Two modern cores for a small Direct Play household |
| Cache | SSD-backed writable storage strongly recommended |
| Network | Stable Ethernet for the server; correct range and streaming proxy behaviour |
CPU and transcoding#
Direct Play mostly consumes storage and network bandwidth. Remuxing changes the container without decoding the original video and is usually much lighter than a full transcode. Video conversion, subtitle burn-in and HDR tone mapping can consume every available software CPU core.
If multiple users may require video conversion, use a supported hardware backend such as Intel Quick Sync, VAAPI or NVIDIA NVENC. Hardware availability alone is not proof that a codec/profile combination works; Finetic verifies the configured path and records the backend selected for each stream.
Memory#
Four gigabytes is a practical starting point for the operating system, PostgreSQL, Finetic and modest background work. Large catalogues, concurrent analysis and multiple transcodes benefit from additional memory. Avoid configuring memory so tightly that the kernel repeatedly reclaims the media cache or terminates FFmpeg.
Storage layout#
Separate three concepts:
- Media storage contains the source files and may be read-only.
- Persistent application data contains configuration, accounts and database state.
- Media cache contains replaceable artwork, subtitles and generated playback assets.
The cache should be local and fast. Network-mounted cache directories increase start latency and make transient network faults look like playback failures.
Network requirements#
The server must be reachable by its clients. LAN discovery can help Fire TV and Android find a local server, but manual HTTPS entry remains important for routed networks and remote access.
A reverse proxy must preserve byte-range requests, streaming response bodies, WebSocket or SSE connections, client timeouts and large responses. Do not buffer live media responses into memory or apply generic response caching to authenticated APIs.
PostgreSQL#
Finetic stores catalogue state, accounts, progress, jobs, history and telemetry in PostgreSQL. The installer requires a dedicated database and least-privilege application role. Back up the database with the Finetic backup workflow rather than copying active database files.
Before you proceed#
Confirm that the server can continuously see every configured media mount, resolve its own public hostname if one is used, write to the selected cache, and execute the supplied FFmpeg/FFprobe tools. Continue with Prepare your server.