Hostinger's One-Click OpenClaw Template: Which of the Two You Actually Want

Search for the Hostinger OpenClaw template and you’ll find a dozen guides walking the same five clicks. Almost none of them mention the thing that matters most: Hostinger sells two different OpenClaw products, and which one you buy decides whether server administration is your job or theirs.

OpenClaw’s own installation documentation splits them cleanly:

• Option A — 1-Click OpenClaw (Managed). “Hostinger handles infrastructure, Docker, and automatic updates. Fastest path to a running instance.”
• Option B — OpenClaw on VPS. “More control over the server. Hostinger deploys OpenClaw via Docker on your VPS; you manage it through the Docker Manager in hPanel.”

Same agent, same one-click deploy, completely different division of labour.

Which one you want

Take Managed if you want an agent, not a server. Hostinger’s own page describes it as “Managed OpenClaw handles all security, updates, and backups” and lists “Security managed for you” among the plan’s inclusions. At the time of writing it’s advertised at $5.99/mo on a summer sale, renewing at $11.99/mo for two years.

Take OpenClaw on VPS if you want root. You get a normal Hostinger VPS with OpenClaw deployed onto it via Docker, administered through Docker Manager in hPanel. You can SSH in, install other things, run other containers — and you own the server’s security posture, because it’s your server.

The rest of this guide covers Option B, since that’s what “VPS template” means. If you picked Managed, the install is genuinely three clicks and you can skip to the sizing section.

Installing it

From OpenClaw’s documentation, the flow is:

1. Buy the plan. Choose an OpenClaw on VPS plan at checkout. During checkout you can add Ready-to-Use AI credits — pre-purchased model access wired in automatically — or decline them and bring your own key from Anthropic, OpenAI, Google Gemini or xAI during setup. Which of those is cheaper is a separate question we worked through in what Hostinger’s bundled AI credits actually cost; the short version is that the credit price isn’t published, so you can’t compute the markup from the documentation.

2. Fill in the configuration fields once the VPS is provisioned:

• Gateway token — auto-generated. Save it. This is the credential for your agent’s dashboard, and it’s issued once during setup.
• WhatsApp number — with country code, optional.
• Telegram bot token — from BotFather, optional.
• API keys — only if you declined the bundled credits.

3. Click Deploy. Provisioning takes a few minutes; wait for the running state in Docker Manager rather than assuming a stall.

4. Open the dashboard from hPanel once it’s running.

5. Verify by sending “Hi” to your agent on whichever channel you connected. OpenClaw replies and walks you through initial preferences. If nothing comes back, that’s a channel problem rather than an install problem — our Telegram setup guide and WhatsApp guide cover the failure modes for each.

Running it afterwards

Logs, restarts and updates all live in Docker Manager in hPanel. Updating is a button: press Update to pull the latest image.

That update button is worth a moment’s thought. On the Managed product, updates are Hostinger’s responsibility and happen automatically. On the VPS product they’re a button you remember to press. OpenClaw is software with a documented history of serious vulnerabilities — an agent with access to your files, shell and messaging accounts is exactly the thing you want patched — so if you take the VPS route, put a recurring reminder somewhere. “I’ll notice when there’s an update” is not a patching strategy.

The three problems people hit

Straight from OpenClaw’s troubleshooting for this install path:

Dashboard not loading. Usually the container hasn’t finished provisioning. Wait a few minutes, then read the Docker Manager logs.

Container keeps restarting. Open the Docker Manager logs and look for configuration errors — a missing token or an invalid API key is the common cause, and it shows up as a restart loop rather than an error message in the UI.

Telegram bot not responding. If DM pairing is required, an unknown sender receives a short pairing code instead of a reply. Approve it from the OpenClaw dashboard chat, or with openclaw pairing approve telegram <CODE> if you have shell access to the container. This one looks like a broken bot and is actually the access control working.

What you’re still responsible for

Here’s where I want to be careful, because this is the vendor we most often recommend and it would be easy to be either too generous or too harsh.

On the Managed product, Hostinger states plainly that security, updates and backups are handled. Take that at face value for what it covers.

On the VPS product, OpenClaw’s documentation is equally plain that you have “more control over the server” and manage it yourself. Control and responsibility are the same thing here. So there’s a hardening pass that a one-click deploy of any application, from any host, does not do for you.

I have not bought this plan and audited what the template configures, so I’m not going to tell you which specific hardening steps it does or doesn’t perform — several guides confidently assert things about this template that I can’t verify, and a wrong claim about a security default is worse than no claim. What I can give you is the checklist to run yourself, and one verified fact that catches people on exactly this kind of deployment.

