Cozy cloud homes for your AI agents

Your agent's brain is
already in the cloud.
Give it a home.

DispatChai is a private, always-warm Linux residence for your coding agents — so your laptop can finally close, and the work keeps brewing.

$ dispatchai up
◔ steeping your residence…
✓ ready — agents home in 42s. close the lid.

FIRST 100 SIP FREE FOR A MONTH · STICKERS INCLUDED, OBVIOUSLY

Dispatch your AI.
Dispatch —

to send something out to do its work elsewhere. That's the whole move: the hands leave your laptop and go somewhere that never sleeps.

Chai —

the small warm thing you keep coming back to. Your residence sits steeping quietly in the EU, always ready when you are.

So: dispatch your agents to a cloud home that stays warm. Not a sandbox that resets, not a laptop that sleeps — a residence you keep.

01 · The itch

We built it for ourselves.
You'll want in.

Modern coding agents are a strange split creature. The brain — the model — lives in a datacenter and always has. Only the hands run at home: a git checkout, a shell, a few tools. And for that, your laptop stays on all night, fans howling, Docker Desktop and PowerShell duct-taped together, hosting… a terminal loop.

The brain

Already cloud.

Every prompt your agent thinks with is answered in someone's datacenter. That part was never local.

The hands

Feather-light.

A checkout, a shell, some tools. About 2 vCPU of honest work. It needs a desk, not a workstation.

The bill

Your laptop.

A €2,000 machine running as a night-shift space heater so a loop can keep looping. It deserves better. So do you.

So we rented the hands a small flat. Laptop closed, agents still working, kitchen table quiet again.

It felt so obviously right that we're making it a product. Not a platform, not a revolution — a residence: the smallest possible cloud home where your agents live, remember, and keep going while you don't.

02 · The residence

A proper Linux home your
agents never want to leave.

  • Your favourite agents, pre-installed.Claude Code, Codex CLI, Gemini CLI — bring your own subscription. You sign in inside your own box; we never see or store your logins. Each residence signs in on its own; whether your plan covers more than one machine is between you and your vendor.
  • Memory that survives everything.Projects, context, caches and half-finished thoughts persist across every disconnect. Reopen tomorrow exactly where you left off.
  • Sessions that outlive your Wi-Fi.tmux keeps every agent running through closed lids, dead batteries and airport lounges.
  • Connect your way.VS Code Remote-SSH for real work, a browser terminal for quick steering, your phone for checking in from the couch.
  • Wakes in seconds, sleeps for free.On-demand residences doze when idle — you stop paying for silence.
# residence.yaml — my whole setup, one file name: my-first-chai agents: [claude-code, codex] recipes: - repo-gardener # tends issues & PRs - inbox-butler # drafts the boring replies memory: 20GB schedule: wake: on-task sleep: 30m-idle region: eu $ dispatchai up ✓ brewed. two agents home.

Under the hood it genuinely is containers and volumes — so everything you already know about images, ports and mounts just works. Docker-like isn't a metaphor here; it's the plumbing.

Recipes — one-click, docker-style

The home is simple. The ecosystem is the magic.

Compose a residence like a compose file. Start from community recipes — a repo gardener, an inbox butler, a standup scribe — or publish your own. The registry is the point.

03 · Your desk

It's just VS Code.
The window you already live in.

No new IDE to learn, no web editor that almost works. Open your residence from the dashboard and your own VS Code opens, connected over Remote-SSH — your files, your extensions, your terminals, all running on the residence instead of your laptop.

  • 1
    Click "Open in VS Code." Your local editor launches straight into the residence. First time takes a few seconds; after that it's instant.
  • 2
    Work exactly as you do now. Same keybindings, same extensions, same integrated terminal — except the machine underneath never sleeps.
  • 3
    Close the lid whenever. tmux keeps every agent running. Your build carries on, your agent keeps going, nothing is lost.
  • 4
    Reopen from anywhere. Same button, another laptop, or the browser terminal from your phone — you land back in the same session, mid-thought.
On the way — VS Code extension

We're building a DispatChai extension so you never leave the editor: see every residence in the sidebar, wake a dozing one, and reattach to a running agent — without opening the dashboard at all. Founding members get it first.

04 · Three sips

Pick. Sip. Close the laptop.

1

Pick a recipe

Or start empty. Your residence brews in a couple of minutes — agents installed, memory mounted, EU region picked.

2

Sign your agents in

Your accounts, your keys, inside your own box. No shared credentials, no inference markup — ever.

3

Walk away

Steer from VS Code, browser or phone. The work keeps brewing while your laptop sleeps and your fans finally rest.

05 · Three pours

Small kettle, fair price.

Why so light? Because most of the brain was never here. The residence hosts the hands — and hands are cheap. That's the whole trick, and we're not pretending otherwise.

Pay as you go
The Cup
€6 / mo + €0.15 / hr
No annual — you are billed for the hours you use
4 vCPU (fair-use) · 8 GB RAM
40 GB persistent home · EU region

