Wymagania sprzętowe BrowserStack Automate TurboScale: pamięć RAM, procesor, pamięć masowa i siatka przeglądarek
Zaplanuj infrastrukturę BrowserStack Automate TurboScale pod kątem równoległej obsługi przeglądarek, węzłów chmurowych, automatycznego skalowania, artefaktów i obsługiwanej topologii wdrożenia.
BrowserStack Automate TurboScale hardware requirements at a glance
Size BrowserStack Automate TurboScale from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No universal host minimum; browser-node resources scale with parallel tests
- CPU
- No universal host minimum; scale from parallel browser concurrency
- Storage
- Plan test artifacts, videos/logs, caches and cloud-node disks
- Infrastructure
- Officially deployed on AWS, Azure, or GCP
- Concurrency
- 50 parallel tests are supported by default, with queueing above that
- Best Zima path
- Do not map this to a normal ZimaOS local container
From official requirements to the right setup
Start with current upstream facts for BrowserStack Automate TurboScale, then size the workload rather than copying generic container or catalog labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Parallel tests
- Framework mix
- Browser/OS matrix
- Warm-pool size
- Cloud provider
- Artifact/video retention
- CI integration
- Queue depth
Official minimum requirements
BrowserStack documents a cloud self-hosted grid architecture rather than a single-server numerical CPU/RAM minimum.
Do not fabricate a Zima host minimum. The supported design deploys browser workers into AWS, Azure, or GCP and scales resources based on test concurrency.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No single host minimum published | Browser-node sizing follows parallel sessions and cloud node type. | |
| No single host minimum published | Scales with browser concurrency. | |
| AWS, Azure, or GCP | Automate Self-Hosted is designed for customer cloud infrastructure. | |
| 50 parallel tests with queueing above that | Concurrency is a direct infrastructure sizing variable. | |
| Selenium, Playwright, Cypress | Browser and framework mix affects resource use. | |
| Chrome, Firefox, Edge, WebKit across supported Linux/Windows setups | The grid manages browser nodes rather than a single app container. | |
| Not a universal requirement | Specific browser/test workloads may have separate graphics needs. |
When to upgrade your hardware
Parallelism increase
Warm-pool demand
Artifact growth
Plan hardware growth with confidence
Cloud worker capacity
Add browser nodes in the supported cloud environment.
AWS/Azure/GCP computeWarm pool
Pre-initialize nodes for lower startup latency.
Cloud node poolArtifact storage
Expand/optimize cloud storage for videos and logs.
Cloud object/block storageCI controller separation
Keep CI orchestration separate from browser execution capacity.
Existing CI / Zima host as client onlyCan it run on ZimaOS?
Direct ZimaOS Custom App is not the documented deployment topology
No specific ZimaOS App Store page was verified, and BrowserStack documents AWS/Azure/GCP as the self-hosted grid infrastructure.
Custom install BrowserStack Automate TurboScale in the ZimaOS app ↗Use supported cloud infrastructure
Deploy the browser grid in AWS, Azure, or GCP according to BrowserStack's setup guide.
Open BrowserStack self-hosted setup ↗Use Zima only as an integration/client host if useful
A Zima CI host can trigger tests, but the browser grid itself should follow BrowserStack's documented cloud topology.
Open BrowserStack overview ↗Zima hardware for BrowserStack Automate TurboScale
This workload should not be mapped to ZimaBoard/ZimaCube as if it were a conventional self-hosted app. The browser grid belongs in supported cloud infrastructure.
Choose by workload
Use AWS, Azure, or GCP browser-grid infrastructure sized to concurrency.
Zima products are intentionally omitted from the products list beyond the minimum schema allowance because recommending them as the BrowserStack grid host would contradict upstream deployment guidance.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaCube 2 Pro | CPU-heavy CI, larger SQL/search workloads, and higher concurrency | Build orchestration, larger databases, and consolidated services |
|
16 GB RAM can still constrain very large enterprise or browser-grid workloads | 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
Can BrowserStack Automate Self-Hosted run as a normal ZimaOS app?
That is not the deployment topology documented by BrowserStack.
Where does BrowserStack Automate Self-Hosted run?
BrowserStack documents deployment on AWS, Azure, or GCP.
How many parallel tests are supported by default?
BrowserStack documents 50 parallel tests by default, with extra tests queued.
Does BrowserStack publish one server RAM minimum?
No. The grid scales from browser concurrency and cloud node resources.
Which automation frameworks are supported?
BrowserStack documents Selenium, Playwright, and Cypress.
Can Zima still be part of the workflow?
Yes as a CI/control client or adjacent service, but not as the documented browser-grid infrastructure.
Does the platform universally require a GPU?
No universal GPU requirement is published.
What should trigger scaling?
Queued tests, browser-node saturation, warm-pool needs and artifact storage growth.
