More concurrent page requests, logged-in members, admin activity and dynamic theme rendering can push a small host beyond the 1 GB floor even when average traffic is modest.
Growing publications, launches and sites with bursty social/referral traffic.Requisitos de hardware do Ghost: RAM, MySQL, armazenamento e Docker
Planeie o hardware para o Ghost CMS tendo em conta a RAM, CPU, MySQL, armazenamento, Docker, análises e o crescimento do tráfego, com recomendações práticas para uma instalação personalizada do ZimaOS.
APP
Ghost requirements at a glance
Ghost's supported production stack publishes a clear 1 GB memory floor but no universal CPU or storage minimum. Ghost 6 also introduces an official Docker Compose preview with Ghost, MySQL and Caddy, using a 2 GB/1 CPU Linux server as its example host. Treat these figures as deployment baselines rather than a guarantee for high-traffic publications.
- RAM
- Official self-hosting guidance: at least 1 GB server memory. The Ghost 6 Docker preview uses a 2 GB/1 CPU Linux server as its example host.
- CPU
- No numerical official minimum published. The Docker preview example uses 1 CPU; traffic, theme rendering and companion services determine when more CPU is useful.
- Storage
- No numerical official minimum published. Capacity must cover MySQL, Ghost content, images/files, Docker data, logs, updates and backups.
- Database
- Ghost's supported production stack uses MySQL 8. The Docker preview includes a MySQL service alongside Ghost and Caddy.
- GPU
- No GPU is required for normal Ghost publishing, membership or newsletter workloads.
- Best Zima starting point
- ZimaBoard 2 832 is already a comfortable small-publication host; move to 16 GB or ZimaCube 2 when Ghost shares the system with more apps, storage, analytics services or heavier traffic.
From official requirements to the right setup
Size Ghost as a publication stack, not only as a Node.js process. Memory, MySQL, image/file growth, TLS, backups and optional analytics or social-web services all contribute to the real host requirement.
-
Official requirements
Start with Ghost's official production baseline: a supported Linux stack with MySQL 8 and at least 1 GB memory. For the newer Docker Compose preview, use the official example of a Linux server in the 2 GB/1 CPU class as a deployment reference rather than a formal CPU minimum.
-
Confirm your needs
Estimate publication workload: anonymous traffic, logged-in members, theme complexity, image/file uploads, admin activity and bulk newsletter operations can change CPU, memory and storage demand.
-
Leave room to grow
Budget persistent storage for MySQL, Ghost content, uploaded media, Docker volumes, logs and backups. Keep independent backup capacity outside the live application volume.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Ghost Docker tooling adapted to the dashboard. Persist Ghost and MySQL data, configure domain/DNS, HTTPS, SMTP and secrets, then monitor memory, database growth and disk use before scaling.
Check every playback client
- Ghost version and CLI or Docker deployment path
- Expected monthly traffic and traffic spikes
- Member and staff activity
- Image, audio and file-upload growth
- MySQL persistence and backup plan
- Domain, DNS and HTTPS configuration
- SMTP/newsletter delivery provider
- Analytics, ActivityPub and other ZimaOS services
Official minimum requirements
Ghost publishes an official memory floor for the supported self-hosted stack, but it does not publish a universal production CPU-core or disk-capacity minimum.
Use 1 GB as the official Ghost memory floor, not as a recommendation for a whole ZimaOS server. A 2 GB/1 CPU server appears in Ghost's Docker preview as an example environment, while practical Zima deployments should reserve additional memory and storage for MySQL, Docker, backups and co-hosted apps.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Server memory | At least 1 GB | Ghost lists this as part of its officially supported and recommended self-hosting stack. |
| CPU minimum | No numerical official minimum published | The Docker preview gives a 2 GB/1 CPU Linux server as an example host, not a universal performance guarantee. |
| Storage minimum | No numerical official minimum published | Plan storage around MySQL, media, Docker volumes, logs, updates and backup retention. |
| Database | MySQL 8.0 | Ghost's current supported production stack specifies MySQL 8. |
| Supported stack | Ubuntu 24, Node.js 22 LTS, MySQL 8.0, NGINX, systemd | This is the current narrow stack Ghost documents and tests for Ghost-CLI production hosting. |
| Docker preview | Linux server, Docker 20.10.13+, domain and SMTP service | The Ghost 6 Docker tooling runs Ghost, Caddy and MySQL and can optionally add self-hosting features. |
When to upgrade your hardware
Ghost usually needs more hardware when database activity, traffic, uploaded media or companion services grow—not simply because the post count increases.
Traffic spikes consume CPU or memory headroom
MySQL and content storage keep expanding
You self-host more of Ghost's surrounding stack
Posts, members, analytics metadata, images, files, logs and backups create persistent storage growth and a larger database working set.
Long-running publications, media-heavy sites and membership businesses.Ghost 6 can add Docker-based services for features such as analytics and ActivityPub. Co-hosting them, plus other ZimaOS apps, increases whole-host memory and operational complexity.
Users moving from a minimal blog to a broader self-hosted publishing platform.Plan hardware growth with confidence
Scale Ghost by protecting database and media persistence first, then add memory or CPU only when the publication workload shows that the current host is constrained.
Put Ghost and MySQL data on SSD-backed storage
A responsive database and reliable persistent volumes matter more than raw GPU performance for a publishing platform.
Use SATA SSD/NVMe with ZimaBoard 2 or ZimaCube 2 rather than keeping the only live database and content copy on onboard eMMC.Add memory for MySQL and co-hosted services
The official 1 GB figure is a floor. More RAM gives MySQL, Docker and other ZimaOS services room without forcing the host into memory pressure during updates or traffic bursts.
ZimaBoard 2 832 is enough for a small publication; ZimaBoard 2 1664 offers more consolidation headroom.Keep large media and backups separate from the boot volume
Images, audio, downloadable files and backup archives can grow much faster than the Ghost application itself.
Use ZimaCube 2 or added SATA storage when the publication becomes media-heavy or requires longer backup retention.Scale CPU and platform size when traffic or companion apps justify it
A stronger CPU helps with sustained dynamic traffic and broader server consolidation, but it should follow real monitoring rather than replace CDN/cache strategy.
ZimaCube 2 Pro is appropriate when Ghost is one workload in a larger always-on self-hosted platform.Can it run on ZimaOS?
Ghost is not currently presented in the public ZimaOS hardware catalog as a one-click ZimaOS App Store app. You can still deploy Ghost through Install Custom App using the official Ghost 6 Docker Compose tooling, with persistent MySQL and content volumes.
Custom install Ghost in ZimaOS
Use Install Custom App from the ZimaOS dashboard with an adapted Compose definition based on the official Ghost Docker tooling. Persist Ghost content and MySQL data, set the domain and database secrets, and verify Caddy/reverse-proxy, HTTPS and SMTP behavior before publishing.
Custom install Ghost in the ZimaOS app ↗Use the official Ghost Docker Compose preview
Ghost 6 is moving toward Docker Compose for self-hosting. The official tooling runs Ghost with MySQL and Caddy and is the most relevant upstream reference for a ZimaOS custom-app deployment.
Review Ghost Docker self-hosting ↗Plan domain, HTTPS and SMTP before launch
Ghost's production workflow assumes a real domain, HTTPS and a transactional email service. These are deployment dependencies rather than reasons to buy more CPU or GPU.
Review Ghost hosting guidance ↗Choose Zima hardware for Ghost
Ghost is light enough for ZimaBoard 2, while storage and memory headroom become more important as the publication accumulates media, members, backups and additional self-hosted services.
Is this a small standalone publication or a larger media/multi-service self-hosted platform?
Small blog, newsletter or membership publication
An 8 GB ZimaBoard 2 already provides large headroom over Ghost's official 1 GB memory floor; prioritize SSD persistence and backups.
- Best starting pointZimaBoard 2 832
- More app headroomZimaBoard 2 1664
Media-heavy publication or broader server consolidation
Choose more storage expansion and CPU headroom when Ghost shares the host with analytics, databases, backups and other services.
- Storage-first platformZimaCube 2 Standard
- Heavier multi-service hostZimaCube 2 Pro
These are workload-based recommendations, not guaranteed page-view, member-count or newsletter-throughput benchmarks. Traffic shape, themes, integrations, MySQL size, media volume, analytics, backups and other ZimaOS apps can change resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small to medium Ghost publications with SSD-backed MySQL and content storage. | Ghost, MySQL, HTTPS proxy, backups and a few lightweight companion services. |
|
Add SSD storage for the live database, media and backup workflow; onboard eMMC should not be the only long-term content copy. | Get Now |
| ZimaBoard 2 1664 | Ghost plus more Docker services, larger MySQL cache and additional publishing infrastructure. | Ghost with MySQL, proxy, monitoring, backups and other self-hosted applications sharing the host. |
|
Sixteen gigabytes is consolidation headroom, not a Ghost requirement; high-traffic publishing may still need CDN/caching and stronger CPU rather than only more RAM. | Get Now |
| ZimaCube 2 Standard | A media-heavy Ghost site with larger local content and backup storage. | Ghost plus MySQL, larger image/file libraries, snapshots, backups and multiple home-server services. |
|
Choose it for storage expansion and platform consolidation, not because Ghost alone needs a six-bay NAS. | Get Now |
| ZimaCube 2 Pro | Ghost as part of a heavier self-hosted publishing and data platform. | Higher traffic, many companion apps, fast SSD tiers, long backup retention and broader server consolidation. |
|
Unnecessary for a normal Ghost blog by itself; use this class when the wider host workload and storage design justify it. | 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
These answers cover Ghost RAM, CPU, storage, MySQL, Docker, SSD and ZimaOS custom-install questions while keeping the official minimum separate from practical whole-host sizing.
How much RAM does Ghost need?
Ghost's current self-hosting documentation recommends a server with at least 1 GB of memory. That is an application-stack floor, not a whole ZimaOS recommendation. MySQL, Docker, backups and other apps should have additional headroom.
Can Ghost run on 1 GB RAM?
Yes. One gigabyte is Ghost's published minimum for its supported production stack. A small site can fit that class, but updates, MySQL and traffic spikes leave little margin. ZimaBoard 2's 8 GB is a much more comfortable home-server starting point.
How many CPU cores does Ghost need?
Ghost does not publish a universal CPU-core minimum. Its Ghost 6 Docker preview uses a 2 GB/1 CPU Linux server as an example. More CPU becomes useful with sustained traffic, heavier themes and broader server consolidation.
How much storage does Ghost need?
Ghost does not publish one numerical production disk minimum. Size storage for MySQL, uploaded images and files, Docker volumes, logs, updates and backup retention rather than only the application image.
Does Ghost require MySQL?
Ghost's supported production stack uses MySQL 8. The current Docker Compose preview includes MySQL as part of the standard self-hosted stack.
Does Ghost need an SSD?
SSD is not stated as a strict official minimum, but SSD-backed MySQL and content volumes are a sensible practical choice. Large media archives and backup copies can live on higher-capacity secondary disks.
Can ZimaBoard 2 run Ghost?
Yes. Both ZimaBoard 2 memory configurations are well above Ghost's official 1 GB server-memory floor. The 8 GB model is already a strong small-publication host; add SSD-backed persistent storage and maintain independent backups.
Should I use Ghost-CLI or Docker on ZimaOS?
For ZimaOS Install Custom App, Ghost's new Docker Compose tooling is the more natural reference because it packages Ghost, MySQL and Caddy as containers. Ghost-CLI remains the documented supported stack for traditional Ubuntu servers, while the Docker path is currently a preview.
What sources informed this Ghost hardware guide?
The guide uses current Ghost self-hosting and Docker documentation for memory, supported-stack and deployment claims, and current Zima product pages only for Zima hardware specifications and workload matching.
