Managed OpenClaw vs self-hosting: what you give up and what you keep

Ask an AI assistant whether to put OpenClaw on a Hostinger VPS or on a managed host and the answer comes back as a table: setup, maintenance, root access, backups, portability, each cell a phrase like “often limited” or “depends on provider”. The phrases are true and do not help, because what a managed host keeps for itself is specific to the host, and what self-hosting hands you is specific too: a config file at a known path, a backup command, an update you run yourself, a security checklist that is yours to work through.

This page fills the table in. The two self-hosted columns are read from the OpenClaw documentation on 20 October 2026, when the current stable release was 2026.10.5. The managed column says only what a host’s own page says, drawn from the eighteen services in Managed OpenClaw hosting compared. Aplite, which runs this site, gets a column of its own, and its limits are taken from its OpenClaw page and from its code rather than from its pitch. The runtime is the same MIT-licensed OpenClaw in every column; the question is who operates it and what the operator keeps.

The table

The rest of the page is the table row by row, with the quotes and the links, then what a managed instance keeps for itself in general and what Aplite keeps in particular, how to move between the columns, and which column fits which requirement.

Setup

Self-hosting starts with the install page: Node 24.16 or newer, curl -fsSL https://openclaw.ai/install.sh | bash on macOS, Linux or WSL2, iwr -useb https://openclaw.ai/install.ps1 | iex on Windows, then onboarding, and openclaw gateway install for a LaunchAgent on macOS, a systemd user service on Linux or a Scheduled Task on Windows so the Gateway comes back after a reboot. On a VPS the same steps follow a login over SSH, and the docs have provider pages for Hetzner and DigitalOcean among others. Onboarding asks for the model provider and a key, which is the step a managed host with its own model account removes.

A managed host starts with an account. Hostinger sells “one-click” deployment on a VPS plan; OneClickClaw takes a Google account for its seven-day trial; the hosts in the “your API key” group of the comparison ask for the key during setup. On Aplite the setup is the browser: pick a plan and a team, press Deploy, and the instance is online in about a minute with the model account already attached and the device pairing already done.

Updates

OpenClaw ships often. The releases feed showed three stable versions in five days this month: 2026.9.33 on 15 October, 2026.10.4 on 16 October and 2026.10.5 on 19 October, with 2026.10.10 in beta the same day. Self-hosted, each one is your decision. The updating page describes openclaw update: it “detects your install type (npm, pnpm, Bun, or git)”, checks the new version “while the old Gateway serves, then activates and verifies the update”, and can be triggered as /update from a connected chat. The same page says “Before a significant update, create a verified backup” and that “Automatic config copies and migration recovery originals are not a full-state backup”; installs older than July 2026 must step through 2026.9.5 first.

Managed, the schedule is the host’s. OneClickClaw: “We auto-update OpenClaw to the stable version we trust in production”, “You get the OpenClaw versions we have tested ourselves”, and “You can pin any version from your dashboard”. xCloud: “Updates that apply themselves”. Hostinger’s application page lists “One-click updates” without saying who clicks. Everpod: “We keep your agent’s software current and roll changes out carefully”. On Aplite the fleet moves when we have tested a release, and the gap is a number you can check: on 20 October 2026 every Aplite workspace runs 2026.9.8, while the upstream stable is 2026.10.5. New features arrive weeks, not hours, after they ship.

Root and shell

On a VPS you are root; on your own machine the Gateway runs as your user with your user’s reach. Among managed hosts the row runs the whole range. OneClickClaw: “You get full SSH with admin rights on a machine nobody else shares”, opt-in from the dashboard, free on every tier. Agent37 puts “a task board, web terminal, file browser, live desktop, and scheduled jobs, all in your browser” and says “Your files and keys live inside your container”. xCloud describes its service as “no Docker, no terminal, no SSH”. Hostinger’s OpenClaw pages mention Docker container management and container logs and do not mention a shell; Everpod’s page does not either.

Aplite gives you no shell. The agent has one: exec is in its tool list, and it runs commands inside its own container, the same place its files live. Every file change it makes, and every action that leaves the workspace, arrives as a proposal in Approvals before it happens. So there is a terminal in the picture, but it is the agent’s, not yours, and you see its results rather than typing into it.

