Wymagania sprzętowe Sentry Self-Hosted: pamięć RAM, procesor, pamięć masowa i przechowywanie zdarzeń
Zaplanuj sprzęt Sentry Self-Hosted pod kątem pamięci RAM, procesora, przechowywania danych na dysku, usług Docker oraz praktycznych zaleceń dotyczących wdrożenia ZimaOS.
Sentry Self-Hosted hardware requirements at a glance
Size Sentry Self-Hosted from verified upstream requirements first, then add headroom for the workload and persistent data.
- RAM
- Feature-complete installer: 14,000 MB available to containers; upstream comments describe a 16 GB host minimum
- CPU
- Feature-complete: 4 cores available to containers
- Storage
- 20 GB free disk is the documented baseline reference
- Runtime
- Docker/Compose self-hosted stack
- Key workload
- Ingest rate + enabled feature profile + retention
- Best Zima starting point
- ZimaCube 2 Pro for CPU headroom, with RAM treated as a tight constraint
From official requirements to the right setup
Sentry sizing must follow the selected Compose profile first, then event volume, enabled products, and retention.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Compose profile
- CPU cores available to Docker
- RAM available to Docker
- Event ingest rate
- Retention days
- Replay/trace/profile usage
- Disk growth rate
- Backup strategy
Official minimum requirements
Upstream self-hosted documentation and the current installer provide numerical checks, so these can be treated as official runtime requirements rather than community estimates.
Do not collapse the errors-only and feature-complete profiles into one minimum. For feature-complete, 16 GB-class hosts are close to the floor; disk capacity must be sized for retention and traffic.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 4 cores for feature-complete; 2 cores for errors-only | Checked inside the container engine. | |
| 14,000 MB available to containers for feature-complete; 7,000 MB for errors-only | The script comments describe 16 GB minimum host RAM for feature-complete. | |
| 20 GB free disk | Retention and workload can require much more. | |
| Docker/Compose or supported container path | Self-hosted is delivered as a multi-service Compose deployment. | |
| SSE4.2 on relevant x86_64 hosts | Required by ClickHouse unless the documented skip conditions apply. | |
| 9000 | Can be changed through SENTRY_BIND. |
When to upgrade your hardware
Compute pressure
Memory pressure
Retention growth
Plan hardware growth with confidence
Fast service storage
Place databases and hot service data on SSD to reduce latency across Sentry's many containers.
SSD or NVMe working storageMemory headroom
Give the Compose stack memory beyond the hard installer threshold before consolidating more services.
A host with materially more than the minimum RAMRetention capacity
Expand persistent storage as event volume and retention increase; 20 GB is not a realistic ceiling.
Larger SSD/HDD pool with backupsCPU throughput
More CPU helps consumers and background services keep up as ingest and enabled features increase.
Higher-core CPU platformCan it run on ZimaOS?
Custom install Sentry Self-Hosted in ZimaOS
No specific public official ZimaOS one-click App page was verified for this batch. Treat deployment as a custom multi-container stack and preserve the upstream Compose design.
Custom install Sentry Self-Hosted in the ZimaOS app ↗Use the upstream self-hosted deployment
Sentry maintains a self-hosted Docker Compose repository and installer; use that as the technical source of truth for services and upgrades.
Open Sentry self-hosted documentation ↗Check the current installer floor before deployment
The repository's minimum-requirements script can change over time and should be rechecked before publishing or upgrading.
Open current minimum-requirements script ↗Zima hardware for Sentry Self-Hosted
Sentry is compute- and memory-heavier than typical home-server apps because the feature-complete profile is a multi-service observability stack.
Choose by workload
Reduce the Sentry feature footprint first, then keep fast persistent storage and measured headroom.
Prioritize CPU throughput and memory headroom; retention then becomes the storage sizing variable.
Zima product guidance is a practical mapping, not an upstream Sentry certification. A product that only barely meets the RAM floor should not be described as a comfortable production recommendation.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Apps that benefit from more memory while retaining a low-power 4-core CPU | Larger database cache, more containers, and moderate background services |
|
The CPU is still the same 4-core N150; 16 GB RAM does not raise compute throughput | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, database-heavy, and consolidated workloads | More background workers, indexing, reports, or concurrent users |
|
16 GB RAM can still be the limiting factor for software that needs substantially more memory | 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 Sentry Self-Hosted need?
The current installer checks 14,000 MB available to containers for the feature-complete profile and 7,000 MB for errors-only; the script comments describe a 16 GB host minimum for feature-complete.
How many CPU cores does self-hosted Sentry need?
The current hard check is 4 cores for feature-complete and 2 cores for errors-only.
Does Sentry need a database?
Yes. The self-hosted stack includes multiple stateful services rather than a single database process, so whole-stack memory and storage matter.
How much storage should I plan?
Upstream documentation uses 20 GB free disk as a baseline, but retention, event volume, replays, traces, and profiles can make real storage demand much larger.
Does Sentry need a GPU?
No GPU requirement is published for the standard self-hosted stack.
Can ZimaBoard 2 1664 run Sentry?
It has 16 GB RAM and a 4-core N150, so it is near the feature-complete host-memory floor and offers limited headroom. It is better treated as a constrained test or errors-only candidate than a broad production recommendation.
What changes with the errors-only profile?
It removes many feature-complete services and the current installer uses lower hard CPU and RAM checks for that profile.
When should I choose ZimaCube 2 Pro?
Choose the Pro tier when CPU throughput and consolidation headroom matter more than the lowest-power starting point, while still checking whether 16 GB RAM is enough for your actual Sentry workload.
