Root vs SSH-only for agent workloads
| Workload | Root needed? | Why |
|---|---|---|
| Dockerised agent + Redis + Postgres | Yes | Install Engine, manage volumes, tune sysctl |
| Local LLM (Ollama / vLLM) | Yes | Drivers, large models, GPU paths |
| MCP server exposing tools | Usually yes | Custom binaries, ports, secrets on disk |
| Agent as SaaS webhook only | Often no | No system packages on your host |
| Managed WordPress + chatbot plugin | No root on host | Wrong product class for self-hosted agents |
Providers with root in our published JSON
Sample of high-scoring unmanaged options. Root flags and scores are copied from the live comparison file.
When root is optional
If the “agent” is only API traffic from a laptop or a serverless function, the VPS question may not apply. If you still want a small always-on worker without caring for the OS, a platform-as-a-service can work — but that is outside this site’s root/control-plane thesis. For self-hosted agents, start from Best VPS for AI agents and confirm root_access: true in the JSON before you buy.
Frequently Asked Questions
See Also
Best VPS for AI agents · How much RAM for AI agents · Cloudways vs Kinsta (control plane) · Docker & homelab