MeerkatQuick start
Repo to production, in five steps.
Two of these happen in a browser because they are sign-ins. The rest can be typed, scripted, or handed to Claude Code. Nothing here needs you to know Kubernetes, and nothing here happens to your default branch without a pull request you merged.
Create your account
Email address, no card. The trial runs 14 days and includes a Rough Cut environment to deploy into; add a card (not charged during the trial) when you want production apps and a managed database.
Create an account →Connect GitHub
Install the Blank Cut App on the repository you want to ship, or let the wizard create a private one in your account seeded with a runnable Next.js or Vite starter. This step is a browser sign-in, which is why it comes before the terminal.
Merge the scaffolding pull request
We open a PR adding what your repo is missing: a hardened multi-stage Dockerfile, the build workflow, a deploy manifest and a declaration of the keys your app may read. Read it like any other PR. Nothing reaches your default branch until you merge.
Hand the CLI to your coding agent
Open CLI setup in the portal. Answer two questions and it writes a prompt you paste straight into Claude Code: the agent installs the CLI, signs it in, checks it works, then validates your repo and tells you what it would change before changing anything. No key needs to pass through your hands — the terminal login mints its own and you approve it in the browser.
Ship it
blankcut promote turns the release into one change to your app's deployment config. A scope guard and our deploy reviewer check it, anything the reviewer isn't sure of waits for one of our engineers, and then the scanned, digest-pinned image rolls out with probes, right-sized resources and a rollback path. Watch it land in the console.
Working with an agent
What Claude Code can do for you, and what it can't.
The CLI is one binary and every command is scriptable, so an agent can drive the whole pipeline. The exceptions are the steps that prove it's you: signing up, installing the GitHub App and approving the CLI's sign-in. Those are exceptions on purpose.
It can
- Check the repo against the platform's rules, with blankcut validate
- Build, scan and ship a reviewed release, with blankcut promote
- Load values into the encrypted store, with blankcut secrets push
- Report what is running and how it got there, with blankcut status
It can't
- Create your account. Signup is a browser flow, by design
- Install the Blank Cut GitHub App. That is a browser sign-in
- Approve its own CLI sign-in. blankcut login waits for you to confirm the code in your browser
The prompt the portal generates already knows this. If you run it in a directory with no project yet, it stops and sends you to the wizard rather than burning turns on a call that cannot succeed from a terminal.
Start at step one.
Steps two and three usually take a coffee. After that your agent can take the keyboard.