NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
ResourcesGuides and case studiesMagazineVideo guidesNews tickerIntegrationsEscrow agreement
Why the hub changed. Production's /integrations opens on product filters for the old line-up (Software Backup, Software Escrow, Saas Escrow, Continuity Escrow, each with "Standard" and "Advanced" integrations), a search box and a grid of 41 cards: 25 link to the 24 integration pages (Azure Blob and Microsoft Azure share one), and the other 16 (Adyen, Alibaba Cloud, Amazon Web Services, Chargebee, DigitalOcean, Heroku, IBM Cloud, Mailchimp, Okta, Oracle Cloud, Rackspace, Sendbird, Shopify, Stripe, Twilio, Zendesk) have no page and no stated method; they look like the services a SaaS or Continuity environment depends on.
  • "50+ integrations" stays, flagged (decided 7 Oct: production stats stay, flagged, until Product confirms). Production says "50+" in its FAQ and on product pages, but its own grid shows 41 cards (40 platforms) and only 24 have pages. The hero no longer states a count; the trust row keeps the production figure, flagged. Earlier draft counted the 24 with pages, plus Secure Upload. The rest of the kit still says "50+" (home, escrow, FAQ): reconcile the figure sitewide before launch, and decide whether the 16 service providers belong on this page.
  • The headline is the job: integrations exist so the deposit stays current, which is where recovery starts.
  • Slim hero, because the grid itself is the visual.
Integrations

Connect once. Deposits stay current.

Codekeeper connects to the platforms where your code and files live, from GitHub to Amazon S3, with Secure Upload for anything else. Connected platforms sync daily, so the version we hold keeps pace with the version you run.

Book a demo Get the sample evidence pack
  • 50+ integrations, plus Secure Upload
  • ISO/IEC 27001:2022 certified
  • Trusted by 3,500+ teams
Find your platform in one click. The 24 production integrations with their own pages, alphabetical, filtered by what the platform is: Code hosting: Amazon CodeCommit, Assembla, Azure DevOps, Beanstalk, Bitbucket, Bitbucket Server, CloudForge, Codebase, GitHub, GitHub Enterprise, GitLab, GitLab Self-Managed, ProjectLocker, RepositoryHosting, Visual Studio; Cloud storage: Amazon S3, Azure, Google Cloud Platform; Version control: Git, Helix Core, Mercurial, Perforce, Subversion; File sharing: ShareFile. The categories are ours (production filters by product, which no longer fits the line-up); Visual Studio sits under code hosting until product confirms what it connects to (see its page). Each card shows production's method label. Production's search box is left out: no kit component, and 24 cards fit on one screen.

All integrations

Find your platform.

Each integration page shows how it connects, what it deposits and the setup steps.

Amazon CodeCommit logoAmazon CodeCommitCustom integration Amazon S3 logoAmazon S3Custom integration Assembla logoAssemblaAdvanced integration Azure logoAzureOAuth integration Azure DevOps logoAzure DevOpsOAuth integration Beanstalk logoBeanstalkCustom integration Bitbucket logoBitbucketOAuth integration Bitbucket Server logoBitbucket ServerCustom integration CloudForge logoCloudForgeAdvanced integration Codebase logoCodebaseAdvanced integration Git logoGitAdvanced integration GitHub logoGitHubOAuth integration GitHub Enterprise logoGitHub EnterpriseCustom integration GitLab logoGitLabOAuth integration GitLab Self-Managed logoGitLab Self-ManagedCustom integration Google Cloud Platform logoGoogle Cloud PlatformOAuth integration Helix Core logoHelix CoreAdvanced integration Mercurial logoMercurialAdvanced integration Perforce logoPerforceAdvanced integration ProjectLocker logoProjectLockerAdvanced integration RepositoryHosting logoRepositoryHostingAdvanced integration ShareFile logoShareFileManual integration Subversion logoSubversionAdvanced integration Visual Studio logoVisual StudioAdvanced integration

Not listed? Use Secure Upload, or ask us.

Step 3, the model, from the deposit's side. The steps follow production's deposit video guide ("How to Deposit Your Assets Into Escrow", 2:02): deposits open once the agreement is signed; there are three deposit methods (OAuth Deposit, Custom Deposit and Secure Upload); you pick each repository from a list; "OAuth and Custom Deposits allows for daily update checks". The film is the existing production video, loaded only when played: it shows the old UI and says "escrow" throughout, so replace it when the new UI ships. The four method cards use production's labels and counts (6 OAuth, 6 Custom, 11 Advanced, 1 Manual). Advanced: production sells an "Advanced Integrations Add-On" but its FAQ says integrations cost nothing extra, and the October list has no such add-on; no price is stated here until that's settled. Daily sync stays flagged ⚑.

