Pull requests only. Never push to main.
Used by 9 jobs
Clone Code can build, deploy and operate real company systems, so every job, for every person on your team, runs through the same process: identity verified, that person's connections only, an isolated sandbox per job, keys that are never shown again, and controls each connection owner sets.
Loaded only into that person's jobs. Every job gets its own sandbox, deleted when it finishes.
Keys are encrypted at save and never shown again, to anyone.
Keys belong on the Connect page. If someone tries to paste one into chat, the Clone tells them not to.
Each connection is tied to one person's verified email and loads only into that person's jobs.
Each job runs in its own sandbox, apart from every other job, and is torn down when it ends.
Clone's own AI key never enters the sandbox. The sandbox receives only a short-lived token for that job.
Secrets are scrubbed from preview links, and previews and zips are served from a separate domain, not the brand site.
Owners decide what each connection may do and can see what used it. Combined, the controls keep any connection as narrow as your policies require.
Pull requests only. Never push to main.
Used by 9 jobs
Finance reports only. Never touch billing.
Used by 3 jobs
Deploy to staging only.
Used by 5 jobs
When a website needs a sign-in, the person takes over and signs in themselves, including any 2-step code or captcha. Clone Code never sees the password. Saved logins are encrypted and can all be forgotten with one click.
How the browser worksUse scoped service accounts and restricted keys that cover only what the job needs.
Start connections read-only and switch to Read & write once a workflow is trusted.
Add notes like “deploy to staging only” or “pull requests only, never push to main”.
Clone Code connects from a fixed outbound IP, shown on the connection form, so allowlists stay tight.
Every request is verified with the Clone platform before any connection is used. Connections belong to individual people, are encrypted with Google Cloud KMS and load only into that person's jobs. Each job runs in an isolated sandbox that is torn down afterwards.
Only the person who created it, in their own jobs. Connections are tied to that person's verified email.
Encrypted with Google Cloud KMS and never shown again after saving, to anyone.
They shouldn't, and the Clone will tell them not to. Keys belong on the Connect page.
In an isolated sandbox per job, torn down when the job ends. Clone's own AI key never enters the sandbox; it receives only a short-lived job token.
Secrets are scrubbed from preview links, and previews and zips are served from a separate domain rather than the Clone brand site.
No. People sign in to websites themselves during a takeover. Saved logins are encrypted, and all of them can be forgotten with one click.
Use Read-only where you can, keep payments in Test, add notes like “deploy to staging only”, use least-privilege service accounts or restricted keys, and allowlist the fixed outbound IP shown on the connection form. Every job also has a spending cap.
Start a free trial and connect a first system read-only, or book a demo and walk through the security process with us.