Tiller is winding down. If we host your server, back up your data before it is shut down. 44 days left Learn more
Tiller
/
Sign in Get Started

Tiller is winding down

We're sunsetting Tiller over the next 60 days. What you need to do depends on which kind of server you have — and for most plans, you must back up and move your data before the shutdown, or it will be lost. Please read this carefully.

Why

Tiller has been a great tool for tinkerers, but providing support at an affordable price has become unsustainable, and running it as a community product makes the tight platform integration we want hard to deliver. Rather than let it quietly degrade, we're winding it down honestly and giving everyone time to move.

The important part: where your server runs

There are two situations, and they're very different. You can see which plan a server is on from its page in the dashboard.

Managed plans — Flex and All-in-One (most users)

These servers run on Tiller's own infrastructure. When the dashboard shuts down on Day 60, these servers are permanently deleted, and any remaining data is purged from our systems by Day 90.

If you're on Flex or All-in-One, you must back up your data and move your agent to a home you control before Day 60. Nothing on these servers survives the shutdown. See the migration steps below.

BYOK — your own Hetzner account

If you connected your own Hetzner account (BYOK), your server lives on your account and keeps running after Tiller shuts down. You only lose the Tiller dashboard in front of it. Your *.tiller.sh subdomain still stops working on Day 60, so point your own domain at the server before then.

Migrating off a managed (Flex / All-in-One) server

Do all of this through the Tiller dashboard while it's still online. Managed servers are reached through the dashboard's built-in terminal — there is no direct SSH access to them from your own machine, and once the dashboard goes offline on Day 60 there is no way back in. Don't wait until the final days.

  1. Open your server's terminal. From your server's page in the dashboard, open the built-in terminal. This is how you reach a managed server.
  2. Send your data somewhere you control. From that terminal, push your OpenClaw data — your workspace, configuration, conversations, and any files your agent uses — to a destination you own. Outbound connections work, so you can push to a Git repository, upload to your own cloud/object storage, or copy to another server you control. (You can't pull files into the server from outside, so do this from the terminal itself.) If you're unsure what to copy, message us via Feedback & Help — you'll only find it inside the Tiller dashboard once you're logged in — and we'll point you to the right paths.
  3. Stand up a new home. OpenClaw is open source and runs on any server you control — it's published as the openclaw npm package. Create your own server (your own Hetzner account is an easy option) and install it yourself by following the official project: github.com/openclaw/openclaw.
  4. Restore and verify. Bring your data onto the new server and confirm your agent runs as expected.
  5. Repoint your domain. If you reached your agent at a *.tiller.sh address, point your own domain at the new server and update your reverse proxy. The *.tiller.sh subdomain stops resolving on Day 60.
  6. Delete the server. Once you've migrated, delete the server from the dashboard. Billing is per day, so deleting it stops the charges immediately (see Billing below).

If you'd rather not run things yourself, get in touch — we'll do what we can to help you land somewhere before the deadline.

Timeline

The wind-down runs over 60 days from 5 June 2026:

  • 5 June 2026 (Day 0) — New orders are disabled. Existing servers keep running.
  • 5 July 2026 (Day 30) — Halfway reminder. Deadline for community maintainer handoff offers (see below).
  • 20 July 2026 (Day 45) — New server provisioning is frozen entirely.
  • 28 July 2026 (Day 53) — One-week warning. Make sure managed servers are backed up by now.
  • 3 August 2026 (Day 59) — Final 24-hour notice.
  • 4 August 2026 (Day 60) — Hard shutdown. The dashboard goes offline, managed Flex and All-in-One servers are deleted, and *.tiller.sh subdomains stop resolving.
  • 3 September 2026 (Day 90) — Any remaining data is purged from our systems.

Billing

Tiller bills per day for each running server, based on usage — there's no upfront subscription. That means there's nothing to refund: once you've migrated, delete your server from the dashboard and the daily charges stop. You only pay for the days your server was actually running.

Handing Tiller to the community

If someone serious wants to keep Tiller alive, we're open to handing over the codebase and the tiller.sh domain to a community maintainer. Reach out before 5 July 2026 (Day 30) if that's you.

Need a hand?

If anything here is unclear, or you need help migrating — getting your data out, or getting your agent running independently — please don't hesitate to reach out through Feedback & Help. It's only accessible from inside the Tiller dashboard once you're logged in, so get in touch while the dashboard is still online. We're happy to help, and we'd much rather everyone land softly than lose data on Day 60.