Clone Code · ConnectionsBeta

Connect your company's stack.Each person, their own connections.

Your repos, clouds, hosting, domains, databases, payment systems and business apps, from 101 providers or any API key. Each team member connects the systems they work with, so Clone Code can deploy builds and work with live company systems, under the rules they set.

Clone CodeConnectionsPrivate link · 24 h
Your deploy path✓Code→✓Repo→3Cloud→4Domain
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
Setup

Five steps per person. A few minutes, once.

  1. Request the linkEach person says “open my Clone Code connections” to a Clone.
  2. Open the Connect pageA private link, valid for 24 hours.
  3. Choose a provider101 providers in 11 categories, or any API key, file or MCP server.
  4. Add the credentialPaste a key, or sign in through your own OAuth app.
  5. VerifiedA harmless test call confirms the connection on save.
The deploy path

Code → Repo → Cloud → Domain. Builds that reach production.

With a repo, a cloud or host and a domain connected, Clone Code can take a build all the way live: push the code, deploy it and point the domain at it.

CodeBuilt by Clone Code
Included
RepoPushed to your repo
CloudDeployed to your cloud or host
DomainYour domain points at it

Build an internal status page and deploy it to our Cloudflare account.

Live on your domain:

  • Status page built, run and tested
  • Code pushed to the company GitHub repo
  • Deployed to your Cloudflare account
  • status.ourcompany.com points at it
Open the live page ↗

List our Cloud Run services.

Here are your services:

  • Every service, by name and region
  • Nothing was changed: this connection is read-only
The catalog

101 providers. 11 categories.

The catalog each person sees on their Connect page, from cloud platforms to payment gateways. Systems that aren't listed still connect.

Cloud Platforms8 to connect

AWS, Azure, Google Cloud, DigitalOcean, Hetzner, Kubernetes, Linode / Akamai, SSH Server

Code & Deployment13 to connect

Cloudflare, GitHub, Vercel, Bitbucket, Docker Hub, Expo (EAS), Fly.io, GitHub Container Registry, GitLab, Netlify, Railway, Render, Sentry

Hosting & Content16 to connect

GoDaddy, Shopify, Webflow, WordPress (self-hosted), Contentful, cPanel hosting (Bluehost, HostGator, etc.), Ghost, Hostinger, HubSpot CMS, Namecheap, Porkbun, Sanity, Squarespace, Strapi, Wix, WordPress.com

Databases9 to connect

MySQL, PostgreSQL, Supabase, BigQuery, Firebase, MongoDB Atlas, Neon, Redis / Upstash, Snowflake

Payment Gateways15 to connect

PayPal, Plaid, Square, Stripe, Adyen, Authorize.net, Braintree, Checkout.com, Coinbase Business (formerly Coinbase Commerce), Dwolla, GoCardless, Lemon Squeezy, Mollie, Paddle, Razorpay

SaaS Applications9 to connect

Auth0, Clerk, Pinecone, Resend, SendGrid, Twilio, AI model APIs

Social16 to connect

Discord, LinkedIn, Meta Business (Facebook + Instagram), WhatsApp Business, X (Twitter), YouTube, Ayrshare, Bluesky, Google Business Profile, Mastodon, Pinterest, Reddit, Snapchat (Marketing API), Telegram, Threads, TikTok

Marketing & Analytics6 to connect

Google Analytics 4 / Tag Manager, Google Search Console, Meta Conversions API, Mixpanel, PostHog, Segment

Automation & Workflow5 to connect

n8n, Make, Webhook signing secret, Zapier, MCP server

Workspace5 to connect

Google Workspace, Microsoft 365, Notion, Obsidian (via GitHub), Slack

CustomAnything that isn't listed
  • Any API key: any service, under your own variable names
  • Credential file: config files, certificates, kubeconfig
  • Any MCP server: any tool that speaks MCP, by URL and token

The Social category connects the social and messaging platforms that your builds work with.

Ground rules

Every connection on the owner's terms.

Connections are Read & write by default, or Read-only when Clone Code should only look. Notes in plain words set the ground rules. Every connection is checked when it's saved and lists the jobs that used it.

  • Read & write, or Read-only, per connection
  • Notes like “deploy to staging only”
  • A Test / Live switch on payment connections, Test by default
  • Checked with a harmless test call on save
  • A list of the jobs that used each connection
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

What IT will ask

Answers before the first connection.

Encrypted keys

Encrypted with Google Cloud KMS, never shown again after saving, and loaded only into the owner's jobs.

Per-person by design

Connections are tied to each person's verified email and are never shared with teammates.

Kept out of chat

Keys go on the Connect page, never into a chat, and the Clone reminds people of that.

Your OAuth apps

OAuth providers use your company's own app: you bring your own client ID.

Allowlist-ready

A fixed outbound IP, shown on the connection form for providers that need an allowlist.

Test before Live

Payment connections have a Test / Live switch and save in Test. No real money moves in Test.

The full security process

Put them to work

Requests that use your connections.

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

Reads Stripe through a read-only connection and builds a dashboard behind a preview link.

Push this project to our GitHub and open a pull request.

Commits to the company repo and opens a pull request for your engineers to review.

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

Ships the page to your host and points the subdomain at it.

Export our Postgres orders table to a spreadsheet.

Runs the query against your database and sends back the file.

Compare last week's Search Console clicks for our top pages.

Reads Search Console and summarizes the changes in chat.

How many new orders did our Shopify store get last month?

Reads the store data and answers in chat.

FAQ

Connections for teams: questions, answered.

Who sets up the connections?

Each person, for the systems they use. Saying “open my Clone Code connections” to a Clone sends a private link to that person's Connect page, valid for 24 hours.

Do teammates share my connections?

No. Connections are tied to each person's verified email and loaded only into that person's own jobs. They do follow that person across all of their Clones.

Which systems can we connect?

101 providers in 11 categories: cloud platforms, code and deployment, hosting and content, databases, payment gateways, SaaS applications, social, marketing and analytics, automation and workflow, workspace, and custom. Anything else connects with Any API key, a Credential file or an MCP server.

How do we know a connection works?

Every connection is checked with a harmless test call when it's saved, and the Connect page shows the result.

Can we limit what Clone Code may do?

Yes. Each connection is Read & write by default or Read-only, and notes such as “deploy to staging only” or “never touch billing” set the ground rules.

What about payment systems?

Each payment connection has a Test / Live switch and saves in Test by default. Clone Code never moves real money with a Test connection.

Our databases only accept allowlisted IPs. Will it connect?

Yes. Clone Code connects from a fixed outbound IP address. For providers that need an allowlist, the address is shown on the connection form.

How are OAuth providers handled?

With your own app: you bring your own client ID, so the app and its permissions stay in your company's account.

How are keys stored?

Encrypted with Google Cloud KMS, never shown again after saving, and loaded only into the owner's jobs. Keys never belong in chat, and the Clone will say so.

Can we audit what used a connection?

Yes. Each connection lists the jobs that used it, and it can be edited, tested or removed at any time.

Connect your company's systems. Let your Clones ship.

Start a free trial, add Clone Code to your Clones, then say “open my Clone Code connections”. Or book a demo and connect the first systems with us.