How deposits work

From your platform to the vault.

1

Activate the protection

Deposits open once the protection is active. For Escrow, that's when every party has signed the agreement.

2

Connect a platform

Activate its integration in the Codekeeper app and follow the steps on its page here.

3

Choose what to deposit

Pick each repository or asset from the list, and repeat for everything the deposit needs.

4

Keep it current

Connected platforms are checked for changes daily. Every protection then gets an automated check and a Software Resilience Certificate.

OAuth integration

You authorise Codekeeper in the platform, which issues an access token. No password is shared. 6 platforms, including GitHub and GitLab.

Custom integration

You create dedicated access in the platform, such as an IAM user, an access token or an app password, and enter it in Codekeeper once. 6 platforms.

Advanced integration

You sign in to the platform and authorise Codekeeper through its own access controls. 11 platforms, from Assembla to Subversion.

Manual upload

Upload through a secure ShareFile folder, or with Secure Upload in the app. Nothing to connect; the deposit updates when you upload.

Nobody leaves because their platform isn't listed. Production: "Can't find your preferred platform? We can add it for you!" and, in its FAQ, "send us an email at contact@codekeeper.co and we'll look into a solution for you". "We can add it for you" reads as a promise, so the card says we'll look at it. The deposit video guide also mentions requesting "a custom integration build"; that isn't stated here until product confirms it's offered. Two buttons, in the agreed order of weight.

Don't see yours?

Upload it, or ask us.

Every protection also takes manual uploads, for anything we don't connect to.

Use Secure Upload

Upload files straight to your deposit from the Codekeeper app. They're encrypted and checked like any other deposit.

Tech team briefing

Ask us about your platform

Tell us what you use at contact@codekeeper.co and we'll look at the options with you.

Talk it through

Not sure what to connect, or what the deposit should hold? We'll go through your stack on a demo.

Book a demo
The secondary conversion, on every page. Visitors who aren't ready to talk can still leave their email. The sample evidence pack is the same offer on every page, so the site has one lead magnet instead of a different e-book per page. It also carries the launch story: proof, not promises. The button goes to the sample evidence pack page.

Sample evidence pack

See what your auditor would receive.

An anonymised set of outputs from a real Agentic Verification run, so you can judge the evidence before you talk to us.

  • Recoverability Certificate
  • Run report
  • SBOM and Exit workbook excerpts
Get the sample evidence pack
Production's FAQ, kept where it's still true. Production asks eight questions. Kept and reworded: which platforms, automation, security, setup, new integrations. "Which platforms" now says 24 (see the hero note). "Encrypted and fully automated" becomes the confirmed facts (TLS in transit, AES-256 at rest). "Access to your code is restricted to authorized users only" is kept as production's claim in softer words; confirm with security. Dropped: the cost answer ("no additional cost"), because production also sells an Advanced Integrations add-on; and "Is there someone I can speak to?", which the final CTA answers. "No per-deposit fees" is a production claim still open in to-confirm.md, so it's flagged ⚑ like the daily sync.

Questions

About integrations.

Which platforms does Codekeeper connect to?

The platforms above each have their own setup page, and Secure Upload covers anything else. If yours isn't listed, email contact@codekeeper.co and we'll look at it with you.

Are integrations automatic?

Yes. Once connected, OAuth, Custom and Advanced integrations check for changes daily and keep the deposit in step, with no per-deposit fees. ShareFile and Secure Upload are manual: the deposit updates when you upload.

Does connecting a platform put our code at risk?

Access is granted the platform's own way: an OAuth token, or access you create, such as an IAM user, an access token or an app password. Traffic is encrypted in transit with TLS, deposits are encrypted at rest with AES-256, and only authorised users can reach them. Codekeeper is ISO/IEC 27001:2022 certified; see the Trust Center.

How do we set an integration up?

Once your protection is set up, the Codekeeper app guides you through activating the integration. Each integration page here shows the same steps.

Do you add new integrations?

We review requests for new platforms. Tell us which one you use at contact@codekeeper.co.

The same close on every page. The hub closes on the reason integrations exist: recovery starts from a deposit that matches what you run. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Connect once. Recover from what you run.

Book a demo and we'll look at your platforms with you. Not ready to talk? See the evidence a rebuild produces.

Book a demoGet the sample evidence pack
Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.