A Pot’s machine, paid for by the hour. For evening builders and weekend shippers who use a residence hard for a few hours and then not at all. Use it most days and The Pot is cheaper — that is the intended answer, not a catch.

  • Everything in the residence — agents, memory, tmux, VS Code
  • You pay for hours, not for silence — an idle month costs €6
  • It closes when you close it — nothing shuts your home behind your back. An agent that is thinking looks exactly like one that is idle, and we would rather bill you an hour than kill a job that was working
  • An open home keeps billing, because only you know when you are done. Leave it open all month and it costs about €115 — The Pot is €29, which is the whole reason we point at it
  • Nothing runs while the home is closed — no cron, no watchers, no overnight builds. That work wants The Pot
  • Around five hours a day and The Pot is cheaper. Past that the meter beats the flat price, and we would rather you moved than overpaid
  • Reopening takes about two minutes, not seconds — the machine is genuinely released while you are away, which is the only reason the hours are cheap
  • 40 GB of home that persists — your repos, your history, your agent’s memory. The OS, docker images and build caches live on the machine’s own disk and rebuild themselves on reopen, so you are not paying to store a cache
  • Closing stops whatever is running. Your files, your history and your agent’s memory are all there when you reopen; a build that was mid-flight is not — so close it when you are done, not when you step away
  • Your home stays while you are subscribed — there is no idle clock, and nothing is deleted for not being used. Cancel and it is removed after a grace period, which we will tell you about before it happens
  • Same support as The Pot
Most chosen Always-on
The Pot
€29 / mo
€290 / year — two months on us
4 vCPU (fair-use) · 8 GB RAM
80 GB NVMe · EU region

The honest minimum for real work: VS Code, Docker and a production build in the same box, all day, every day. Your agent lives here now.

  • Never sleeps — cron, watchers and overnight jobs actually finish
  • 8 GB is the number that matters. VS Code's TypeScript server alone will reach for 3 GB before it blinks
  • Docker compose stack + a Next.js build without the OOM roulette
  • Multiple recipes side by side
  • Unmetered waking hours under fair use · priority support
Workshop
The Samovar
€59 / mo
€590 / year — two months on us
8 vCPU (fair-use) · 16 GB RAM
160 GB NVMe · EU region

For running several agents at once on a big monorepo — the parallel-agent lifestyle, without any of them stepping on the others' memory.

  • Everything in The Pot, with room to breathe
  • Parallel agents — several residences' worth of work in one home
  • Heavy monorepos, big test suites, long builds
  • Priority support

All pours · EU regions · one residence per subscription · unlimited traffic for coding (20 TB out a month, per residence) · cancel anytime · export your home as a snapshot, it's yours · fair-use CPU · the price you see is the price you pay

14 days to change your mind. The full amount back — write to us and we will sort it. Once per account per year on the no-questions path; after that we still honour it, just not automatically.

Why these numbers. A residence is a real machine in an EU datacenter, and European hosting got more expensive in June 2026 — so we'd rather price it honestly than run a launch promo we have to claw back later. You are paying for the hands, the snapshots and someone keeping the kettle warm. You are never paying an inference markup: the model is your subscription, billed by your vendor, at their price.

One home per subscription. A subscription is one room key, and one key opens one home. A residence holds its disk and its memory on a real machine whether or not you are using it, so a second home is a second machine — we would rather charge for it plainly than pretend it is free. Want more room? Move to a bigger pour: a Cup and a Pot are the same machine, so the question is only whether you use it enough for the flat price to win. Want a genuinely separate home — client work walled off from your own? Take a second subscription. Its own name, its own snapshots, its own bill, and you can cancel either one on its own. Up to three homes on one account; past that, email us and tell us what you're building.

Your second Pot or Samovar is 15% off. So is your third, monthly or annual. Not The Cup: it is already priced at cost plus the hours, and a Cup neither takes a discounted place nor uses one up — so a Cup on the account never changes what your Pots and Samovars cost, whichever order you pour them in. This is a thank-you, not a bulk rate: a second residence costs us exactly what the first one did, and we would rather say that than dress it up. The loyalty price rides on keeping the extra home, so if you come back down to one Pot or Samovar, that one goes back to its list price. Better said here than discovered at renewal.

06 · Optional extras

Pour in something stronger.

Your residence is complete on its own. But because DispatChai is brewed by Digital One, three of the suite's grown-up capabilities can be poured straight into your home — individually, or all three as a bundle, for a very fair price. Ask when you join the list.

07 · Who it's for

Two kinds of people get it instantly.

The young builder

Ships from anywhere.

Side-projects on a four-year-old laptop and a phone. Wants agents grinding overnight without fan noise, dead batteries or "sorry, my machine was off". The residence is the upgrade the laptop never needed to be.

The senior cloud hand

Wants a clean box.

Lives in Kubernetes and Terraform all day, in a stack that never leaves the EU. Wants a personal, disposable, well-behaved machine that is not the company VPC — for experiments, agents and after-hours ideas. Knows exactly why containers, snapshots and a European jurisdiction are the right answer, and would rather not make an exception for a side project.

We also believe a quiet thing:

your personal agents — with your mail, your repos, your keys — shouldn't live inside the model vendor's house. The brain can be theirs. The home should be yours.

THE QUIET PART — WHAT'S UNDER THE FOAM
DispatChai runs on the same guarded infrastructure its parent, Digital One, operates for European enterprises: EU-owned clouds, signed machine images, egress firewalls, evidence logs. You get all of it without ever thinking about it — it's simply how the house is built.

08 · First pours

Small kettle, honest plan.

Now

Waitlist opens at dispatchai.cloud. We keep building it for ourselves, in public.

Oct 2026

First pours: 100 residences, EU regions, all three pours. Founding members shape the recipes.

Q4 2026

Recipe registry beta — browse, fork and publish community residences.

2027

Mobile console, shared team houses, and whatever the first hundred of you demand loudest.

Get on the list

First 100 sip
free for a month.

Tell us what you'd brew and which agents you run — we'll save you a residence for the first pours in October, and founding members get to shape the recipe registry.

Join the waitlist Ask us anything

STICKERS INCLUDED, OBVIOUSLY