openclaw.json

Self-hosted, the whole runtime is one file. The configuration reference is a “field-level reference for ~/.openclaw/openclaw.json”, in JSON5 “(comments + trailing commas allowed)”, with sections for channels, agents, tools, models, MCP, skills, plugins, gateway, hooks, automations (cron), update and the rest. Anything the runtime can do has a key here.

Managed hosts’ pages do not talk about the file. Where a host gives you a shell, the file is on a machine you can log into; where it does not, the page is silent on whether you can read it. On Aplite the file exists, one per workspace, and you do not see it: agents, their models, skills and channels are configured in the browser, and the platform regenerates openclaw.json from those settings on every change. The consequence to be clear about is the inverse: a setting the interface does not expose cannot be changed. The heartbeat interval, the tool allowlist, the sandbox policy and the provider routing are set by us for every workspace.

Skills and plugins

Self-hosted, the skills CLI installs from ClawHub (openclaw skills install @owner/<slug>), from git or from a local folder, and the plugins CLI takes clawhub:, npm: and git: sources, so anything published anywhere is a command away. Managed pages mostly say nothing about either. OneClickClaw’s “Anything OpenClaw can do, your server can do” is the broadest statement, and with SSH it holds. Everpod mentions skills only in its export FAQ, “the skills it made”.

On Aplite skills come from a curated catalog, 25 of them switched on today, enabled per agent in the browser; agents also write their own skills into their own folder, and those survive a resync. Servers you run yourself connect as MCP servers from the Skills page on every plan. A set of command-line tools (ffmpeg, pandoc, jq, ripgrep, the GitHub CLI, DuckDB and others) is switched on per workspace from the Server page. What you cannot do is install an npm package or an arbitrary plugin on the box; a skill that needs one is not available until we add it.

Models and keys

The model providers page lists the bundled providers (OpenAI, Anthropic, Google Gemini and Vertex, OpenRouter, xAI, Z.AI, MiniMax, NVIDIA, Kilo Gateway, Vercel AI Gateway, Moonshot and more), the ChatGPT and Codex OAuth login, custom providers under models.providers, and local runtimes: Ollama, LM Studio, llama.cpp, vLLM, SGLang. Self-hosted, the key is yours and the bill is the provider’s; on your own machine a local model makes the model line $0, with the caveats the upstream FAQ attaches to small models.

Managed hosts fall into the three groups the comparison already sorted. The host runs the model account: Aplite, Runware, Hostinger, Everpod, RapidClaw, ClawHosters, OpenClaw Launch, Ampere. A subscription sign-in: OneClickClaw (ChatGPT or Grok) and Hostinger (ChatGPT Plus or Pro). Your own key: xCloud, Flux, Railway, MyClaw, OpenClaw Cloud, BetterClaw Basic. Local models on a managed host appear on two pages: OneClickClaw installs Ollama on its Hobbyist and Pro servers, ClawHosters connects Ollama on your own hardware over a VPN. Whether a key can be avoided at all is the subject of Can you use OpenClaw without an API key?.

Aplite’s column is the narrowest here, on purpose: 24 models in the catalog, routed through one metered OpenRouter account, billed in credits at 1 credit = 1¢; Free gets the budget end of the catalog, paid plans all of it. Bringing your own key is not supported, a local model is not an option, and a model that is not in the catalog is not reachable. The price of a model in credits sits above OpenRouter’s list price; how that works out per message and per month is in What OpenClaw really costs per month.

Backups

Self-hosted, the backups page gives you openclaw backup create: a verified .tar.gz of “state, config, credentials, every configured agent directory” and, by default, the workspaces, with the SQLite databases captured through the online backup API. It is manual unless you run openclaw backup enable for a daily Gateway-owned job; the docs call a daily archive “a reasonable daily routine for small installs”, say to run one before updates, resets and machine moves, and warn that archives “contain credentials and session history” and belong encrypted and off the machine. Restore is openclaw backup restore <archive> --target <new-dir> and “never activates in place”. On a VPS the provider’s snapshots sit underneath; on your own machine, your own habits do.

