connections, TLS handshakes, request size, encryption/inspection cost and throughput Time the job and identify CPU, storage or external-service waits before replacing hardware.
Imports, processing and simultaneous users.Requisitos de hardware do Respan Gateway: RAM, CPU, armazenamento e TLS, encaminhamento e carga de rede
Planeie a RAM, a CPU, o armazenamento persistente e as dependências de serviços do Respan Gateway, com dimensionamento do ZimaOS com base nas cargas de trabalho, cópias de segurança e escolhas práticas de hardware.
Respan Gateway hardware requirements at a glance
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
- RAM
- README benchmark: 31 MB process memory in its reference run; 128 MB with 1,000 streams. These are benchmark observations, not a host minimum.
- CPU
- No fixed numerical whole-host requirement verified; measure the selected deployment with OS and companion-service headroom.
- Storage
- Retain gateway configuration and any enabled usage/log state; provider model files are separate.
- Required services
- Use the supported upstream Respan Gateway runtime and service topology. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
- Main sizing variable
- connections, TLS handshakes, request size, encryption/inspection cost and throughput
- Practical Zima starting point
- ZimaBoard 2 832 with SSD-backed active state is an editorial starting point for modest use. Include the OS and all companion services; it is not a measured capacity guarantee.
From official requirements to the right setup
Plan the complete Respan Gateway workload before selecting a server.
-
Official requirements
Choose the exact edition, stable release and supported container/runtime. Use the supported upstream Respan Gateway runtime and service topology. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
-
Confirm your needs
Test a representative busy operation: connections, TLS handshakes, request size, encryption/inspection cost and throughput Record peak resident memory, CPU, disk latency and completion time, including other containers.
-
Leave room to grow
Place active state on reliable persistent storage. Persist proxy configuration, credentials, certificates, access logs and enabled policy state. Budget working space for an upgrade or import and test recovery before relying on the deployment.
-
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. AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
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.
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM guidance | README benchmark: 31 MB process memory in its reference run; 128 MB with 1,000 streams. These are benchmark observations, not a host minimum. | Official guidance keeps its original test, recommendation or example scope. |
| CPU guidance | No fixed numerical whole-host requirement verified; measure the selected deployment with OS and companion-service headroom. | Core counts do not predict a fixed user, device or document capacity. |
| Storage planning | Retain gateway configuration and any enabled usage/log state; provider model files are separate. | Installation space is separate from retained content, working files and backups. |
| Service topology | Use the supported upstream Respan Gateway runtime and service topology. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. | Include every stateful companion service in the host budget. |
| Persistent state | Persist proxy configuration, credentials, certificates, access logs and enabled policy state. | An image rebuild or container replacement is not a backup. |
| Deployment boundary | AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. | Check the linked project instructions for the selected edition and release. |
When to upgrade your hardware
Use observed Respan Gateway 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
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 proxy configuration, credentials, certificates, access logs and enabled policy 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
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
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
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. 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 ↗Use the official Respan Gateway deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Respan Gateway official installation ↗Check workload-specific deployment details
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
Review Respan Gateway deployment details ↗Which Zima hardware fits Respan Gateway?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Respan Gateway deployment?
Start with durable active data and a measured whole-stack memory budget.
- Workload optionZimaBoard 2 832
Choose added memory or compute only when observed peaks justify the change.
- Workload optionZimaBoard 2 1664
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 | Modest Respan Gateway workload | connections, TLS handshakes, request size, encryption/inspection cost and throughput |
|
This is an editorial host choice, not an official app minimum or a guaranteed user/device capacity. | Get Now |
| ZimaBoard 2 1664 | More processing or shared-service headroom | Use the supported upstream Respan Gateway runtime and service topology. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. |
|
Size the combined stack and active working set; more RAM does not fix remote API limits or missing dependencies. | 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
Answers to Respan Gateway RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM should I plan for Respan Gateway?
README benchmark: 31 MB process memory in its reference run; 128 MB with 1,000 streams. These are benchmark observations, not a host minimum. 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 requirement verified; measure the selected deployment with OS and companion-service headroom. The workload to test is: connections, TLS handshakes, request size, encryption/inspection cost and throughput
Which data must survive a container update?
Persist proxy configuration, credentials, certificates, access logs and enabled policy 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 Respan Gateway runtime and service topology. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
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. AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate.
What should I check before upgrading hardware?
AI API routing and streaming to independently provisioned model providers. This is a routing layer rather than the answer-generating model. Include streaming connections, policy work, optional classification and retained usage data; upstream model weights, KV cache and provider rate limits are separate. Measure the same representative operation before and after a configuration or hardware change.
Which Zima device is a practical starting point?
ZimaBoard 2 832 is the editorial starting point for this modest deployment. Choose ZimaBoard 2 1664 for measured memory/processing pressure or broader shared services; retained data determines storage expansion.
What sources informed this Respan Gateway 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.


