husk Join waitlist
Agent-native cloud · early preview

Your agent
needs a body.

Meta gave Muse a machine. OpenAI gave dots a computer. husk gives one to yours — any model, any harness, your keys, your root.

Reserve a machine $husk wake --agent ./yours
machine 0042 — your-agent awake asleep · zzz
Billing running · billed per second $0.00 · sleeping is free
The gap

Every giant gave its agent a computer. None will give yours one.

Works with every agent

Your bots can set up husk too.

Already living with Muse, dots or Grok Bot? Ask them for a husk. Anything that can run a command or call an API can spin one up. Their brains, a body you own — and the keys never leave your hands.

you ▸ "dots, set up a husk for this repo"
dots ▸ husk wake --agent ./repo-agent
husk ▸ machine 0043 ready · keys stay with you
Without husk · their machine, their keysclosed
With husk · any agent, your machine, your keysopen

Product names belong to their owners. husk is independent and not affiliated with them.

Control

You hold the keys.
All of them.

Handing your inbox, repos and API keys to a computer you can’t open is a leap of faith. husk is a machine you can open, inspect and switch off — whenever you want.

Bring your own agent

Claude Code, OpenClaw, Hermes or your own harness. If it runs on Linux, it lives on husk. No model lock-in, ever.

Keys stay sealed

Secrets live in your vault and are injected at runtime. Your agent can use a key — it can never read one back or send it out.

Root is yours

SSH in, read every log, freeze the machine with one switch. Every command and every byte that leaves is on the record.

The Guard

A watchman your agent can’t sweet-talk.

A separate process on every machine checks what your agent tries to do against rules only you can write. Nothing ships, spends or leaves without passing it.

Publish to the webAsk me
Spend over your limitAsk me
Buy a domainAsk me
Call an unknown hostBlock
Read a vault secretNever
Push to a branchAllow
How it works

Think it. It ships.

The machine that builds is the machine that serves. Everything between the idea and the live URL happens in one body that remembers.

  1. 1Think

    One prompt to your agent. That’s the onboarding.

    "ship a waitlist page"
  2. 2Wake

    The machine restores its last snapshot, state intact.

    husk wake
  3. 3Build

    Your agent codes, installs and tests in place. CI runs inside.

    husk run
  4. 4Snapshot

    Every stable state is sealed. Every release is a rollback point.

    husk snapshot
  5. 5Publish

    A live URL or your own domain — once the Guard says yes.

    husk publish
  6. 6Sleep

    No work, no bill. It wakes on the next request or prompt.

    husk sleep
Inside the shell

Everything a body needs.

Persistent sandboxes

Disk, packages and state survive between sessions. Your agent picks up where it left off.

Scale to zero

Idle machines nap into a snapshot and the meter stops.

One-prompt onboarding

Your agent provisions its own machine through MCP or the CLI. No console tour.

One-command deploys

husk publish turns a running port into a live URL.

Snapshots & backups

Automatic, restorable, yours to export. Roll back any release in one command.

Auto CI/CD

Push and the machine builds and tests itself. No external pipeline to wire.

Domains

Buy and wire a domain from the terminal — always behind the Guard.

Usage-based billing

Pay per second awake. Nothing while it sleeps. No plan to forget.

Preview pricing

$0.00

What a sleeping machine costs you. You pay for the seconds your agent actually works — not for a box idling at 3 a.m.

Compute, awake$0.000012 / vCPU·s
Memory, awake$0.000004 / GiB·s
Disk & snapshotsComing soon
Asleep$0 · zzz

Preview rates for early access. Final pricing may change before launch.

Reserve a body for your agent.

Early access opens in waves. Builders who already run their own agents go first.

We’ll only use your email to send you husk access. Ask us anytime and we’ll delete it.