Managed, the row is what the page says. Daily: xCloud (“daily encrypted backups”), Everpod (“daily automatic backups” and “restores we actually test”), OpenClaw Launch, MyClaw, RapidClaw. OneClickClaw: “Daily and weekly snapshots, completely free”, a snapshot before every update, “restored in minutes”. Hostinger: backups are in “we handle the setup, updates, backups, and security”, frequency not stated on the OpenClaw page. ClawHosters: an add-on on the pricing page. Railway: yours. Runware: not stated.

Aplite backs up every workspace nightly: the database, the runtime state and the workspace files, in one encrypted bundle, kept for 7 days plus the newest of each of the last 4 weeks and 3 months. There is no backup button and no self-serve restore; a restore goes through us, not through a dashboard. That is the row where “managed” is most literal.

Export and portability

Self-hosted, portability is the same archive: the migrating guide is “stop the Gateway, back up the whole ~/.openclaw/ directory, not just openclaw.json”, move the archive “via scp, an external drive, or another protected channel”, restore to a staging directory on the new machine, run openclaw doctor and restart. Plugin node_modules are reinstalled, WhatsApp may need relinking, approvals and delivery state roll back to the archive’s moment.

Managed hosts answer in their own words. Everpod: “ask it to pack itself into one .zip file”, and on leaving “we’ll send you a full copy of your pod’s data”. Agent37: “your workspace is plain files you can download through the file browser or terminal anytime”. OneClickClaw: “No proprietary layer, no export fee, no conversation with support. Copy it off and go”. Hostinger, on switching applications: “your configurations, conversation history, and custom setups don’t transfer automatically”, and “We recommend exporting or noting down any important settings before switching”. xCloud: “No lock-in, cancel anytime”, and nothing about how the data leaves.

On Aplite the files you wrote and the files the agents wrote are plain markdown: notes, AGENT.md instructions, tasks and schedules as .md with frontmatter, and any of them downloads as a file from its own menu. What does not download is the runtime state: session transcripts, the memory database, pairing records. There is no openclaw backup create for you to run and no one-click archive. Moving to your own server is a fresh install from the docs above with your files carried over, which is described in Moving between the columns. Cancelling keeps the workspace intact until the end of the billing period.

Security: gateway and approvals

Self-hosted, security is a checklist you own. The security page notes that “on a regular host install the Gateway binds to loopback”, covers exposing it (firewall, Tailscale, a reverse proxy), pairing codes for unknown DM senders, and openclaw security audit for drift. Two defaults matter for the comparison. The trust model states that host exec “is allowed without approval prompts” by default (security="full", ask="off"), “intentional UX, not a vulnerability by itself”, and that exec approvals “are guardrails for operator intent, not hostile multi-tenant isolation”; for strong boundaries it says “Use sandboxing and host isolation”. And sandboxing “is off by default”, runs tool execution in Docker when on, and “is not a perfect security boundary, but it materially limits filesystem and process access when the model does something dumb”. On your own machine, add that the agent runs as you, on the disk with your documents on it.

Managed hosts describe the machine, rarely the policy. OneClickClaw: “a machine nobody else shares”. Hostinger and xCloud list “security” among what they handle. The pages do not say whether exec approvals are on, whether the agent is sandboxed or what the Gateway is bound to.

Aplite’s answer is in its code, so it can be exact. Each workspace is one container on its own Docker network; the gateway port is published on 127.0.0.1 of our host only, so nothing on the internet reaches a gateway directly; device pairing is done by the platform with one signed identity, and you never see the Control UI. The agent’s exec runs inside the container, which is the sandbox. On top of the runtime sits the approval gate: file writes, edits, shell commands that change files and anything that sends something out are held as proposals until you accept, edit or reject them. The trade is the one in the openclaw.json row: these policies are set for you, and you cannot loosen them.

Always on

