OpenHands hosting
A software-engineering agent that writes, runs and debugs code.
OpenHands hosting at AIHostBox means a dedicated, single-tenant OpenHands instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $18.99 per month and the admin account, the data and any API keys are yours.
OpenHands, formerly OpenDevin, is an MIT-licensed coding agent developed in the open by the All Hands AI team and a large contributor base. Unlike an editor plug-in that suggests lines, it works a task end to end: it reads the repository, edits files, runs commands and tests in a terminal, browses documentation when it needs to, and reports back with a diff. You watch in a web UI on port 3000, or drive it from its CLI and headless mode.
Each conversation runs in its own Docker sandbox started from an agent-server image, so the agent can install packages and execute code without touching the host. That is exactly why it wants a server: a laptop running several sandboxes plus a browser gets hot and noisy, and a task that takes forty minutes should not stop when the lid closes. On a hosted instance you start the job, leave, and review the result later.
OpenHands hosting plans
Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.
How we run OpenHands
The OpenHands app container on port 3000 with access to the instance’s Docker engine, which it uses to start a separate agent-server sandbox container for each conversation, plus a persistent state directory.
What we configure for you
- Agent-server image repository and tag pinned to match the app release
- LLM_MODEL, LLM_API_KEY and, if needed, LLM_BASE_URL for your provider or gateway
- State directory on persistent storage for settings, history and secrets
- Access limited to your login in front of the web UI, since the agent can run arbitrary code
- GitHub or GitLab token scoped to the repositories you choose
Which plan fits
Pro (8 GB, 4 vCPU) runs the app plus one or two active sandboxes on a typical web or Python repository. Max (12 GB, 6 vCPU) is for larger repositories with heavy builds or test suites, or several conversations running at the same time.
The honest limits
The quality of the work is set by the model you pay for, and CPU-hosted local models are too slow and unreliable at tool use for real tasks. Frontier-model token costs on long tasks are yours and can add up.
What people run OpenHands for
Background refactors
Hand over a mechanical change and review the diff afterwards.
Issue triage
Let it reproduce a bug report before a human picks it up.
Test coverage catch-up
Ask it to write tests for an untested module and run them until they pass.
Dependency upgrades
Bump a library, fix what breaks and hand back a branch for review.
Licence and version policy
| Item | Position |
|---|---|
| Upstream licence | MIT |
| Sold as managed hosting | Yes |
| Tenancy | Single tenant — one customer per instance |
| Patching | Critical advisories within 24 hours, high severity within 72 |
Our full position on licences, including the applications we decline to sell, is on the licensing page.
Reading on OpenHands
Works well with OpenHands
More Agents & RAG we host
OpenHands hosting: your questions
Does it run code on my instance?
Which models work best?
Can I use a local model on CPU?
How does it reach my repositories?
What is kept between sessions?
Run OpenHands without running a server
A dedicated OpenHands instance, deployed and maintained by us. Month to month, cancel whenever.