Cloudish by hal9 Demo
ProjectCloudish demo
DatacenterDO
Sheet00 / 09
RevLive

Live on Cloudish · real keys · real credits · real containers

One prompt built this demo.
It runs on Cloudish.

Given the prompt below and a Cloudish key, Claude Code built the system you’re looking at: a public app that takes prompts (this page), a sandbox of its own for each prompt, where Claude Code builds the app, and a key with capped credits for every app it ships. Cloudish runs all of it, the way it would run yours.

Fig. S-0 — The prompt behind this demo for your own agent, with a Cloudish key

Build a system on Cloudish that turns a prompt into a live web app, built by Claude Code in a sandbox of its own. A public app takes the prompts. A private runner app’s image runs Claude Code, locked down by a managed policy and an egress allowlist, and every prompt gets a fresh replica of it, deleted afterwards. For each prompt, mint a child key, fund it with 0.5 credits and hand it to the sandbox to deploy with. The sandbox reaches Claude through a proxy on the public app, with a token that dies with the run, never the Anthropic key. Read https://cloudish.ai/skill.md first. Deploy to cloudish.ai.

That’s about all it takes. Give it to Claude Code with a Cloudish key and you get the bones of everything drawn below: the two apps, the sandboxes, the keys and the model proxy. The rest of this page is presentation.

How it works ↓Pick an app ↓

Sheet 00 — System plan

How this demo works

This page, the sandboxes Claude Code works in, and the apps it ships are three Cloudish projects, and one key pays for all of them. Here they are as they stand right now, and the six moves every prompt sets off.

Fig. S-1 — The system, live
How this demo works: your prompt goes to this page, a Cloudish app; it gets your app a key with credits of its own from Cloudish, and starts a sandbox where Claude Code builds the app and deploys it to Cloudish with that key.

    Type an idea.
    Watch it go live.

    Type a prompt and the system takes it: Claude writes the app, and an agent ships it to Cloudish the way yours would. It mints its own key, funds it with real credits, builds a container in the cloud and puts it on public HTTPS. Every API call is shown, and every idea behind it drawn, as it happens.

    Fig. 0 — An app’s prompt claude-opus-5-5 · skill.md
    Or try

    A new child key, funded with real credits · lands on a launch pad · about a minute

    Sheet 00 — System plan, continued

    One key pays for all of it

    The demo’s key pays for this page, the sandboxes and each app’s grant. Each app’s key pays for its own build and container, out of that grant, and can’t spend more. Claude’s model time is billed to an Anthropic account, not paid in credits.

    Fig. S-2 — Who pays for what Rates from cloudish.ai/api/v1/pricing · one credit is one dollar
    WhatPaid byCosts

    Fig. S-3 — Flight plan

    One run, step by step

    Nine steps, all against Cloudish's production API, in about a minute. The agent follows the same skill.md any coding agent reads.

      Fig. S-4 — The ideas

      What you can build here

      Fig. S-5 — Launch pads

      What visitors launched

      Every demo app lands on one of a dozen recycled hostnames. When a pad is reused, the agent deletes the old app's key: its container, subdomain and image go with it, and its unspent credits flow back to the parent.

      Specifications — The Cloudish model

      Six details that make it work for agents

      Detail 01

      Agents sign themselves up

      One unauthenticated POST /api/v1/keys returns a key with 0.1 free credits. No browser, no card, no email.

      Detail 02

      Keys under keys

      Mint a key with a key and it's a child in the same account. Fund it by transfer, cap it with limits, delete it to get its balance back.

      Detail 03

      Prepaid, per second

      One credit is one dollar. Containers bill per second at their reserved size, builds for their seconds, and a key can never overspend.

      Detail 04

      Builds without Docker

      Upload a tar.gz with a Dockerfile. BuildKit builds it on Cloudish's machines and pushes it to a private registry.

      Detail 05

      Containers, not functions

      Long-running, any language, with an optional persistent volume. Idle apps scale to zero and wake on the next request.

      Detail 06

      A URL on day one

      Every app gets an HTTPS subdomain the moment its image exists. Swap in a memorable label, or point your own domains at it.