A VPS is on for the rent. Your own machine is on while it is awake and online; the upstream FAQ lists “sleep/network drops disconnect it, OS updates/reboots interrupt it, must stay awake” as the laptop’s disadvantages. Managed paid plans are on; the free tiers are not, by design: Agent37’s free agent sleeps after 15 minutes idle, Aplite’s Free workspace sleeps after 6 hours idle and wakes on the next visit, usually under a minute, which means a Telegram bot on Free answers only while the workspace is awake. Pro and Power stay on. Which free plans sleep and which take a card is in OpenClaw hosting with a free plan and no credit card.

Price

The numbers are in What OpenClaw really costs per month; the shape is enough here. A VPS is $5 to $12 a month (Contabo, DigitalOcean, Hostinger as printed on 20 October 2026) plus the model tokens, about $1.50 a month on a cheap model and $31 on a frontier one at thirty messages a day, plus whatever the heartbeat adds. Your own machine is electricity, under $1 to $9 a month for a Mac mini, plus the same model line, or $0 with Ollama; the other $0 paths, Oracle’s free tier among them, are in OpenClaw hosting for free. Managed entry plans run $0 to $29 across the eighteen hosts, with model usage included at some. Aplite is $0 on Free with 300 welcome credits that do not expire, $20 on Pro with 2,000 credits a month, $50 on Power with 6,000, at 1 credit = 1¢ of model use priced above OpenRouter’s list.

Your time

The row no page prints. Self-hosted, it is the install, each update decision (three stable releases in five days this month), the backup routine, the security checklist and the evening the Gateway stops answering. Managed, it is agents and channels, and on Aplite also the approvals queue, which is work you take on in exchange for an agent that cannot change a file without you.

What a managed host keeps for itself

Across the pages, the managed trade has a shape. The host decides the version. The host decides whether you get a shell, and most pages do not say. The host decides what model accounts are possible, and the “your API key” column of the comparison is where that lands. Backups exist but their frequency, encryption and restore path are stated by about half the hosts. The exit is described by four (Everpod, Agent37, OneClickClaw, Hostinger) and silent at the rest. None of the pages read for this article says whether exec approvals are on or the agent is sandboxed. That silence is a finding: for every row where a managed page says nothing, the self-hosted column has a documented answer and a command.

What Aplite keeps for itself, exactly

• No shell for you. The agent runs commands in its container; you see proposals and results.
• No raw openclaw.json. Agents, models, skills and channels are set in the browser; settings the interface does not show, among them the heartbeat interval, the tool allowlist and the sandbox policy, are fixed by us.
• Models from the catalog only. 24 models through one metered account; no own key, no local models.
• Skills from the catalog, plus your own. 25 curated skills, skills your agents write, MCP servers you host; no npm packages or arbitrary plugins.
• Our release schedule. 2026.9.8 on 20 October 2026 against upstream’s 2026.10.5.
• No backup or restore button. Nightly encrypted backups exist; using one goes through us.
• No archive export. Notes and agent files download as .md; the runtime state does not.
• Free sleeps. After 6 hours idle, until the next visit.

What stays: a standard OpenClaw runtime per workspace, so what the OpenClaw docs say about agents, sessions, skills and tools applies; files in plain markdown; Telegram in two minutes with a BotFather token; and the approvals layer, which is the one thing in this list that self-hosting does not give you by default. Aplite is run by PIKsolution OÜ, an Estonian company, on a server in Nuremberg, and is not affiliated with the OpenClaw project.

Moving between the columns

From your server to a managed host. The workspace files travel: AGENTS.md, SOUL.md, USER.md, MEMORY.md and your notes are plain text and paste into any host that shows you the files. The config does not, because the host writes its own; sessions and pairing do not either. Channels are re-created on the host’s side (a Telegram bot token from @BotFather works anywhere).

From a managed host to your server. It depends on what the host lets you take. With SSH (OneClickClaw, Agent37’s terminal) the self-hosted procedure applies on their machine: openclaw backup create, copy the archive, openclaw backup restore on yours. Everpod sends a zip. From Aplite you take the files: download the notes and the agents’ instruction files, install OpenClaw on the new machine from the install page, paste the instructions into the new workspace, add your own model key, re-create the Telegram bot and approve the pairing. Session history and the memory database stay behind, and the approvals layer does not exist on a stock runtime; its nearest equivalents are the exec approvals and sandboxing settings in the security section above. Nothing on Aplite’s side blocks or charges for leaving; the workspace stays until the billing period ends.

