Realtime collaborative editing raises websocket, rendering and database activity.
Teams and classrooms.HedgeDoc Hardware Requirements: RAM, CPU, Database & Storage
Plan HedgeDoc hardware for RAM, CPU, PostgreSQL, uploads, collaboration and Docker, with practical ZimaOS custom-install recommendations.
HedgeDoc requirements at a glance
HedgeDoc is a collaborative Markdown editor backed by a SQL database. Current Docker docs publish software prerequisites but no universal runtime CPU/RAM minimum; the manual build path requires at least 2 GB RAM to build the frontend.
- RAM
- No numerical official runtime minimum published. The 2 GB figure in upstream docs applies to building the frontend from source, not to the normal prebuilt Docker runtime.
- CPU
- No numerical official core minimum. Concurrent editing, Markdown rendering, uploads and database activity determine practical CPU use.
- Database
- Docker examples use PostgreSQL; manual installation also supports MySQL, MariaDB and SQLite.
- Storage
- No universal official minimum. Database data, uploaded files and backups determine capacity.
- Architecture
- Official HedgeDoc container images currently support amd64 and arm64.
- Best Zima starting point
- ZimaBoard 2 832 is ample for a small team; use SSD-backed PostgreSQL and more RAM for heavier collaboration or more co-hosted apps.
From official requirements to the right setup
Size HedgeDoc from collaborative usage, database load and upload storage rather than the frontend-build requirement.
-
Official requirements
Use the official HedgeDoc Docker image with Docker Compose and a persistent database. The current minimal example uses PostgreSQL.
-
Confirm your needs
Do not interpret the documented 2 GB RAM frontend-build requirement as the runtime requirement for the prebuilt container.
-
Leave room to grow
Estimate concurrent editors, note count and uploads. For production, upstream strongly recommends a server database rather than SQLite except for very small/single-user cases.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official image, persist the database and uploads volume, configure CMD_DOMAIN/CMD_DB_URL, and place the service behind HTTPS.
Check every playback client
- Concurrent editors
- Note count
- Upload volume
- PostgreSQL vs SQLite
- Database persistence
- Uploads persistence
- HTTPS/domain
- Backup retention
Official minimum requirements
HedgeDoc's current docs define software prerequisites and one build-time RAM figure rather than a runtime sizing table.
The 2 GB figure is specifically for building the HedgeDoc frontend from source. A normal Docker deployment should be sized around database, uploads and collaboration load.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Runtime RAM minimum | No numerical official minimum published | The documented 2 GB applies to frontend builds. |
| Frontend build RAM | At least 2 GB | Only needed when building the frontend from source. |
| CPU minimum | No numerical official minimum published | Concurrency and database activity drive demand. |
| Docker prerequisites | Git, Docker 17.03.1+ and Docker Compose | Current official Docker requirements. |
| Architectures | amd64 and arm64 | Current official container support. |
| Production database | Server database recommended | Upstream recommends PostgreSQL/MySQL/MariaDB over SQLite for production. |
When to upgrade your hardware
HedgeDoc should scale when collaboration, uploads or database activity creates sustained contention.
Concurrent editors increase
Uploads and note history grow
Database contention appears
Persistent uploads and database size increase storage and backup requirements.
Long-running knowledge bases.A production database may need more RAM/IO as note activity grows.
Shared public or team instances.Plan hardware growth with confidence
Scale HedgeDoc around PostgreSQL and persistent uploads before adding unnecessary compute.
Use SSD-backed PostgreSQL storage
Low-latency durable storage improves collaborative database responsiveness.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 8 GB for a comfortable small-team host
HedgeDoc itself is light, while PostgreSQL and other ZimaOS apps share the system.
ZimaBoard 2 832.Move to 16 GB for heavier collaboration stacks
More RAM helps PostgreSQL and additional productivity services coexist.
ZimaBoard 2 1664.Use ZimaCube when uploads/backups become storage-heavy
Larger local file retention can justify a multi-drive platform.
ZimaCube 2 Standard.Can it run on ZimaOS?
HedgeDoc is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App using the official HedgeDoc image.
Custom install HedgeDoc in ZimaOS
Use Install Custom App with quay.io/hedgedoc/hedgedoc, persist uploads and the SQL database, and map container port 3000 to an available ZimaOS host port.
Custom install HedgeDoc in the ZimaOS app โUse HedgeDoc's official Docker setup
The official Docker guide provides a Compose example with PostgreSQL and the HedgeDoc app container.
Review HedgeDoc Docker setup โUse a production-grade database
Upstream strongly recommends a server database rather than SQLite for production except very small instances.
Review HedgeDoc production guidance โChoose Zima hardware for HedgeDoc
HedgeDoc is lightweight enough for ZimaBoard 2; SQL persistence and collaboration scale determine when more resources help.
Is this a small-team editor or a larger collaborative knowledge service?
Small team / normal note collaboration
Use ZimaBoard 2 with SSD-backed PostgreSQL and uploads.
- Best starting pointZimaBoard 2 832
- More headroomZimaBoard 2 1664
Large uploads or broader productivity server
Use ZimaCube when file/backup capacity becomes the main driver.
- Storage-first platformZimaCube 2 Standard
These are workload recommendations, not official editor-count or note-throughput tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small HedgeDoc teams. | HedgeDoc, PostgreSQL, uploads and normal collaborative editing. |
|
The 2 GB upstream figure is build-time only; 8 GB provides comfortable whole-host headroom. | Get Now |
| ZimaBoard 2 1664 | Larger collaboration/productivity stacks. | More editors, PostgreSQL cache and co-hosted services. |
|
16 GB is practical headroom, not an official HedgeDoc runtime requirement. | Get Now |
| ZimaCube 2 Standard | Upload-heavy HedgeDoc on a broader NAS. | HedgeDoc plus larger attachments, backups and shared storage. |
|
Choose it mainly for storage topology. | 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 HedgeDoc RAM, CPU, databases, Docker, frontend builds and ZimaOS deployment.
How much RAM does HedgeDoc need?
HedgeDoc does not publish a numerical runtime RAM minimum. The documented 2 GB figure is for building the frontend from source.
How many CPU cores does HedgeDoc need?
No numerical official core minimum is published.
Which database should HedgeDoc use?
The official Docker example uses PostgreSQL, and production guidance recommends a server database rather than SQLite for most shared instances.
Does HedgeDoc support ARM64?
Yes. Current official container images support amd64 and arm64.
How much storage does HedgeDoc need?
No universal disk minimum is published; database data, uploads and backups determine capacity.
Does HedgeDoc need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run HedgeDoc?
Yes. The 8 GB model is ample for a small team with persistent PostgreSQL and uploads.
Why does HedgeDoc mention 2 GB RAM?
That requirement is for building the frontend from source; release tarballs and container images avoid that build step.
What sources informed this HedgeDoc hardware guide?
The guide uses HedgeDoc's current Docker, manual installation and production guidance plus current Zima product pages.
