OpenClaw server · preinstalled · KVM VPS

Your own AI assistant, always on.

An AI assistant you message on WhatsApp, Telegram or Slack, running on a server that's yours. OpenClaw, the free open-source assistant, comes already installed: add your AI account key, connect your chat apps, and it's ready. You look after the server yourself, or add paid Server Management at checkout and we'll do it.

See plans & pricing

Runs on our Standard KVM VPS · openclaw.ai ↗

Plans & pricing

Longer terms cost less per month. The price shown is per month at the term you pick, with the amount billed underneath.

Every plan includes 1 TB bandwidth · OpenClaw preinstalled, comes up ready · Daily VM disk backup

O1 Starter

Already meets OpenClaw’s own minimum

₹1,643/mosave 17%

billed ₹19,717 per year

  • 2 vCPU
  • 4 GB RAM
  • 50 GB NVMe SSD
  • 1 TB bandwidth
  • Note: 1 IPv4 + 1 IPv6
  • OpenClaw preinstalled, comes up ready
  • Note: Bring your own LLM key
  • Note: Full root · KVM · self-managed
  • Daily VM disk backup
Choose O1 Starter

O3 Multi

Double the memory of O2 Everyday

₹3,874/mosave 17%

billed ₹46,489 per year

  • 6 vCPU
  • 16 GB RAM
  • 120 GB NVMe SSD
  • 1 TB bandwidth
  • Note: 1 IPv4 + 1 IPv6
  • OpenClaw preinstalled, comes up ready
  • Note: Bring your own LLM key
  • Note: Full root · KVM · self-managed
  • Daily VM disk backup
Choose O3 Multi
  • Seamless migration from your current host
  • No lock-in, cancel anytime
  • SLA-backed 99.9% uptime
  • Plan prices exclude 18% GST, added at checkout for billing addresses in India

Each plan renews for the same term at the price in force then, shown before you pay. Promo codes apply to the first term only.

Bring your own LLM key

OpenClaw connects to whichever AI provider you choose: Anthropic, OpenAI, Google, OpenRouter, or a model you host yourself. You add your key after setup, so you pay that provider directly, at their rates, with nothing added by us. Model usage is billed by them rather than in your hosting price, and you can switch provider whenever you like. We help you wire it up and keep the key safe on the box.

What OpenClaw is

OpenClaw is a personal AI assistant you run yourself; in the project’s own words, it answers you on the channels you already use. You message it on WhatsApp or Telegram the way you would message a person. It remembers, it can do work on a schedule, it can talk out loud, and it thinks with whichever AI model you hand it a key for. It is MIT-licensed and free. It is also very new: the first code landed in November 2025, and in the months since it has gathered more than 380,000 stars on GitHub, among the most-starred projects there, ever. It moves at that speed too, which is the part worth planning for.

The software is the open-source project from openclaw.ai. We run the server it sits on; we are not affiliated with the project.

How a self-hosted OpenClaw fits together Your chat apps reach a Gateway running as a daemon on your own machine. It has to stay running, because scheduled jobs run inside that process. Its memory is plain Markdown files in your workspace and its schedule persists on disk. The only hop off your server is to the AI model you choose, using your own key. Where it answers you WhatsApp · Telegram · Slack · Signal · +19 more Your VPS · your Gateway The Gateway, running as a daemon Scheduled jobs run inside it; stop it and they stop Memory · Markdown Schedule · on disk Files you can open yourself, no hidden state The AI model you pick Anthropic · OpenAI · Google · xAI · OpenRouter
The dashed box is the one thing outside your server: the AI model you pick, reached with your own key.
  • 380,000+ GitHub stars
  • 360+ Contributors
  • MIT Open source, free
  • It answers where you already are

    WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Teams and about sixteen more: all through one gateway. No new app to check.

  • Memory you can actually read

    It keeps what it learns as plain Markdown in a workspace on your disk. In the project’s words, the model only remembers what gets saved to disk; there is no hidden state to take on trust.

  • Work that happens on a schedule

    Built-in cron, with jobs persisted to disk so they survive a restart. They run inside the gateway process, which is precisely why that process has to stay up.

  • Voice, and a canvas

    Wake it by voice and talk to it on macOS, iOS and Android; watch it work on a live canvas; reach it from companion apps on Windows and Mac.

  • Any model you like

    Anthropic, OpenAI, Google, xAI or OpenRouter: you bring the key and pick the model. You pay the model provider directly at their price, with nothing added by us.

