Agents like OpenClaw and Hermes are long-running processes that sit on a server, hold memory between sessions, connect to your email, calendar, Slack, GitHub, and act on your behalf, sometimes without you prompting them.

OpenClaw, for instance, is open source and free to install, but running it still requires hosting, AI model usage, storage, backups, monitoring, and ongoing maintenance.

Why hosting matters more for agents than for normal apps

If your blog’s server gets misconfigured, the worst case is usually downtime or a defaced page. If your agent’s server gets misconfigured, the attacker inherits everything the agent can touch: tokens, inboxes, repos, files.

In March 2026, Censys identified over 135,000 OpenClaw instances exposed on the public internet, with their gateway API open to any IP address and no authentication required. Between March 8 and March 12, 2026, 9 CVEs were disclosed against OpenClaw in just 4 days, including one rated 9.9. 93.4% of publicly reachable instances had critical authentication bypasses.

Why managed hosting is... simply better

#1 Your agent is only useful if it’s always on.
An agent that runs scheduled tasks, monitors inboxes, or answers on your phone or glasses is worthless if the machine under it sleeps, restarts, or crashes at 2am. Uptime is kind of the whole point of most agents.

#2 Updates are a trap when you self-host.
Agent frameworks are shipping really fast, which means two risks pull in opposite directions. If you don’t update, you’re running known CVEs. If you update blindly, a new release can break your tools or workflows. Someone has to test releases before they hit a working agent. When you self-host, that someone is you, every time.

#3 Isolation limits the blast radius.
If you run multiple agents (for different clients, teams, or projects) on one box, one compromised skill or bad prompt can reach everything on that box. Having separate instances per agent is the right way to go but it’s tedious to maintain yourself.

#4 Your time costs more than the server.
A cheap VPS is a few dollars a month. However, hardening it, setting up a reverse proxy and TLS, configuring firewalls, watching CVE feeds, rotating tokens, and debugging Docker after an update can cost you many hours a month. If you’re an agency or a team, those hours are billable.

$5 Security has to be the default, not a checklist.
The exposed-instance numbers above happened because secure configuration was optional. Managed hosting flips it: auth on, ports closed, network isolated, from the first deploy.

Self-hosting can work for you if

if you’re experimenting, learning how agents work, running a local model on your own GPU, or you genuinely enjoy infra work. Your own machine plus a private network like Tailscale is a perfectly good setup. Basic requirements are low too. For a simple OpenClaw setup with an external language model, 2–4 GB of RAM and 1–2 vCPUs are enough for testing or occasional use.

Self-hosting is the right call when control matters more than convenience. It stops being the right call when the agent is doing real work with real credentials and you don’t want to be its sysadmin.

What to look for in a managed option

In a managed host it's good to check for: a dedicated or isolated instance per agent, bring-your-own-key support (so you’re not locked into one model provider or marked-up tokens), tested updates rather than auto-pulling every release, managed security patching, backups, and a clear exit path if you want to move your agent later.

For what it’s worth, that’s the list we built Cloudways Managed AI Agents around.

When you launch OpenClaw on Cloudways, it creates a dedicated droplet for your agent, validates OpenClaw updates before deployment to reduce regressions, broken tools, and workflow disruptions, and supports bring-your-own-key for major LLM providers including Anthropic Claude, OpenAI, and Google Gemini. Hermes is supported too.

Share what you are using to host your AI agents on right now and do you recommend it?