AI agent hosting
Every hosting guide on this site so far asks you to already know your runtime. This one does not. If you have an agent, or are about to, and just want to know where it should live so it keeps working, start here: four options, what each genuinely costs including your time, and how to tell which one you are.
Direct answer
Where should I host an AI agent that runs 24/7?
There are four options. A local machine is free and stops when the machine does. A VPS costs roughly $12 to $18 a month and hands you a server to run. Serverless suits short scheduled jobs and struggles with long-running or stateful agents. A managed agent host costs more per month and removes the operations work entirely. Choose by how much operational work you want, not by price alone.
The four options compared
| Option | Monthly cost | You operate | Best for |
|---|---|---|---|
| Local machine | Free | Everything, plus uptime | Development and testing |
| Your own VPS | $12 to $18 | The server and everything on it | Full control, unusual needs |
| Serverless | Usage-based, low | Function code and its limits | Short scheduled jobs |
| Managed agent host | From $39 | The agent, not the machine | Output over infrastructure |
Option 1: a local machine
A laptop, a desktop, or a Mac Mini in a cupboard. Free compute you already own, and the honest starting point for almost everyone. It stops being viable at the exact moment the agent starts mattering.
- Good for: development, experimentation, and agents that only need to run while you are working anyway.
- Breaks on: sleep, reboots, power cuts, travel, and network changes.
- A Mac Mini that stays on solves the lid problem and none of the others: you still patch it, restart the agent, rotate its keys, and have no alerting.
Option 2: your own VPS
The most common next step, and a genuinely reasonable one if you like servers. Roughly $12 to $18 a month buys a machine that stays on. What it does not buy is anything above the operating system.
- Good for: full control, unusual dependencies, strict data residency, and people who already run servers.
- You operate: hardening, the runtime install, updates, restart policies, log rotation, backups, and alerting.
- Honest cost: the invoice is $12 to $18. Setup runs to a few hours and upkeep to a few hours a month, which dominates the total for most people.
Option 3: serverless
Functions that run on a schedule and bill per execution. Excellent for a narrow shape of agent and awkward for the rest, and the mismatch is structural rather than a matter of configuration.
- Good for: short, stateless, scheduled jobs with predictable runtimes.
- Fights you on: long-running work against execution timeouts, persistent state between runs, warm interactive sessions, and anything wanting a filesystem.
- Cost is genuinely low when the fit is right, and the fit is right less often than it first appears.
Option 4: a managed agent host
A platform whose job is running agents rather than running machines. Higher monthly price, and the comparison is only meaningful if you count what it replaces.
- You operate: the agent's instructions, tools, and schedule.
- The platform operates: provisioning, isolation, restarts, health monitoring, secret storage, run records, and spend limits.
- Good for: anyone whose interest is the agent's output rather than its infrastructure.
How to choose, in one question
Ask what you want to be doing on a Sunday when an agent stops. If the honest answer is diagnosing it, self-host and enjoy it. If the honest answer is not finding out until Monday, you need something that restarts the agent and tells you it did.
Then, and only then, pick a runtime
Hosting and runtime are separate decisions taken in that order. Once you know where the agent should live, choose what it runs on: OpenClaw for the OpenClaw operating model and existing setups, Hermes for config-driven agents with schedules, gateways, and approvals, Codex for code-first agents on the OpenAI Codex CLI. Qoren runs all three in the same managed environments.
Related guides
Deployment trade-offs
Self-hosted vs managed agents: what changes when the agent must stay online
Compare local, VPS, and managed deployment for OpenClaw, Hermes, and Codex agents. What changes for uptime, security, cost, and operations when you self-host.
Read guideThe homework, itemised
Stop babysitting your AI agents
Running an AI agent is easy. Keeping it running is the homework: restarts, key rotation, silent failures, runaway spend. The whole list, and who does it.
Read guideRuntime decision guide
OpenClaw vs Hermes: which agent runtime should you deploy?
A neutral guide to choosing between OpenClaw and Hermes: how the two agent runtimes differ, and which one to deploy for managed, always-on agents.
Read guideFrequently asked questions
What is the cheapest way to run an AI agent 24/7?
On the invoice, a small VPS at roughly $12 to $18 a month, or a machine you already own for nothing. Counting your time, the answer changes: self-hosting adds setup hours and recurring upkeep, and once you value those the gap against a managed plan narrows or closes. Compare total cost, not just hosting.
Can I run an AI agent without a server?
Yes. Serverless works for short scheduled jobs, and a managed agent host removes the server entirely: you configure the agent and the platform provisions, isolates, and operates the environment underneath it. Neither requires you to touch an operating system.
Is a Mac Mini a good AI agent host?
It is a real improvement over a laptop, because it stays on and stays put. It is not a solved hosting problem: you still patch it, restart agents after reboots, store credentials somewhere, and have no alerting when something stops. It fixes uptime and leaves the operations work with you.
Do I choose the host or the runtime first?
The host, in most cases. Where the agent lives determines whether it can run on a schedule at all, which is the thing that makes an agent useful. The runtime decides how the agent is configured and what it can do, and on a platform that supports several the template usually decides it for you.
When is self-hosting genuinely the right answer?
When you need local-only or offline execution, when data residency rules require a specific machine, when your dependencies are unusual enough that a managed runtime cannot accommodate them, or when operating the infrastructure is itself something you want to do. Those are good reasons and this page is not trying to talk you out of them.
Run OpenClaw, Hermes or Codex agents 24/7, without the homework.
Qoren runs the machine, the secrets, the updates and the logs, with a hard cap on credit spend. Start from a template and have an agent working today.