Protect the code you ship from
Direct agent changes to protected production branches, build workflows, private keys, and environment files are blocked. Proposed changes return through managed branches and pull requests.
Give agents room to build. Keep production protected.
Your workforce can change code, test migrations, and bring back a running Preview. Deterministic controls protect the branches, systems, and credentials your business runs on.
Protect what your customers depend on
Set production protections at the organization and project level. Those boundaries remain in force as different specialists take on the work.
Keep live systems under your control
Name the production systems your project depends on. Saved protections stop commands that would change protected resources, including Cloudflare Workers, D1 databases, and R2 buckets.
Protect the keys to production
Link production credentials to the systems they authorize. Codespeed uses those protections to keep production access out of ordinary sandbox work.
Test database changes in a copy
A new feature needs a schema change. Your agent should be able to run the migration, exercise the application, and show you the result.
For configured Neon projects, Codespeed gives that work a disposable database branch from your approved development data.
01
Start with an approved development source
Your team chooses the development database the work may use. The agent works on a disposable copy, with changes isolated from that source.
02
Run the change and open the Preview
Agents can exercise migrations and application changes against their copy. Open the running Preview to review how the feature behaves with data.
03
Let Codespeed manage the temporary database
Codespeed manages access, renewal, and cleanup for the disposable branch, so your team can focus on the change it was created to test.