OpenClaw
An autonomous AI agent you run yourself: web dashboard, scheduled tasks, plugins, persistent workspace.
One-click deploy, from $13/mo on a Miget plan.
OpenClaw is an autonomous agent designed to live on a server, not in a chat tab: it has a dashboard, scheduled tasks, a plugin system, and a persistent workspace where its files and context accumulate. Think of it as hiring an agent and giving it a desk.
This template runs the coollabsio all-in-one image (nginx + gateway, env-driven) with a 5 GB /data volume. Three secrets configure it: your Anthropic API key, a dashboard password, and a gateway token; after first deploy you pin OPENCLAW_ALLOWED_ORIGINS to your https domain.
Treat it as a privileged deployment - an autonomous agent with an API budget and a persistent disk. Give it its own API key with a spending limit, and read its task history the way you would review a new hire’s work.
Upstream project: OpenClaw
#what you get
- Web dashboard for conversations, tasks, and agent configuration
- Scheduled/recurring tasks - the agent works while you sleep
- Plugin system for tools and integrations
- Persistent /data workspace survives redeploys
- All-in-one image: nginx + gateway, configured by env
- Basic auth + gateway token + origin allowlist
#topology
| Service | Role | Public |
|---|---|---|
| openclaw | agent + dashboard (:5000) | yes (basic auth) |
#miget sizing
// this stack needs
2 GiB RAM · 5 GB disk · 1 service
2 GiB runs the agent and dashboard comfortably; the model does the heavy thinking remotely. The 5 GB volume holds the agent’s accumulated workspace and state.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. other PaaS
Estimated monthly cost of running this exact stack (2 GiB RAM, 5 GB disk, 1 container) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$100 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$29 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$26 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$21 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$13 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
openclaw -
Set the required variables:
ANTHROPIC_API_KEY, the agent’s model access, billed to you; set a spend limitAUTH_PASSWORD, dashboard basic authOPENCLAW_GATEWAY_TOKEN, gateway token (openssl rand -hex 24)
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/openclaw
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
What can OpenClaw actually do autonomously?
Whatever its tasks and plugins allow: recurring research, monitoring and summarizing, file processing in its workspace, calling external APIs. You define tasks in the dashboard; it executes on schedule and keeps history you can audit.
Why does the template call this a privileged deployment?
Because it is an autonomous agent with your API key and a persistent disk. Scope the key, set a billing limit, use a strong dashboard password, and lock OPENCLAW_ALLOWED_ORIGINS to your domain - the standard posture for anything that acts on its own.
What does running OpenClaw cost?
Infrastructure is $13/month (2 GiB hobby plan). Model usage on your Anthropic key dominates real cost and scales with how busy you keep the agent - a spending limit on the key keeps surprises out.
Does the agent’s memory survive redeploys?
Yes - state and workspace live on the /data volume. Redeploying the image (updates, config changes) leaves the agent’s accumulated context intact.
Ship OpenClaw today
One compose stack, 2 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.