Video transcodes and image/media processing can consume far more CPU/GPU/RAM than Jellyseerr. Upgrade according to the media server, not request count.
All-in-one media servers.Jellyseerr Hardware Requirements: RAM, Database & Seerr Migration
Learn Jellyseerr CPU, RAM, database and media-request requirements, plus the 2026 migration path to Seerr on ZimaOS.
Jellyseerr requirements at a glance
Jellyseerr does not publish a formal CPU or RAM minimum. More importantly, Jellyseerr and Overseerr officially merged into Seerr in February 2026, and Seerr is now the maintained successor. ZimaOS still lists Jellyseerr, so existing installations remain lightweight request-management workloads, but long-term deployments should plan migration to Seerr.
- CPU
- No numerical Jellyseerr/Seerr host minimum. Request management, metadata calls, library sync and notifications are light compared with actual Jellyfin/Plex/Emby media serving.
- RAM
- No numerical official minimum. Media-server transcoding RAM does not belong to Jellyseerr.
- Database
- The maintained Seerr successor uses SQLite by default and also supports PostgreSQL. Existing Jellyseerr data can be migrated automatically by Seerr.
- Storage
- Persist the configuration/database. Requests, users and integrations are important state even though the footprint is small.
- 2026 status
- Seerr became the official unified successor in February 2026. The current migration guide supports Jellyseerr data migration on first Seerr startup.
- Best Zima starting point
- ZimaBoard 2 832 is already ample for Jellyseerr/Seerr. Choose larger hardware for Jellyfin/Plex, Sonarr/Radarr, download clients and storage—not the request manager itself.
From official requirements to the right setup
Jellyseerr hardware sizing should be separated from the media and automation services it controls.
-
Official requirements
Treat Jellyseerr as a request/control-plane app. Jellyfin/Plex/Emby performs media playback/transcoding, while Sonarr/Radarr and download clients perform acquisition and file operations.
-
Confirm your needs
Keep the Jellyseerr config/database persistent. User accounts, request history and service integrations matter more to recovery than the small application binaries.
-
Leave room to grow
Plan the 2026 Seerr migration. Official Seerr documentation says existing Jellyseerr data can migrate automatically on first startup when the config/data is copied and permissions are correct.
-
Run it on ZimaOS
Run Jellyseerr/Seerr with representative library scans and requests, but size CPU, GPU and storage from the actual media server and download stack separately.
Check every playback client
- Existing Jellyseerr versus new Seerr deployment
- Jellyfin/Plex/Emby integration
- Sonarr and Radarr integration
- SQLite or PostgreSQL after migration
- Persistent config/database backup
- Library size and periodic sync
- Notification integrations
- Media-server hardware sized separately
Official minimum requirements
Neither legacy Jellyseerr nor current Seerr publishes a universal host CPU/RAM minimum in the deployment documentation.
Do not borrow Jellyfin's media-server RAM recommendations for Jellyseerr. The request manager does not transcode media. The important current requirement is migration and maintenance status: Seerr is now the supported project.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical host minimum published | Request management and metadata/API activity are lightweight compared with media serving. |
| RAM | No numerical host minimum published | Do not confuse Jellyseerr with Jellyfin server requirements. |
| Current successor | Seerr | Jellyseerr and Overseerr officially merged into Seerr in February 2026. |
| Seerr default database | SQLite | PostgreSQL is also supported. |
| Seerr port | 5055 | Current Seerr Docker/getting-started default. |
| GPU | Not required | Transcoding occurs in Jellyfin/Plex/Emby, not Jellyseerr/Seerr. |
When to upgrade your hardware
Jellyseerr itself rarely drives upgrades; the surrounding media stack does.
The same host runs Jellyfin/Plex transcoding
The automation/download stack grows
You migrate to PostgreSQL for a larger Seerr deployment
Sonarr, Radarr, Prowlarr and download clients add databases, scans and disk/network I/O. The combined stack can justify more RAM and SSD appdata.
Larger automated media servers.Seerr supports PostgreSQL as well as SQLite. The database becomes another service with its own memory, storage and backup requirements.
Larger teams or managed database environments.Plan hardware growth with confidence
Scale the request layer by keeping its database healthy and moving to Seerr, not by buying GPU hardware.
Migrate legacy Jellyseerr to Seerr
Seerr is the maintained unified successor and can automatically migrate Jellyseerr data when the data directory is prepared correctly.
No hardware upgrade is inherently required for migration.Keep SQLite for a normal small deployment
Seerr defaults to SQLite; PostgreSQL is optional rather than mandatory for a household request server.
Use fast local persistent appdata storage.Use PostgreSQL only when its operational benefits justify it
External PostgreSQL adds a connection pool, database service and backup path.
Size PostgreSQL independently from Seerr.Back up before migration
Seerr documents SQLite/PostgreSQL backup paths and the migration guide expects preserving existing appdata so rollback remains possible.
Keep a separate copy of the config/database before switching images.Can it run on ZimaOS?
ZimaOS still lists Jellyseerr under Media, while upstream development has moved to Seerr.
Existing ZimaOS Jellyseerr installations remain identifiable
The current ZimaOS App Store still exposes Jellyseerr as a Media app.
Open Jellyseerr in the ZimaOS App StorePlan migration to Seerr
The official Seerr team merged Jellyseerr and Overseerr into one maintained codebase in February 2026.
Read the Seerr release announcementBack up and follow the official migration guide
Seerr automatically migrates Jellyseerr data on first startup, but the project provides platform-specific migration and permission steps.
Read the Seerr migration guideChoose Zima hardware for Jellyseerr / Seerr
The request manager is light. Pick Zima hardware from the media server, automation stack and storage that sit behind it.
Is this a request manager only, or part of a full all-in-one media server?
Request manager plus light automation
ZimaBoard 2 832 is ample for Jellyseerr/Seerr and several *Arr services.
- Normal request/automation hostZimaBoard 2 832
- Larger automation/container stackZimaBoard 2 1664
All-in-one media library and storage server
Use ZimaCube for the media/storage workload rather than Jellyseerr.
- Integrated multi-drive media serverZimaCube 2 Standard
No fixed requests/users/library-size benchmark is implied. External API latency, database choice and library sync affect the request app, while transcoding/storage requirements belong to other services.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Jellyseerr/Seerr plus Sonarr, Radarr and similar lightweight services. | Request management, library sync and notifications. |
|
Media transcoding is a separate Jellyfin/Plex workload. | Get Now |
| ZimaBoard 2 1664 | A larger *Arr/request-management stack. | More containers, databases and automation services. |
|
16 GB is for the combined media-control stack, not Jellyseerr alone. | Get Now |
| ZimaCube 2 Standard | A multi-drive media server that also runs Jellyseerr/Seerr. | Media storage plus request and automation services. |
|
Choose it for media capacity and broader server workload. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around Jellyseerr's 2026 status, Seerr migration, RAM, SQLite/PostgreSQL and whether media-server hardware belongs to the request app. Reddit migration discussions were used to reflect current user confusion.
Is Jellyseerr discontinued in 2026?
As an independent project, yes: the Jellyseerr and Overseerr teams officially merged into Seerr in February 2026. Seerr is now the maintained unified successor.
Does ZimaOS still have Jellyseerr?
Yes. ZimaOS currently still lists a Jellyseerr Media app even though upstream development has moved to Seerr.
How much RAM does Jellyseerr need?
There is no official numerical host minimum. Jellyseerr/Seerr is a request-management service, so its own RAM needs are far below the media server that may be transcoding video.
Does Jellyseerr need the same hardware as Jellyfin?
No. Jellyseerr sends requests and syncs media status; Jellyfin performs playback and transcoding. GPU and heavy CPU requirements belong to Jellyfin, not Jellyseerr.
Can I migrate Jellyseerr to Seerr without losing requests?
Yes. Seerr's official migration guide says Jellyseerr data is migrated automatically on first startup when the existing data/config is copied or mounted correctly.
Should Seerr use SQLite or PostgreSQL?
SQLite is the current default and is appropriate for many household deployments. PostgreSQL is optional when you deliberately want an external managed database.
Can ZimaBoard 2 832 run Jellyseerr or Seerr?
Yes. Its Intel N150 and 8 GB RAM provide very large headroom for the request manager and several companion automation apps.
Should I buy stronger hardware before migrating from Jellyseerr to Seerr?
Not because of the migration itself. Upgrade only if the surrounding Jellyfin/Plex, download, database or storage workload already needs more capacity.
What sources and further reading informed this Jellyseerr hardware guide?
Seerr's official February 2026 release announcement and migration guide define Jellyseerr's successor status and migration path. Current Seerr database documentation defines SQLite/PostgreSQL behavior. Reddit was used for query fan-out around migration timing, while ZimaOS confirms the Jellyseerr package still exists.