The verified fact: this deploys via Docker, and Docker publishes ports past ufw. Docker’s own documentation says container traffic is routed in the nat table, “before the firewall rules can be applied, effectively ignoring your firewall configuration.” So if you add containers to this box later and assume a firewall rule protects them, it doesn’t. Publish to 127.0.0.1 explicitly, or filter with the DOCKER-USER chain.

The checklist, which takes about five minutes:

1. See what’s actually listening — ss -tulpn on the box, and check anything bound to 0.0.0.0.
2. Check it from outside — the only test that proves reachability. Our exposure audit walks it properly.
3. Confirm the dashboard needs the Gateway token before it will do anything.
4. Add Hostinger’s network firewall in hPanel, which sits outside the machine and so can’t be routed around by Docker’s iptables rules.
5. Lock the messaging channel to your own account — an agent reachable by a stranger on Telegram is an exposure regardless of how tight the server is.

Which tier to buy

This is the decision the sales page won’t make for you, and it turns on one feature:

A single headless Chromium instance wants 1–2GB to itself. That’s why the entry tier is comfortable right up until you enable browser automation, and then it isn’t — and the failure mode is nasty, because the kernel kills the agent with no application-level error. If your agent starts vanishing mid-task with an empty log, that’s an OOM kill, not a bug.

Buy 8GB if browser automation is anywhere in your plans. The gap between tiers is a few dollars a month and it’s the difference between an agent that works and one that dies silently under load.

Check Hostinger’s OpenClaw plans → · Read our Hostinger review

For how this compares to running it yourself elsewhere, best VPS for OpenClaw prices the alternatives, and self-hosting OpenClaw on a VPS covers the manual path with hardening done first.

How we checked this

The install flow, configuration fields, Docker Manager behaviour and troubleshooting steps are from OpenClaw’s own Hostinger installation documentation, read in August 2026 — including the two-option split between Managed and VPS, which most third-party guides for this keyword collapse into one. Plan pricing and the “Managed for you” inclusions are from Hostinger’s OpenClaw page and appear in the screenshot above. The Docker ufw behaviour is quoted from Docker’s own documentation.

What we did not do: we did not purchase this plan and audit the deployed server. That’s the honest limit on the hardening section — we can tell you what to check and why, and we can tell you what Docker demonstrably does, but we can’t tell you what this specific template configures on first boot without running it. Several published guides do make those claims; we’d treat them sceptically unless they show evidence.

Nor have we measured memory use across agent workloads ourselves. The RAM figures above are published floors, and the browser-automation number is the one most worth respecting.

The Hostinger link above is an affiliate link, and Hostinger is the highest-commission vendor in this category for us — which is exactly why the hardening section refuses to make claims we haven’t verified in either direction.

FAQ

What’s the difference between Managed OpenClaw and OpenClaw on VPS?

Managed means Hostinger handles infrastructure, Docker, updates and security. OpenClaw on VPS gives you root on a normal VPS with OpenClaw deployed via Docker, administered through Docker Manager — you get control and the administration that comes with it.

How long does the Hostinger OpenClaw template take to install?

A few minutes of provisioning after you complete the configuration fields. The realistic path from checkout to a working agent is well under an hour, most of which is deciding on channels and models rather than waiting.

Do I need my own API key?

No. You can add Ready-to-Use AI credits at checkout, which are pre-purchased and wired in automatically. You can also bring your own key from Anthropic, OpenAI, Google Gemini or xAI. Whether the bundled credits are good value is unresolvable from the documentation, because Hostinger doesn’t publish what a credit costs.

What is the Gateway token?

The auto-generated credential for your OpenClaw dashboard, issued during setup. Save it when it’s shown — it’s what stands between your agent and anyone who reaches its dashboard.

Which VPS plan should I pick for OpenClaw?

4GB is fine for a text-only agent calling a hosted model. Go to 8GB if you want browser automation, because a single headless Chromium instance wants 1–2GB by itself. Undersizing shows up as the agent being killed mid-task with no error in its own logs.

My container keeps restarting. What’s wrong?

Almost always a configuration error — a missing token or an invalid API key. Open the Docker Manager logs in hPanel and read them; the failure appears there rather than in the dashboard.

Does the one-click template secure the server for me?

On the Managed product Hostinger says security is handled. On the VPS product you’re the administrator, so run the five-minute checklist above — particularly checking what’s reachable from outside, since Docker-published ports are not filtered by ufw.