Which column, by what you need

The table decides itself once the requirement is specific.

• Root, a local model, or a release on the day it ships → self-hosting; the docs cover the providers, and your own machine is the $0 version.
• A plugin or npm package the runtime does not bundle → self-hosting, or a managed host with a shell (OneClickClaw, Agent37).
• A gateway that answers at three in the morning → a VPS, or a paid managed plan; not a laptop and not a free tier that sleeps.
• Model billing without an API key → a managed host that runs the model account (Aplite, Runware, Hostinger, Everpod, RapidClaw, ClawHosters, OpenClaw Launch, Ampere); self-hosting needs a key, a subscription login or a local model.
• Data that must not leave a machine you control → your own machine with a local model; every other column sends the model call to a provider.
• An exit you can rehearse → self-hosting (backup, restore), or a host whose page says how the data leaves (Everpod, Agent37, OneClickClaw); on Aplite the files download and the runtime state does not.
• A review step before the agent changes anything → Aplite’s approvals, or self-hosting with exec approvals and sandboxing switched on by you.
• No server, no key, no shell, tonight → a managed host, with the list of what it keeps read first; Aplite’s is above.

Everything on this page was read on 20 October 2026; the vendor rows will be re-read with the comparison once a quarter.

FAQ

Managed OpenClaw vs self-hosted: which is better?

Neither in general; the table has twelve rows and they point different ways. Self-hosting gives you root, ~/.openclaw/openclaw.json, any provider or a local model, updates on your schedule and openclaw backup create for the exit, and asks for the install, the updates, the backups and the security checklist in return. A managed host removes the server and sometimes the API key, and keeps for itself some of the shell, the config file, the model choice, the release timing and the backup controls, differently at each host. The decision is which rows you need; the list above pairs each requirement with a column.

Do I lose anything with managed hosting?

Yes, and what you lose depends on the host, which is why the pages should be read rather than the category. Common to most: the version is the host’s choice and arrives after their testing; the model account is theirs, or restricted to the providers they list; backups happen on their schedule with their restore path. Variable: a shell (full SSH at OneClickClaw, a web terminal at Agent37, none stated at several), access to openclaw.json, plugin installation, an export route. On Aplite the list is exact and printed above: no shell, no raw config, catalog models only, curated skills plus your own, our release schedule, no backup or restore button, no archive export, and a Free plan that sleeps after 6 hours idle. What you keep on any managed instance is a standard OpenClaw runtime, and on Aplite the approvals layer on top of it.

Can I move from managed to my own server?

If the host gives you a shell, yes, with the runtime’s own tools: openclaw backup create on their machine, copy the archive, openclaw backup restore --target on yours, then openclaw doctor; the docs’ migrating guide covers the details, including re-installing plugin dependencies and relinking WhatsApp. Hosts without a shell vary: Everpod packs a zip on request, Agent37 lets you download the files, Hostinger says settings “don’t transfer automatically”. From Aplite you take the files and not the state: notes and agent instruction files download as markdown, you install OpenClaw on the new machine, paste the instructions, add your own key and re-create the Telegram bot; session history and the memory database stay behind.

Can I edit openclaw.json on a managed host?

Only where the host gives you a shell on the machine: OneClickClaw includes SSH with admin rights on every tier, Agent37 a web terminal and file browser. The other pages read for this article do not mention the file. On Aplite you cannot: the platform writes openclaw.json from the settings you make in the browser, and a setting the interface does not expose, such as the heartbeat interval or the tool allowlist, is fixed.

What does self-hosting OpenClaw involve day to day?

The install once (Node 24.16 or newer, the one-line installer, openclaw gateway install for a service), then: running openclaw update when a release you want appears, with a verified backup first as the docs advise; a backup routine, by hand or with openclaw backup enable, stored encrypted off the machine; the security checklist on the gateway page and openclaw security audit for drift; and keeping the machine awake and online, which on a laptop the upstream FAQ lists as the main disadvantage. The commands are short; the recurring part is deciding, and noticing when the Gateway has stopped.