Cliff Cloud

Hand Cliff a task. Close the laptop.

Cliff runs your task on its own throwaway cloud machine with your model key, then hands back the changed files and, if you ask, a live link. One free task per wallet per day.

Checking…

Start a task

Your model key is sent per task, passed to the sandbox only as an environment variable, and never stored or logged. This page doesn't save it either. A key with a spending limit is wise: the agent there uses it as it would on your computer.

Or upload files (optional)
Up to 200 files and 2 MB in all.

Cliff runs there with --yes: it edits files and runs commands without asking, inside that machine only. There is no wallet in the cloud: wallet commands are refused.

Sign in with a wallet first.

1. Sign in with a wallet

A free API key from a signed message: no transaction, no gas, no $CLIFF needed. It starts tasks and counts your free one a day.

Your tasks

  • Sign in to see the tasks this wallet started. They are kept 7 days.

What happens on the machine

  1. A fresh Vercel Sandbox starts for your task alone: 2 vCPUs, 4 GB of memory, in iad1.
  2. It installs the same cliff.mjs this site serves, with install.sh, which refuses the file unless its SHA-256 matches version.json.
  3. It clones your public repo or copies your uploaded files, and notes what is there.
  4. It runs cliff -p "<your task>" --yes --json with your model and key, and the log streams to this page.
  5. When Cliff finishes, or the time limit is near, or you press Stop, it packs the files Cliff changed as a .tar.gz, publishes your folder if you asked, and the machine is stopped and deleted.

Files that contain your key are left out of the download and the live link. The task's record, log and changed files are kept 7 days so you can come back for them, then deleted.

What it costs

You pay usYour first task each UTC day: free. After that: 1 credit a minute of the time limit, charged up front; whole minutes it didn't use come back when it ends. Credits are bought by burning $CLIFF, once it launches.
You pay your model providerThe tokens, at their price, on your key. Cliff prints them in the log.
The machine costs the operatorAt Vercel's list prices (checked 2026-11-16): about $0.0018 a minute when the machine mostly waits on the model (10% CPU), at most $0.0057 a minute with both vCPUs busy. A 20-minute task is at most $0.11. Each finished task shows what its own run cost.
CapsThe operator caps tasks at 2 running at once, 20 minutes each and $5 of machine time a day for everyone ($1 per wallet). When a cap is reached, Cloud says it is paused and nothing is charged.

From the terminal or another agent

cliff key new                       # a free API key signed by Cliff's own wallet (or: cliff key set ck_…)
cliff cloud run "add a dark mode toggle" --repo https://github.com/you/site --publish
cliff cloud status <task>            # also: logs, download, stop, list

The same over HTTP: POST /api/cloud/run with Authorization: Bearer ck_…, and over MCP: cloud_run_task and cloud_task_status. Every route is in the docs.

Not built yet

Always-on services (a small bot or API that keeps running) and apps with a server and a database are on the waitlist. Tasks are the only thing Cloud runs today.