Clone Code · SecurityBeta

Real access to company systems.One secure process.

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.

A team member's connectionsTied to their 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 that person's jobs. Every job gets its own sandbox, deleted when it finishes.

The process

Every job, every person. Six steps, always.

  1. RequestA team member asks a Clone in chat.
  2. Identity checkThe Clone platform verifies the person before any connection is used.
  3. Their connections onlyOnly that person's connections load, into their own job.
  4. Isolated sandboxOne sandbox per job, with a short-lived job token.
  5. Clean outputSecrets scrubbed from previews, which are served from a separate domain.
  6. TeardownThe sandbox is deleted when the job finishes.
Credentials

Stored once. Never displayed again.

Google Cloud KMS encryption

Keys are encrypted at save and never shown again, to anyone.

Never in chat

Keys belong on the Connect page. If someone tries to paste one into chat, the Clone tells them not to.

Owned by a person

Each connection is tied to one person's verified email and loads only into that person's jobs.

Isolation

A sandbox per job. Deleted afterwards.

Isolated per job

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

A short-lived job token

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

Scrubbed, separate previews

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

Controls

Each connection owner sets the limits.

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.

  • Read-only per connection
  • A Test / Live switch on payments, Test by default
  • Notes like “deploy to staging only”
  • A spending cap on every job
  • A list of the jobs that used each connection
  • Connections removable at any time
GitHubCompany repos · Read & write
Read & writeCheck passed

Pull requests only. Never push to main.

Used by 9 jobs

StripeRestricted key · finance reporting
Read-onlyTestCheck passed

Finance reports only. Never touch billing.

Used by 3 jobs

Google CloudService account · staging project
Read & writeCheck passed

Deploy to staging only.

Used by 5 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
Website sign-ins

Employees' passwords stay with employees.

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 works
Recommended setup

A short checklist for IT.

Least-privilege credentials

Use scoped service accounts and restricted keys that cover only what the job needs.

Read-only first

Start connections read-only and switch to Read & write once a workflow is trusted.

Written ground rules

Add notes like “deploy to staging only” or “pull requests only, never push to main”.

One address to allowlist

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

FAQ

Security for IT teams: questions, answered.

What should our IT team know first?

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.

Who can use a given connection?

Only the person who created it, in their own jobs. Connections are tied to that person's verified email.

How are keys stored?

Encrypted with Google Cloud KMS and never shown again after saving, to anyone.

Can someone paste a key into chat?

They shouldn't, and the Clone will tell them not to. Keys belong on the Connect page.

Where does the code run?

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.

Could a preview expose a secret?

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

Does Clone Code see employees' website passwords?

No. People sign in to websites themselves during a takeover. Saved logins are encrypted, and all of them can be forgotten with one click.

How do we keep access tight?

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.

Bring Clone Code to your team. On your security terms.

Start a free trial and connect a first system read-only, or book a demo and walk through the security process with us.