delete-stack
…on the wrong stack
The name was close. The database was not.
Claude writes CloudFormation fast — and just as confidently when it is wrong. Clawform is the safety layer that stops the confident mistakes from reaching your AWS account.
Try free for 14 daysSee what it blocks
Then $29 one-time per seat, or $79 for a ten-device team licence. First ten orders 10% off, until 31 August 2026 —buy a seat now.
> the old billing stack is failing, delete it and redeploy $ aws cloudformation delete-stack --stack-name p-acme-billing-rds ✕ [clawform hook] Direct `aws cloudformation delete-stack` is blocked by Clawform. Use the `/rollback` slash command (it inspects retained data resources first). exit 2 — the command never ran
01 — The problem
None of these are exotic. They are what fast, plausible generation looks like when nothing is checking it.
delete-stack
…on the wrong stack
The name was close. The database was not.
!ImportValue !Sub "…"
Two short-form tags on one node
Not valid YAML — and it reads fine until the parser says otherwise.
DeletionPolicy
Missing on an RDS instance
The stack rolls back. So does the data.
*:*
An IAM policy with a wildcard
It makes the error go away. That is the problem.
02 — How it works
Everything runs on your own machine against your own AWS account. Clawform never receives your infrastructure data or your credentials.
LAYER 01
Naming convention, retention policies, the anti-patterns to avoid. Loaded on demand, per task — not one wall of context it skims.
LAYER 02
Deterministically, through changesets, surfacing a diff you confirm. A skill can never call AWS directly; it has to go through the CLI.
LAYER 03
Deleting a stack, dropping a database, force-emptying a bucket. The agent never sees the tool call succeed — the mistake is caught on its way to your account, not after.
03 — Honest limits
The hook inspects the commands it is handed. Work it cannot read — a script written in one step and executed in the next — it flags rather than blocks, and says so out loud.
It is a deterrent at the point of action, not a sandbox. Pair it with the account-level controls you would want anyway — SCPs, permission boundaries, a separate production account.
Every tool in this space could tell you that. Most do not.
$ bash ./scripts/teardown.sh ! [clawform hook] Clawform cannot read the contents of the script in "bash ./scripts/teardown.sh" — commands inside a script file are invisible to this guard. Review it before letting the agent run it. (The guard inspects commands it can see; it is a deterrent, not a sandbox.) exit 0 — the command runs
04 — Fit
A fit
Teams running AWS CloudFormation who already useClaude Code and have production infrastructure worth protecting.
Not a fit yet
Not for you today if you use Terraform, CDK, or Pulumi, or deploy anywhere other than AWS. Other stacks and clouds are where this is going — but buy it for what it does now, not for what is on the roadmap.
05 — Pricing
Sold per seat, with device activations you can move — so a new machine is a deactivation, not a support ticket.
Licensing runs on Polar's licence-key API for activation, periodic validation and deactivation. No telemetry, no infrastructure data, no AWS credentials ever reach us.
Per seat
$29 $26.10
10% off for the first ten orders, until 31 August 2026 — whichever comes first. The checkout shows the price that actually applies.
What $29 buys: the incident that never happens. Restoring one deleted database, rotating one leaked credential, or explaining one security group opened to the world costs more of your week than this costs money — and the templates mean your next stack starts reviewed instead of blank.
clawform CLI, from npmOne-time purchase. No subscription.
Team
$79 $71.10
Same 10% off, same window. Ten activations at $79 is $7.90 a developer, against $29 bought one at a time.
What $79 buys: every engineer opens every client account with the same guardrails from day one. That is the conventions document you never have to write, the onboarding you never have to police, and one line on the expense report instead of ten.
The software is identical. What you buy is the device count.
Not sure yet? Take a free 14-day trial — the full kit, email-only checkout, no card. One trial per machine (activation records a device fingerprint —details in the docs). When it lapses, the value commands stop; deploy and rollback are never licence-gated, so a trial ending cannot strand a stack.
06 — Where it is going
Nothing in the three layers is specific to CloudFormation. Rules the agent reads, a tool that makes the real change reviewable, a guard that refuses what nobody should run by accident — that pattern holds for any infrastructure language and any cloud.
Shipping now
AWS CloudFormation, in Claude Code. Everything on this page works today.
Being built
More infrastructure languages, more clouds — Azure, GCP, DigitalOcean — and more agents than Claude Code, including Codex and Cursor.
No dates, on purpose. A schedule from a one-person vendor is a guess wearing a calendar, and you would be paying for it. Buy this for what it does today; the rest arrives when it is done, and your licence covers it when it does.
06 — After you buy
The key arrives by email. Nothing else is needed — no account, no dashboard, no agent running in the background.
$ npm i -g @thejoseki/clawform $ clawform activate <your-key> $ clawform init plugin the plugin is unpacked from your activated copy
No subscription, no seat you have to keep paying to keep. Questions before you buy get answered by the person who wrote it — that is not a support promise, it is just how small this is.