Clone Code · For your team's ClonesBeta

Your team's Clones build software.And ship it into your stack.

Anyone on your team can ask a Clone, in plain words, for an internal tool, a dashboard on company data or a new landing page. Clone Code plans, writes, runs and tests the code in a private sandbox, hands back a live preview and the full source, and, with the connections each person sets up, deploys to your company's repo, cloud and domain. It also works the admin portals that have no API. Every job runs through the same secure process.

Live preview
Your cloneClone Code on
Internal tools

Build an IT request form our team can start using today.

Ready for review:

  • Request type, priority and details fields
  • Run and tested in a private sandbox
  • The full source in a zip for your repo
Live preview ↗ Download zip ↓
Ask your Clone to build something…
~4 minfrom one request to a complete website
70 secto inventory every Worker and Pages project in a Cloudflare account
101providers your team can connect
11categories, from cloud platforms to payments
7 daysto keep iterating on the same project

From real Clone Code jobs.

What it does

Build it. Ship it. Run it.

Your team's Clones don't stop at writing code. Clone Code runs and tests what it writes, deploys it into the systems your company already uses, and takes on routine portal work in between.

Build

Internal tools, on request.

Forms, dashboards on company data, landing pages, scripts and automations. Clone Code writes the code, runs it and tests it before anyone on the team sees it.

  • A live preview for reviewers, the full source for engineers
  • Feedback changes the same project
  • Most jobs finish in 2 to 15 minutes
What teams build
Deploy

Into your company's stack.

Each person connects the systems they work with, from 101 providers or any API key, so Clone Code can ship builds to the company repo, cloud and domain.

  • GitHub, Google Cloud, AWS, Cloudflare, Vercel and more
  • Checked with a test call when saved
  • Read & write, or Read-only, per connection
Connections
Operate

The portals your team logs into.

For admin portals and dashboards with no API, Clone Code drives a real browser. People watch it live and take over whenever a sign-in is needed.

  • Ad platforms, analytics, admin panels, vendor portals
  • Each person signs in themselves; passwords are never seen
  • Logins remembered for later jobs
The browser
For every team

The tools your teams keep asking for, built on request.

Internal tools, dashboards on company data, sites and automations. A few requests your teams could send today.

Internal tools

“Build an equipment checkout app so staff can reserve laptops and cameras.”

Dashboards on company data

“Turn our Postgres orders table into a weekly sales dashboard for leadership.”

Websites & landing pages

“Create a landing page for our customer webinar with a registration form.”

Calculators

“Build an ROI calculator our sales team can send to prospects.”

Training games

“Make a quiz game for our new-hire security training.”

Scripts & tools

“Write a script that checks every link on our website and lists the broken ones.”

Data cleanup

“Merge these three vendor spreadsheets, remove duplicates and standardize the addresses.”

Automations & workflows

“Build a workflow that posts each new support ticket into the right Slack channel.”

It can also start from a public GitHub repo: “Start from this repo and add our brand colors.”

The workflow

One request in. Working software out.

  1. 01RequestAnyone on the team asks a Clone in chat, or by voice or SMS where the Clone has those.
  2. 02PlanThe Clone passes the job to Clone Code, which plans the build.
  3. 03BuildReal code, written in a private sandbox for that job alone.
  4. 04Run & testClone Code runs what it wrote, tests it and fixes what it finds.
  5. 05Hand overA summary, a live preview and the full source, posted to the chat.
  6. 06IterateFeedback arrives as a follow-up and changes the same project.
Most jobs: 2 to 15 minutesLarge builds: up to 45 minutesStatus updates in the chat while it works
The handover

A preview to review. Source files to keep.

When a job finishes, the Clone posts a summary, a live preview link for websites and apps, and a zip of the full source. Reviewers open the preview; engineers take the source into your repo, or let Clone Code push it there.

In our own testing, a complete small-business website took about 4 minutes from a single request.

  • Code is run and tested before anyone reviews it
  • Preview links work on any device
  • The zip holds every file of the project
  • Status updates in the chat while it works
Your cloneClone Code finished

The IT request form is ready. It has request type, priority and details fields, a confirmation page and a list of open requests. I ran it and tested every page.

Reply in the chat to keep iterating

Live preview

Add a priority field and use our brand blue for the header.

Updated the same project:

  • Priority field added to the form
  • The header uses your brand blue
  • New preview link and zip are ready
Open the new preview ↗
Iterate

Review it like a product owner. It keeps the project.

Feedback goes in as a follow-up message, and Clone Code changes the same project instead of starting over. Projects stay available for 7 days; “start a new project” begins a fresh one.

“Add a priority field”“Use our brand blue”“Add an export to CSV”“Make it work on phones”“Start a new project”
Your company's stack

Connect the stack you run. Ship into it.

Each person says “open my Clone Code connections” and connects the systems they work with, from 101 providers. Clone Code can then take a build all the way to the company repo, cloud and domain, or work with the systems already running.

CodeBuilt by Clone Code
Included
RepoPushed to your repo
CloudDeployed to your cloud or host
DomainYour domain points at it
Clone CodeConnectionsPrivate link · 24 h
Your deploy path✓Code→✓Repo→3Cloud→4Domain
  • Popular12
  • Cloud Platforms8
  • Code & Deployment13
  • Hosting & Content16
  • Databases9
  • Payment Gateways15
  • SaaS Applications9
  • Social16
  • Marketing & Analytics6
  • Automation & Workflow5
  • Workspace5
  • Custom2
