I wonder how long it'll take (if it hasn't already) until the messaging around this inevitably moves on to "Do not self-host this, are you crazy? This requires console commands, don't be silly! Our team of industry-veteran security professionals works on your digital safety 24/7, you would never be able to keep up with the demands of today's cybersecurity attack spectrum. Any sane person would host their claw with us!"

Next flood of (likely heavily YC-backed) Clawbase (Coinbase but for Claws) hosting startups incoming?

I wonder how much the clawbase domain name would sell for, hmm

What exactly are they self hosting here? Probably not the model, right? So just the harness?

That does sound like the worst of both worlds: You get the dependency and data protection issues of a cloud solution, but you also have to maintain a home server to keep the agent running on?

Great idea, happy to ~steal~ be inspired by.

I propose a few other common elements:

1. Another AI agent (actually bunch of folks in a 3rd-world country) to gatekeep/check select input/outputs for data leaks.

2. Using advanced network isolation techniques (read: bunch of iptables rules and security groups) to limit possible data exfiltration.

  This would actually be nice, as the agent for whatsapp would run in a separate entity with limited network access to only whatsapp's IP ranges...

  Possibly like IFTTT/Zapier/etc. like integration, where you drag/drop objectives/tasks in a *declarative* format and the agent(s) figure out the rest...

There are lots of results for "host openclaw", some from VPS SEO spam, some from dedicated CaaS, some from PaaS. Many of them may be profitable.

In a sense, self-hosting it ( and I would argue for a personal rewrite ) is the only way to limit some of the damage.

I already built an operator so we can deploy nanoclaw agents in kubernetes with basically a single yaml file. We're already running two of them in production (PR reviews and ticket triaging)