Why it wants a server

Setting OpenClaw up installs its gateway as a background service, because the thing has to keep running to be any use: scheduled jobs execute inside that process, and an assistant that is asleep cannot answer you. A laptop closes. A small always-on machine does not, and it keeps the memory, the workspace and the keys on hardware you control rather than a platform you rent.

Why run OpenClaw with us

One tenant

Your own copy, not a shared one

OpenClaw is designed for one owner per copy: its own guide says it isn't built to be shared safely between strangers. So you get your own copy on your own server, the way the project intends, not a slice of someone else's.

Private

Private to you

The assistant runs on a server that's yours, in the region you choose. Your chats, its memory and your connected accounts stay on your server, not mixed into someone else's cloud.

One-click

Ready when you order

The server arrives with OpenClaw installed and set to start by itself, so it keeps running after a restart from day one. Nothing technical to set up before you say hello.

Yours

You're in charge, with help on tap

OpenClaw updates often. On a self-managed server you decide when to update, with a best-effort full backup of the server every day as a safety net. If you'd rather not look after a server at all, add paid Server Management at checkout.

Example session
systemctl is-active openclawactive su - openclaw -c 'openclaw --version'OpenClaw 2026.7.1-2 (0790d9f) ss -tlnp | grep 18789LISTEN 0 511 0.0.0.0:18789 users:(("openclaw-gatewa",pid=8507))
An illustration of the shape of a session, not a recording from a live box. The image ships with OpenClaw already installed, so the first thing you run is a check rather than an install.
Your chat app
  1. Every weekday at 9, send me yesterday’s order count.
  2. Saved. I’ll message you here each weekday at 09:00.
  3. What did I tell you about invoices?
  4. From your memory file: they go to accounts@, never to you.
An illustration. It answers in whichever app you connect, in your own words and on your own schedule.

How it works

  1. 01

    Pick a plan

    Three tiers on KVM hardware: start where your workload fits and move up later.

  2. 02

    The image does the setup

    Pick where the server lives (India, Germany or the US) and your VPS deploys with OpenClaw installed and its gateway registered as a service. Optional extras (offsite backups, paid Server Management) are there to take or leave.

  3. 03

    Add your LLM key and channels

    Connect your own model provider (Anthropic, OpenAI, Google, OpenRouter…) and the chat channels you use. Inference is billed by your provider, and never appears on your hosting bill.

  4. 04

    Yours to run

    It is a self-managed VPS with full root: you decide when to update OpenClaw and what runs beside it. Hardware, network and the virtualisation layer are on us. If you would rather not look after a Linux box, Server Management tiers are at checkout.

your-server:18789
The OpenClaw gateway dashboard in a browser, with fields for the WebSocket URL, gateway token and an optional password.

Claiming it, once

  1. 01

    Open the dashboard

    Browse to https://your-server-ip:18789 and accept the self-signed certificate. The gateway generates its own on first boot, so your browser will not know it yet. Use the IPv4 address your server was delivered with: that is where the dashboard answers, and every plan on this page includes one.

  2. 02

    Fetch your gateway token

    Over SSH, read it from the gateway config. It is generated on your machine and never leaves it.

    ssh root@your-server-ip
    grep token /home/openclaw/.openclaw/openclaw.json
  3. 03

    Connect

    Paste the token into the Gateway Token field and press Connect.

  4. 04

    Approve the device

    Pairing is approved from the server, so a browser alone cannot claim your gateway.

    su - openclaw -c "openclaw devices list"
    su - openclaw -c "openclaw devices approve <requestId>"

The token is generated on your own machine and read over SSH. We never see it, and pairing is approved from the server, so a browser alone cannot claim your gateway.

