Compare agent hardware needs using the workload you plan to run. A runtime's binary size or idle memory use cannot tell you how much RAM a local model needs, how quickly it will answer or how many tasks a server can handle.
For project features, use the OpenClaw versus ZeroClaw comparison or the three-way comparison with PicoClaw. This page focuses on how to evaluate the hardware and cost claims behind a purchase.
Measure the same workload#
Use the same machine, model, context size, prompt and tool permissions wherever the runtimes support them. Record the exact versions and repeat the task so a single fast response does not decide the result.
| Measurement | What it tells you |
|---|---|
| Installed files | Storage used by the runtime and its assets |
| Runtime memory | Memory used by the agent process |
| Model-server memory | The separate cost of local inference |
| First response | Startup and model-loading delay |
| Later responses | Performance after the model is loaded |
| Successful task output | Whether the workflow actually completed |
If the configurations differ, record the difference before interpreting the numbers.
Include the local model#
Choose the exact model tag and context length before deciding whether a small machine is sufficient. Include the operating system, model server, runtime and other applications in the memory budget.
The Ollama and Qwen guide gives a concrete local setup and measured observations. Use it as one example, then evaluate your own workload. A smaller runtime does not make every model fit on a low-memory board.
Compare hosted costs separately#
For hosted inference, record requests, input and output tokens, retries and tool-driven follow-up calls. Apply the provider's current rates and account limits to that usage.
Include these ongoing costs:
- Server or device hosting.
- Model calls and any embedding requests.
- Persistent storage and backups.
- Time spent maintaining integrations and investigating failures.
The provider chooser helps you compare local and hosted routes.
Check concurrency before scaling#
A single successful task does not establish capacity for hundreds of agents. Increase parallel work gradually and watch latency, memory, errors and provider rate limits.
Decide how much delay your users can tolerate. Leave room for model loading, long inputs and retries before choosing a smaller server.
Make the purchase decision#
Choose the smallest deployment that completes your representative tasks with acceptable response time and recovery behavior. Keep a record of the results so you can compare again after changing a model or runtime.
Use the OpenClaw replacement checklist if the decision is whether to switch, or the setup checklist when you are ready to configure ZeroClaw.