wisp Cloud · early preview

Close the laptop. The agents keep going.

wisp Cloud runs your agents on managed machines, keeps every queue alive overnight, and gives your team one dashboard for what shipped. The wisp you run locally doesn't change and stays free.

No card. We'll write once, when your team's seats are ready.

Just want wisp? MIT, free forever.
18:40

This laptopawake

wisp Cloud3 machines

Flip the switch. Local runs stop with the lid; the cloud runs don't.

Same six harnesses, signed in with your own accounts

01 · Managed machines

Machines, without the SSH.

wisp already runs agents on your own boxes over SSH. Cloud machines show up in the same Run on menu, except we boot them, keep the harness CLIs current and take them down when the queue is empty. Every task still gets its own worktree, diffs, rollback and Ship it.

Ready in seconds

Warm images with Node, git, gh and all six harness CLIs. A machine boots, clones and starts the task before you've switched tabs.

Scale to zero

Machines sleep when the queue is empty and wake on the next task, a schedule or a CI failure. You pay for minutes that ran agents.

Your keys, your repos

Harnesses sign in with your own Claude, OpenAI or Cursor accounts. Repos come in through a GitHub App scoped to the ones you pick.

02 · Persistent queues

A queue that works the night shift.

Your queue lives in the cloud, not in a process on your laptop. Tasks you queue from your phone, recipes on a schedule and CI-failure triggers keep landing and running while you're away. Drag through one night.

18:00Laptop closed. 0 done, 0 running.
18:0021:0000:0003:0006:0009:00
    wisp · 09:00
    The wisp queue: finished tasks with their reports, and one task waiting for an answer

    What's waiting at 09:00: the real wisp queue, synced from the cloud. Finished reports, open PRs, and the one question that needed you.

    03 · Team dashboards

    One view of what every agent shipped.

    See tasks, merged PRs, success rate and spend for the whole team or one person, across every harness. Share recipes and Auto's routing data, so the team's agents learn from each other's merges.

    acme / platformlast 14 days
    Tasks per day, whole team
    Latest

      04 · Free vs Cloud

      The CLI stays free. Cloud is for when you're not there.

      Everything wisp does on your computer today stays MIT-licensed and free, with no account. Cloud only adds what needs a server: machines that keep running, queues that outlive your laptop, and a shared view for teams.

      wisp free forever

      $0 MIT · no account

      Everything on your own computers.

      • All six harnesses, Auto, Compare and subagents
      • Worktrees, presentations, checkpoints and rollback
      • Ship it, PR tracking and Merge
      • Recipes, schedules and CI / issue triggers
      • Your own machines over SSH
      • Phone questions on ntfy or Telegram

      wisp Cloud preview

      $20 per seat / month + machine minutes

      Everything in wisp, plus:

      • Managed machines that boot on demand and scale to zero
      • Persistent queues that run while your laptop sleeps
      • Team dashboard: tasks, merges, success rate and spend
      • Shared recipes, triggers and Auto routing
      • SSO, audit log, per-repo access
      • Same app: Cloud shows up as places in Run on

      Pricing is a draft and may change before launch. Model usage is billed by your own providers, not us.

      FAQ

      Questions

      Will the local CLI ever need an account?

      No. npx wisp-agents keeps working with no sign-in, no telemetry you haven't turned on, and no feature moved behind Cloud. Cloud is opt-in from Settings, like every integration.

      Do you resell model usage?

      No. Harness CLIs on cloud machines sign in with your own Claude, OpenAI, Cursor or xAI accounts. You pay us for seats and machine time only.

      How is this different from Machines?

      Machines connects wisp to computers you already run, over SSH, and stays free. Cloud machines are ones we run for you: booted on demand, kept current, and asleep when nothing is queued.

      Where does my code live?

      On the machine running the task, in its worktree, for as long as the task is open. Machines are single-tenant; disks are wiped when a machine is removed.

      Can I answer questions from my phone?

      Yes, as today: ask_user questions reach ntfy or Telegram, and your answer goes straight back to the agent on its cloud machine.

      Can I mix local and cloud?

      Yes. Run on lists this computer, your SSH machines and cloud machines together. Pick one, or several at once.

      Let it run while you sleep.