Bonfire-hardwarevereisten: RAM, CPU, opslag & gefedereerde taken & media

Plan het RAM, de CPU, persistente opslag en serviceafhankelijkheden van Bonfire, met op workloads gebaseerde dimensionering voor ZimaOS, back-ups en praktische hardwarekeuzes.

Bonfire-hardwarevereisten: RAM, CPU, opslag & gefedereerde taken & media

Bonfire hardware requirements at a glance

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface.

RAM
No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below.
CPU
No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity.
Storage
Persist users/posts, media, federation queues, database and search/cache state.
Required services
Use the supported upstream Bonfire runtime and service topology. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Upstream repository references include PostgreSQL, Redis / Valkey. Confirm which are required in your selected mode rather than enabling all references by default.
Main sizing variable
federation fan-out, active peers, upload volume, timeline queries and queue depth
Practical Zima starting point
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

From official requirements to the right setup

Plan the complete Bonfire workload before selecting a server.

  1. Official requirements

    Choose the exact edition, stable release and supported container/runtime. Use the supported upstream Bonfire runtime and service topology. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Upstream repository references include PostgreSQL, Redis / Valkey. Confirm which are required in your selected mode rather than enabling all references by default.

  2. Confirm your needs

    Test a representative busy operation: federation fan-out, active peers, upload volume, timeline queries and queue depth Record peak resident memory, CPU, disk latency and completion time, including other containers.

  3. Leave room to grow

    Place active state on reliable persistent storage. Persist users/posts, media, federation queues, database and search/cache state. Budget working space for an upgrade or import and test recovery before relying on the deployment.

  4. Run it on ZimaOS

    Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

Check every playback client

  • Exact edition and stable release
  • Supported upstream runtime and architecture
  • All required companion services
  • Realistic peak activity
  • Persistent data and file ownership
  • Free host ports and reachable URLs
  • Working space and backup retention
  • Successful database/file restore

Official minimum requirements

Reviewed November 18, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.

Review Bonfire official requirements

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.

RequirementOfficial minimumWhat this supports
RAM guidanceNo fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below.Official guidance keeps its original test, recommendation or example scope.
CPU guidanceNo fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity.Core counts do not predict a fixed user, device or document capacity.
Storage planningPersist users/posts, media, federation queues, database and search/cache state.Installation space is separate from retained content, working files and backups.
Service topologyUse the supported upstream Bonfire runtime and service topology. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Upstream repository references include PostgreSQL, Redis / Valkey. Confirm which are required in your selected mode rather than enabling all references by default.Include every stateful companion service in the host budget.
Persistent statePersist users/posts, media, federation queues, database and search/cache state.An image rebuild or container replacement is not a backup.
Deployment boundaryCommunity publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.Check the linked project instructions for the selected edition and release.

When to upgrade your hardware

Use observed Bonfire workload pressure to decide when an upgrade is warranted.

Busy operations exceed the available window

The complete stack runs short of memory

Persistent data approaches available capacity

federation fan-out, active peers, upload volume, timeline queries and queue depth Time the job and identify CPU, storage or external-service waits before replacing hardware.

Imports, processing and simultaneous users.

Inspect the application and each required service for OOM events, sustained swap or growing queues. Reduce unnecessary concurrency before adding capacity.

Shared hosts and background work.

Persist users/posts, media, federation queues, database and search/cache state. Track primary state and backup retention separately.

Long-lived installations and growing collections.

Plan hardware growth with confidence

Address storage, memory, compute and deployment limits separately.

Use suitable active storage

Put latency-sensitive application/database state on durable local SSD storage and keep recoverable copies.

SATA or PCIe SSD according to measured data growth.

Add memory for the complete stack

Choose a higher-RAM host when peak application and companion-service usage leaves inadequate OS headroom.

ZimaBoard 2 832 or ZimaBoard 2 1664 according to the measured constraint.

Separate capacity from compute

A multi-drive system helps when retained content and backup storage are the problem; it is not automatically a faster application.

ZimaCube 2 when a broader multi-drive workload justifies it.

Fix the observed bottleneck

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

Check service configuration, I/O and network behavior before selecting a stronger CPU.

Can it run on ZimaOS?

Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.

Verify the supported upstream deployment

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements. Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.

Review upstream deployment guidance ↗

Check workload-specific deployment details

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

Review Bonfire deployment details ↗

Which Zima hardware fits Bonfire?

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements.

Which workload best matches your Bonfire deployment?

Conditional lab or supporting storage use only

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

  • Supporting hardware onlyZimaBoard 2 832

These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.

Zima hardware Best for Example workload Core configuration Recommended boundary Next step
ZimaBoard 2 832 Conditional lab or supporting-service role federation fan-out, active peers, upload volume, timeline queries and queue depth
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
8 GB LPDDR5
Storage
32 GB eMMC; add SATA/PCIe SSD storage for persistent application data
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required for this workload.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements. Get Now
ZimaBoard 2 1664 Conditional lab or supporting-service role Use the supported upstream Bonfire runtime and service topology. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Upstream repository references include PostgreSQL, Redis / Valkey. Confirm which are required in your selected mode rather than enabling all references by default.
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
16 GB LPDDR5
Storage
64 GB eMMC; add SATA/PCIe SSD storage for persistent application data
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required for this workload.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements. Get Now

What the Press Says

Highlights from trusted reviewers worldwide.

La Razón
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”
Read full review
GameRevolution
“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
TechRadar Pro
“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
FOX 8
“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.

ZimaBlade single-board server
★★★★★

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.

ZimaCube Pro personal cloud
★★★★★

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.

ZimaBlade single-board server
★★★★★

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.

ZimaBoard 2 single-board 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

Answers to Bonfire RAM, CPU, storage, Docker, database and ZimaOS sizing questions.

How much RAM should I plan for Bonfire?

No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below. Include ZimaOS, the application and its companion services rather than reserving the entire machine for one container.

What drives the CPU requirement?

No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity. The workload to test is: federation fan-out, active peers, upload volume, timeline queries and queue depth

Which data must survive a container update?

Persist users/posts, media, federation queues, database and search/cache state. Preserve a consistent database/file set and verify that your recovery procedure restores a working application.

What other services belong in the budget?

Use the supported upstream Bonfire runtime and service topology. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Upstream repository references include PostgreSQL, Redis / Valkey. Confirm which are required in your selected mode rather than enabling all references by default.

Does this workload need a dedicated GPU?

A dedicated GPU is not assumed for the core workflow described here. Optional AI, acceleration or media-processing integrations must be evaluated separately against the selected backend.

Can I deploy it on ZimaOS?

Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

What should I check before upgrading hardware?

Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements. Measure the same representative operation before and after a configuration or hardware change.

Which Zima device is a practical starting point?

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Community publishing and interaction with independently configured federation and persistent media. Use the exact supported server/runtime and persistence mode. Size concurrent jobs, retained data and companion services independently of the browser interface. Federation, media storage and enabled extensions add background work beyond local browsing. Use the release-matched data services, queue configuration and public endpoint requirements.

What sources informed this Bonfire hardware guide?

This guide was reviewed against the linked project deployment documentation on November 18, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.

  1. Bonfire official setup / requirements
  2. Bonfire configuration / deployment
  3. Bonfire official repository and releases
  4. ZimaBoard 2 specifications
  5. Bonfire image source: public project material