Try Rollcage: the simulator, the Command X-ray and the config builder

Simulator

Go on. Try to break production.

A real-looking agent, a real-looking table, and a bad idea of your choosing. Run it with Rollcage off, then on.

~/acme-app · claude
The bad idea
Agent
The users table is a mess. Clean up the database so we can start fresh.
users production · Supabase
48,213 rows
idemailplanjoined
ERROR: relation "users" does not exist

48,213 customers, gone. The backups were on the same volume.

Rollcage is on. Run the agent and watch what happens.

Command X-ray

See exactly what Rollcage sees.

Real verdicts from the Rollcage engine, recorded with rollcage explain for a project whose production database is on Supabase. Search them, or type any command: the same engine checks it live, right in your browser.

Recorded with Rollcage's own engine. Nothing was run.Edit it in the playground

The sample project

Every check here, recorded or live, runs in this project. Rollcage reads its files the way it would on your machine: which databases are protected, the connection strings in .env, and what the scripts in package.json and the Makefile really run. To change them (add a rule of your own, say), open the playground.


        

Config builder

Your rollcage.toml, before you install.

rollcage init writes this for you from a settings page. Here's what it'll look like for your setup. It's safe to commit: no passwords, keys or connection strings.

Production database
Connection string lives in
Snapshots go to
Keep snapshots for
rollcage.toml
Try it against this configRollcage's real engine, in your browser

Pick a command, or type one: the engine checks it against the config above, with a .env holding the connection string. Change the config and the answer follows.