GitHubCode & Deployment
Connect
Google CloudCloud Platforms
Connect
AWSCloud Platforms
Connect
VercelCode & Deployment
Connect
CloudflareCode & Deployment
Connect
GoDaddyHosting & Content
Connect
WebflowHosting & Content
Connect
SupabaseDatabases
Connect
StripePayment Gateways
Connect
  • 101 providers in 11 categories, plus any API key, credential file or MCP server
  • Each person's connections are their own
  • Checked with a test call when saved
  • Read & write, or Read-only
  • Payments save in Test until switched to Live
Explore connections
Admin portals

No API? Your portals still count.

Plenty of business tools only have a website. Clone Code drives a real browser through them while the requester watches live. When a portal needs a sign-in, that person takes over, signs in, handles any 2-step code or captcha, and hands back control. Clone Code never sees the password.

Logins are remembered, encrypted, for that person's later jobs. We use it ourselves to read Google Ads spend from the ads dashboard.

  • Ad platforms, analytics, admin panels and vendor portals
  • Every step visible live
  • All saved logins can be forgotten in one click
How the browser works
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
Ideas for every team

Requests your teams could send today.

Build

“Build an internal directory of our vendors with search and filters.”

“Make a time-off request form for the operations team.”

“Turn our price list spreadsheet into a quoting tool for sales.”

“Build a status page for our internal services.”

Connect & ship

“Pull this quarter's Stripe payouts into a dashboard for finance.”

“Push this project to our GitHub and open a pull request for review.”

“Deploy the new careers page to Vercel and point careers.ourcompany.com at it.”

“List our Cloud Run services and flag the ones with no recent deploys.”

Operate

“Check our Google Ads spend and pause anything over budget.”

“Pull last week's numbers from our analytics dashboard for the Monday meeting.”

“Inventory every Worker in our Cloudflare account and describe what each one does.”

“Compare this month's Search Console clicks with last month for our top pages.”

Why teams use it

Small tools and routine ops, off the engineering backlog.

The usual backlogWith Clone Code
Small toolsWaiting behind bigger projects in the engineering backlogRequested in a sentence and built by a Clone, usually in minutes.
First versionA spec, a ticket, then rounds of reviewA live preview and the full source, posted back to the chat.
IterationA new ticket for every tweakA follow-up message changes the same project.
DeploymentHand-offs between whoever built it and whoever runs the cloudPushed to the company repo, deployed to your cloud, on your domain.
Ops choresSomeone logs in to five portals to compile one reportA Clone reads them, through a connection or a real browser.
CredentialsKeys shared in chats and spreadsheetsEncrypted once, never shown again; people sign in to sites themselves.
For IT and security

Built for real company systems. Run through one secure process.

Clone Code can reach production systems, so every job, for every person, follows the same steps.

  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.

Keys under encryption

Encrypted with Google Cloud KMS and never shown again after they're saved.

Least privilege by choice

Any connection can be read-only, and payments stay in Test until switched to Live.

Caps and an audit trail

Every job has a spending cap, and each connection lists the jobs that used it.

Security details for IT

Roll it out

Three steps. A first build the same day.

  1. 1Add the skillIn Clone Studio, add the Clone Code skill to the Clones your team works with.
  2. 2Send a first requestAnyone working with the Clone asks for what they need, in plain words.
  3. 3Connect your systemsOptional: each person says “open my Clone Code connections” and connects the systems they use.
FAQ

Questions from teams, answered.

What does Clone Code give our team?

A software engineer for your team's Clones. Anyone can ask a Clone, in plain words, for a tool, a dashboard, a page or an automation. The Clone hands the job to Clone Code, a coding agent that plans, writes, runs and tests real code in its own private sandbox, then posts a summary, a live preview and the full source to the chat. With connections, it can deploy what it built and work with your company's systems.

Does our team need developers to use it?

No. Requests are written the way you would brief a colleague: what it's for, who uses it, what it should show. Engineers on your team can still review the source, or have Clone Code open a pull request.

What do teams build with it?

Internal tools, dashboards on company data, websites and landing pages, calculators, training games, scripts, data cleanup, and automations and workflows. It can also start from a public GitHub repo.

What comes back when a job finishes?

A message in the chat with a summary of the work, a live preview link for websites and apps, and a zip of every file. People can keep chatting while it works, and it posts status updates along the way.

How long do jobs take?

Most jobs finish in 2 to 15 minutes, and large builds can take up to 45. In our own testing, a complete small-business website took about 4 minutes.

Can we iterate on a build?

Yes. Follow-up messages change the same project, which stays available for 7 days. Saying “start a new project” begins a fresh one.

Can it deploy to our company's systems?

Yes, once someone connects them. Each person says “open my Clone Code connections” and gets a private link to their Connect page, with 101 providers plus any API key, credential file or MCP server. Clone Code can then push to your repo, deploy to your cloud or host and point your domain at it.

Can it work in admin portals that have no API?

Yes. Clone Code drives a real browser that people can watch live. When a portal needs a sign-in, the person takes over, signs in themselves and hands back control. Clone Code never sees the password.

How is company data protected?

Every request is verified with the Clone platform before any connection is used, and connections load only into the jobs of the person who owns them. Keys are encrypted and never shown again, each job runs in its own sandbox that is torn down afterwards, and any connection can be read-only. The security page has the full process.

How is it billed?

Usage is billed to your plan like other skills, based on how much work each task takes, and every job has a spending cap. Teams can start on the 30-day Free Trial plan.

Can people ask by voice or SMS?

Yes, on Clones that have voice or SMS. The request works the same way, and the result is posted to the chat.

Is Clone Code generally available?

Clone Code is in Beta. It is improving quickly and some details may change, so tell your Clone what works for your team and what doesn't.

Give your team's Clones a software engineer. Start with the 30-day Free Trial.

Start a free trial, add Clone Code to your Clones and send a first request. Or book a demo and see it build, test and deploy with your team.