Run it yourself, or rent it

On a VPS of your own

  • Your own model key, billed to you by the provider you picked.
  • Memory is Markdown and the schedule is a file, both on your disk.
  • Root on the box, so you install whatever tools you want beside it.
  • One flat monthly price for the server, whoever ends up using it.
  • A daily full-disk backup of the VM is included.

On a subscription

  • Usually billed per person, per month.
  • History and settings live on the vendor’s servers.
  • The model is generally whichever one the vendor ships.
  • Usually no shell, so the toolset is what the vendor built.

Questions

How is this different from a plain KVM VPS?

It is the same self-managed KVM line, with full root. The difference is the setup: OpenClaw arrives installed with its gateway registered as a service, on hardware sized for it, so you skip the install and go straight to adding your key and your channels.

Which plan should I start on?

O1 Starter already meets OpenClaw’s own minimum of 2 vCPU and 4 GB of RAM, so even the smallest plan gives the gateway the room the project asks for. Start there, and move up to O2 Everyday or O3 Multi when you give the assistant more to do.

Do I need to run commands to install it?

Not to install it. Ordering provisions a VPS with OpenClaw pre-installed and its gateway registered as a service, so it comes back up on its own after a reboot. Claiming it is a one-time step over SSH: read your gateway token and approve your device. Connecting your channels and your model key follows OpenClaw’s own onboarding, and an engineer can point you right if you get stuck.

What does “self-managed” mean here?

The base plans are a real KVM VPS with full root that you run: OS updates, OpenClaw updates and housekeeping are in your hands. Hardware, network and the virtualisation layer are ours. If you want our engineers on the box (updates, monitoring, hardening), add a paid Server Management tier at checkout.

Are backups included?

Yes, at VM level: we take a daily full-disk backup of your instance on a best-effort basis, and it is what we use to bring the whole server back if something goes badly wrong. Restoring an individual file or database is yours to do on a self-managed box, so keep your own copies of anything you cannot lose. The “Offsite Backups for Data” option at checkout adds offsite copies. And since OpenClaw keeps its memory as plain files, your own exports are easy.

How private is this, really?

Your instance is single-tenant: your own box, your own gateway, in the datacenter region you choose at checkout (India, Germany or the US), and OpenClaw keeps its memory as plain files you can read yourself, so nothing about it is opaque to you. Your keys are yours, and we do not read your conversations. It is worth knowing exactly where that line sits: we operate the host, so the disk is technically reachable by us, and OpenClaw’s own documentation says resisting a compromised host is not one of its design goals. So what you get is a machine nobody else shares, plus a policy we hold ourselves to. If your threat model needs more than that, talk to us before you order and we will tell you whether this fits.

Is it safe to let an AI agent read my messages?

Treat it the way the project itself does: OpenClaw’s docs say to treat inbound messages as untrusted input, and by default the agent can act on the machine it runs on. That is what makes it useful and it is also the risk. Give it its own box (you are), be deliberate about which channels and which skills you connect, and ask us if you are unsure about one. We would rather have that conversation than have you find out later.

Is the price final?

It is the full hosting price for the term you choose. Promotional discounts apply to your first term. If your billing address is in India, 18% GST is added at checkout.

OpenClaw or Hermes?

Both are open-source AI assistants that live on a server of your own and answer through your chat apps, on the same self-managed KVM line. OpenClaw is built around one gateway for around two dozen chat channels, with voice, a live canvas and companion apps. Hermes, from Nous Research, turns what it works through into skills it writes and refines itself, and connects to more than forty model providers. If you are unsure which suits what you have in mind, ask an engineer.

OpenClaw is an independent open-source project. IndicHosts is not affiliated with, endorsed by, or sponsored by the OpenClaw project or the OpenClaw Foundation. We sell infrastructure for running it; the software is theirs, and we use the name only to say what runs on the server.

Ready for an assistant of your own?

Order and the gateway comes up ready for your key and your channels. Unsure which tier, or whether OpenClaw fits what you have in mind? Ask an engineer; you'll get a straight answer.