Requisitos de hardware de AgentFlux: RAM, CPU, almacenamiento, workers y trabajos simultáneos

Planifica la RAM, la CPU, el almacenamiento persistente y las dependencias de los servicios de AgentFlux, con dimensionamiento de ZimaOS según la carga de trabajo, copias de seguridad y opciones de hardware prácticas.

Requisitos de hardware de AgentFlux: RAM, CPU, almacenamiento, workers y trabajos simultáneos

AgentFlux hardware requirements at a glance

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

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 workflow definitions, credentials, job metadata, logs and retained input/output artifacts.
Required services
Use the documented AgentFlux runtime and selected service topology. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Upstream references include SQLite. Verify which apply to your selected mode; a mention is not a mandatory dependency.
Main sizing variable
parallel jobs, task duration, browser sessions and separately executed scripts
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. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

From official requirements to the right setup

Plan the complete AgentFlux workload before selecting a server.

  1. Official requirements

    Choose the exact edition, stable release and supported container/runtime. Use the documented AgentFlux runtime and selected service topology. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Upstream references include SQLite. Verify which apply to your selected mode; a mention is not a mandatory dependency.

  2. Confirm your needs

    Test a representative busy operation: parallel jobs, task duration, browser sessions and separately executed scripts 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 workflow definitions, credentials, job metadata, logs and retained input/output artifacts. 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. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

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 20, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.

Review AgentFlux official requirements

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. 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 workflow definitions, credentials, job metadata, logs and retained input/output artifacts.Installation space is separate from retained content, working files and backups.
Service topologyUse the documented AgentFlux runtime and selected service topology. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Upstream references include SQLite. Verify which apply to your selected mode; a mention is not a mandatory dependency.Include every stateful companion service in the host budget.
Persistent statePersist workflow definitions, credentials, job metadata, logs and retained input/output artifacts.An image rebuild or container replacement is not a backup.
Deployment boundaryVisual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Check the linked project instructions for the selected edition and release.

When to upgrade your hardware

Use observed AgentFlux 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

parallel jobs, task duration, browser sessions and separately executed scripts 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 workflow definitions, credentials, job metadata, logs and retained input/output artifacts. 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

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

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

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. 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

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

Review AgentFlux deployment details ↗

Which Zima hardware fits AgentFlux?

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 AgentFlux 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. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

  • 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 parallel jobs, task duration, browser sessions and separately executed scripts
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
Backend-specific acceleration is optional or required according to the selected workflow; verify support and device access separately.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Get Now
ZimaBoard 2 1664 Conditional lab or supporting-service role Use the documented AgentFlux runtime and selected service topology. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Upstream references include SQLite. Verify which apply to your selected mode; a mention is not a mandatory dependency.
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
Backend-specific acceleration is optional or required according to the selected workflow; verify support and device access separately.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. 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 AgentFlux RAM, CPU, storage, Docker, database and ZimaOS sizing questions.

How much RAM should I plan for AgentFlux?

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: parallel jobs, task duration, browser sessions and separately executed scripts

Which data must survive a container update?

Persist workflow definitions, credentials, job metadata, logs and retained input/output artifacts. 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 documented AgentFlux runtime and selected service topology. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. Upstream references include SQLite. Verify which apply to your selected mode; a mention is not a mandatory dependency.

Does this workload need a dedicated GPU?

Accelerator needs depend on the selected inference, synthesis, browser or media backend. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

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. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

What should I check before upgrading hardware?

Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack. 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. Visual agent workflows and independently executed tools. The controller, retained run state and jobs it starts need separate budgets. Include browser sessions, containers or VMs only when enabled; local inference and external-provider limits are independent. Verify the supported host privileges and topology rather than treating an idle panel as the complete stack.

What sources informed this AgentFlux hardware guide?

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

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