Requisitos de hardware do Medusa: RAM, CPU, armazenamento e automatização da biblioteca de TV
Planeie o hardware do Medusa para RAM, CPU, análises da biblioteca de TV, integração com o downloader, armazenamento e recomendações práticas de implementação do ZimaOS.
Medusa hardware requirements at a glance
Size Medusa from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- App database/cache plus TV downloads and library
- Runtime
- Python 3.9–3.13 for source installs
- Database
- SQLite-based application databases
- Best Zima starting point
- ZimaBoard 2 832 for automation; ZimaCube for large TV storage
From official requirements to the right setup
Start with upstream facts for Medusa, then size the workload instead of copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- TV library size
- Indexer count
- Search frequency
- Downloader integration
- Post-processing
- Subtitle downloads
- MediaInfo use
- Backup retention
Official minimum requirements
Upstream publishes Python and Docker deployment information but no numerical whole-host CPU, RAM, or disk minimum.
Do not invent a 1 GB/2 GB minimum. Medusa itself is modest; the downloader stack, metadata work, post-processing, and TV media library determine real sizing.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Post-processing and scans drive CPU. | |
| No numerical official minimum published | Depends on library and integrations. | |
| 3.9 through 3.13 | Required for source deployment. | |
| Direct project build available for x86 | Alternate LinuxServer builds exist for other architectures. | |
| SQLite database files | Backups are important before migration. | |
| Optional but highly recommended on Linux | Improves media metadata handling. | |
| Not required | No GPU requirement for Medusa itself. |
When to upgrade your hardware
Large scans
Media growth
Automation stack growth
Plan hardware growth with confidence
SSD app state
Keep database and cache on SSD.
SSDMore RAM
Useful when Medusa shares the host with download/indexer apps.
Higher-RAM hostTV library storage
Use large HDD arrays for retained episodes and backups.
ZimaCube-class storageFaster CPU
Helps repeated scans and post-processing.
Higher-throughput CPUCan it run on ZimaOS?
Install Medusa from the ZimaOS App Store
A specific public Medusa App Store page is available.
Open Medusa in the ZimaOS App Store ↗Follow the upstream project
Use the current Medusa repository for Python versions, Docker status, and migration warnings.
Open Medusa repository ↗Keep database and media persistent
Map application databases and media/download paths to durable storage.
Review Medusa deployment guidance ↗Zima hardware for Medusa
Medusa itself is not the largest resource consumer; TV storage, scanning, and the downloader/indexer ecosystem dominate sizing.
Choose by workload
Use ZimaBoard for the app and separate media disks.
Storage capacity and scan/post-processing throughput become more important.
Zima recommendations are workload-based and do not convert community container labels into official upstream minima.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small home-server workloads | Single-app or small multi-app deployments |
|
8 GB RAM and the 4-core N150 can constrain heavier game servers, large scans, and multi-service consolidation | Get Now |
| ZimaCube 2 Standard | Storage-heavy media, archives, downloads, and long retention | Large persistent data sets where drive bays matter more than peak CPU |
|
8 GB RAM can be lower than ZimaBoard 2 1664 for memory-heavy applications | Get Now |
| ZimaCube 2 Pro | CPU-heavier, higher-concurrency, and consolidated workloads | Game servers, repeated media scans, higher concurrency, or many demanding containers |
|
16 GB RAM can still constrain very large game or database workloads | 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
How much RAM does Medusa need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does Medusa need?
No numerical official CPU minimum is published.
Which Python versions are supported?
The current project states Python 3.9 through 3.13 for source installs.
Does Medusa support Docker?
Yes. The upstream project provides a direct Docker build for x86.
How much storage should I plan?
Size primarily for TV downloads, the final TV library, metadata, and backups.
Can ZimaBoard 2 832 run Medusa?
Yes for a typical home automation setup.
Does Medusa need a GPU?
No.
When should I choose ZimaCube 2?
For larger TV libraries, more disks, or heavier post-processing.
