(no title)
PranayKumarJain | 19 days ago
If you’re mostly using OpenClaw as a “gateway + chat UI” that calls hosted model APIs, and you’re not running a headful browser / local models / heavy indexing, you can often get by with much less than 4GB.
Where it gets chunky is when each tenant has its own Chromium instance, lots of background workers, or you’re doing anything that keeps long-lived context/caches around. In a multi-tenant setup I’d start conservative, but it’s worth measuring with cgroup limits and seeing what your actual p95 looks like.
vishnukool|18 days ago
It's the damn chromium instances that chugs memory like an Irish man chugs beer. I experimented launching containers with it and quickly realized the tiny shared infra hosts are not a good fit. We're launching a higher prized plan that has more memory for such things.