Clone Code · SecurityBeta

Powerful by design.Safe by process.

Clone Code can build, deploy and operate real systems, so it runs every job through the same secure process: verified as you, your connections only, a private sandbox for each job, keys that are never shown again, and controls that stay in your hands.

Your connectionsTied to your verified email
Encrypted
  • GitHubKey hidden · checked on save
    Read & write
  • CloudflareKey hidden · checked on save
    Read & write
  • StripeKey hidden · checked on save
    Test mode
  • PostgreSQLKey hidden · checked on save
    Read-only
  • Google AnalyticsKey hidden · checked on save
    Read-only

Loaded only into your own jobs. Each job runs in its own sandbox, torn down afterwards.

The secure process

Every job. The same six steps.

  1. You askIn your clone's chat.
  2. Verified as youThe Clone platform confirms it's you before any connection is used.
  3. Your connections onlyLoaded only into your own job, never anyone else's.
  4. A private sandboxEach job runs alone, with a short-lived job token.
  5. Results, scrubbedSecrets removed from previews, served from a separate domain.
  6. Torn downThe sandbox is deleted when the job ends.
Your keys

Saved once. Never shown again.

Encrypted with Google Cloud KMS

Keys are encrypted when you save them and never shown again, not even to you.

Never in chat

Keys go in your Connect page, never into chat. If you try, your clone tells you not to.

Tied to your verified email

Connections belong to you, follow you across your clones and load only into your own jobs.

The sandbox

Each job alone. Torn down afterwards.

An isolated sandbox per job

Each job runs in its own sandbox, separate from every other job, and is torn down when it ends.

Only a short-lived job token

Clone's own AI key never enters the sandbox. The sandbox only gets a short-lived token for that job.

Secrets scrubbed from previews

Secrets are scrubbed from preview links. Previews and zips are served from a separate domain, not the brand site.

Your controls

Decide how far it may go.

You choose what each connection may do, and you can see what used it. Combine the controls to keep a connection as low-risk as you like.

  • Read-only per connection
  • Test mode for payments: no real money moves
  • Notes like “never touch billing”
  • A spending cap on every job
  • An audit of which jobs used each connection
  • Remove a connection any time
GitHubYour repos · Read & write
Read & writeCheck passed

Open a pull request, never push to main.

Used by 6 jobs

StripeRestricted key
Read-onlyTestCheck passed

Reports only. Never touch billing.

Used by 2 jobs

Google CloudService account · default region set
Read & writeCheck passed

Used by 4 jobs

ads.example.com/sign-inLive
Your turn: please sign inClone Code paused. Sign in yourself, then hand back.
Take over
You're watching liveNext: open the Campaigns report
Browser sign-ins

Your password stays yours.

When a website needs a sign-in, you take over and sign in yourself, including any 2-step code or captcha. Clone Code never sees your password. Saved logins are encrypted, and you can forget all of them with one click.

How the browser works
Good habits

A few minutes of setup. Much less to worry about.

Use least-privilege keys

Where a service offers restricted or scoped keys, give Clone Code only what the job needs.

Start read-only

Let it look first. Switch a connection to Read & write when you're ready for it to make changes.

Write it down

Add notes like “open a pull request, never push to main” to set the ground rules for a connection.

Allowlist one address

Clone Code connects from a fixed outbound IP, shown on the connection form, so you can keep allowlists tight.

FAQ

Security: questions, answered.

Who can use my connections?

Only your own jobs. Every request is verified with the Clone platform as you before your connections are used, and connections are tied to your verified email.

How are my keys stored?

Encrypted with Google Cloud KMS. They're never shown again after you save them, and they're loaded only into your own jobs.

Should I paste a key into chat?

No, never. Use the Connect page instead. If you try, your clone will tell you not to.

Where does the code run?

Each job runs in its own isolated sandbox that is torn down afterwards. Clone's own AI key never enters the sandbox; it only gets a short-lived job token.

Can a preview link leak a secret?

Secrets are scrubbed from preview links, and previews and zips are served from a separate domain, not the Clone brand site.

Does Clone Code ever see my website passwords?

No. When a site needs a sign-in, you take over and sign in yourself. Saved logins are encrypted, and you can forget all of them with one click.

How do I keep a connection low-risk?

Make it Read-only, keep payments in Test mode, add notes like “never touch billing”, and use restricted or least-privilege keys where the service offers them. Each job also has a spending cap.

Can I see what happened?

Yes. Each connection shows which jobs used it, and you can remove any connection at any time.

Build with confidence. Stay in control.

Start a free trial and connect your first system read-only, or book a demo and we'll walk through the secure process with you.