Telebugs Hardware Requirements: RAM, CPU, Storage & Error Event Throughput
Plan Telebugs hardware for RAM, CPU, disk retention, error-event throughput, Docker, and practical ZimaOS deployment recommendations.
Telebugs hardware requirements at a glance
Size Telebugs from verified upstream requirements first, then add headroom for the workload and persistent data.
- RAM
- Recommended minimum: 1 GB
- CPU
- Recommended minimum: 1 core
- Storage
- Recommended minimum: 40 GB
- Runtime
- Docker-based
- Architecture
- AMD64 and ARM64
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Telebugs sizing is straightforward: start from its published minimum, then use report volume, pending ingest backlog, retention, attachments, and response latency to decide when to scale.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Reports per second
- Pending ingest backlog
- Retention period
- Attachment volume
- HTTP p95 latency
- Failed jobs
- Backup retention
- Other containers on host
Official minimum requirements
Telebugs publishes numerical recommended minimum and small-to-medium project tiers, so these can be used directly without inventing a host floor.
Treat 1 core/1 GB/40 GB as Telebugs' documented recommended minimum, not as a guarantee for every workload. Sustained ingest and retention still determine practical capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 1 core | Small-to-medium projects: 2 cores. | |
| 1 GB | Small-to-medium projects: 4 GB. | |
| 40 GB | Small-to-medium projects: 40โ80 GB. | |
| Docker | Documented self-hosted deployment is Docker-based. | |
| AMD64 and ARM64 | Supported by the included Docker image. | |
| Not required | No GPU requirement is documented for error tracking. |
When to upgrade your hardware
Ingest backlog
Memory pressure
Retention growth
Plan hardware growth with confidence
SSD for event data
Fast persistent storage helps keep ingest and query latency predictable.
SSDRAM headroom
Move beyond 1 GB as project count, event volume, and background work increase.
4 GB+ practical memoryRetention capacity
Increase disk beyond 40 GB when keeping more historical events or attachments.
Larger SSD/HDD poolCPU for sustained ingest
More CPU helps Telebugs process sustained error bursts without a growing backlog.
2+ cores for small-to-medium workloadsCan it run on ZimaOS?
Custom install Telebugs in ZimaOS
No specific public official ZimaOS one-click page was verified, so use the Custom Install route and the vendor's Docker deployment.
Custom install Telebugs in the ZimaOS app โUse Telebugs' Docker deployment
Telebugs is designed to run as a self-hosted Docker container on customer-controlled infrastructure.
Open Telebugs installation requirements โMeasure ingest rather than guessing
Telebugs' capacity guidance emphasizes end-to-end processed reports, pending ingest backlog, latency, and failed jobs.
Open Telebugs system requirements โZima hardware for Telebugs
Telebugs is light enough that ZimaBoard 2 832 already exceeds the vendor's small-to-medium CPU/RAM guidance; storage retention is the more likely long-term growth variable.
Choose by workload
The vendor's published 2-core/4 GB small-to-medium guidance fits comfortably inside ZimaBoard 2 832.
Scale storage first when history grows, then CPU when pending ingest or latency shows processing pressure.
The mapping is workload guidance, not a Telebugs certification of Zima hardware. Preserve enough storage for retention and backups rather than relying on the onboard eMMC.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and N150 CPU limit heavy databases, large observability stacks, and compute-heavy jobs | Get Now |
| ZimaCube 2 Standard | Storage-heavy services, archives, and growing file libraries | Large persistent data sets where drive bays matter more than CPU throughput |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy applications | 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 Telebugs need?
Telebugs documents 1 GB as the recommended minimum and 4 GB for small-to-medium projects.
How many CPU cores does Telebugs need?
The documented recommended minimum is 1 core; small-to-medium projects are listed at 2 cores.
How much disk space does Telebugs need?
The documented recommended minimum is 40 GB, while small-to-medium projects are listed at 40โ80 GB.
Does Telebugs use Docker?
Yes. Its self-hosted deployment is Docker-based.
Which CPU architectures are supported?
Telebugs states that its Docker image supports AMD64/x86-64 and ARM64/AArch64.
Can ZimaBoard 2 832 run Telebugs?
Yes as a practical starting point: its 4-core N150 and 8 GB RAM exceed Telebugs' published small-to-medium CPU/RAM guidance.
What should I monitor before upgrading?
Watch reports processed end-to-end, pending ingest backlog, HTTP p95 latency, failed jobs, disk growth, and retention.
When should I choose ZimaCube 2?
Choose it when local retention needs more drive capacity or sustained ingest and consolidation justify stronger CPU/network resources.
