Why this page looks like this. Production's /integrations/sharefile is a short template: the pill "MANUAL INTEGRATION", "Codekeeper x Sharefile", one security paragraph, setup steps with screenshots and a Secure Upload note, closing on "Let's build bulletproof software resilience together". This rebuild keeps every production specific (the method, the steps, the step screenshots, how access is granted) and adds what the template leaves out: why a current deposit matters when you need to recover, what the integration works with, and the next step.

The pair and the pill say what connects to what, and how, before anyone reads a word. The pill is production's label, word for word.
The mock shows ShareFile as a deposit source in the app, with the Software Resilience Certificate and, on a Pro level, a change flagged since the last rebuild (monitoring between runs). Example values and fictional names.
Logos: the ShareFile logo is production's file. Platform logos name the integration here; check ShareFile's brand guidelines before launch.
Integration count: production says "50+" (hub FAQ, product pages), but only 24 integration pages exist and its hub grid shows 41 cards (40 platforms). The kit keeps "50+" flagged everywhere and states no other count; reconcile the figure sitewide before launch.

MANUAL INTEGRATION

Codekeeper + ShareFile

Name an uploader and they get a secure ShareFile folder: what they upload goes straight into your deposit, so the version we hold can match the version you run.

Book a demo Get the sample evidence pack

Trusted by 3,500+ teams
ISO/IEC 27001:2022 certified
Uploads go straight into the deposit

Deposit sourcesFleet Ledger · Escrow ProActive

ShareFile folderManual integration · uploader invitedActive

release-2026-09.zipFile · uploaded to the folderDeposited

architecture-notes.pdfFile · uploaded to the folderDeposited

Software Resilience CertificateAutomated check passed · vault report attachedCurrent

Example values. Names are fictional.

The facts a technical buyer checks first. Method, deposit and steps are production's. "Daily" is production's sync claim (the deposit video guide says OAuth and Custom deposits get "daily update checks") and stays flagged ⚑ until product confirms it; ShareFile is manual and does not sync. "Works with": production offers integrations for every product family (Software, SaaS and Continuity Escrow and Software Backup); Resilience is new, so confirm deposits work the same way there.

At a glance

ShareFile and Codekeeper, in six facts.

Connection method: Manual integration, through a ShareFile folder
What it deposits: The files your nominated uploader puts in the ShareFile folder
How often it syncs: Whenever files are uploaded to the folder
Works with: Every protection: Escrow, Resilience, Continuity and Backup
Set up by: Whoever holds the code: usually the vendor's tech team, or yours for an in-house application
Also available: Secure Upload, in the Codekeeper app

Production's steps, reworded, with production's screenshots. Step order and content are production's (4 steps); the wording is tightened and "the necessary" becomes "listed in the in-app instructions", which production says hold the same steps. The screenshots are production files from the Codekeeper 2024 image set: old UI, replace when the new UI ships. I couldn't open them from the build environment, so check each still matches its step. Production spells it "Sharefile"; the product is ShareFile. The kit uses ShareFile (the footer already does). Production's meta description promises "automated escrow deposits" for ShareFile, but the page itself calls it a manual integration. The kit describes it as manual.

Set up

Connect ShareFile in four steps.

You'll find the same steps in the Codekeeper app when you activate the integration.

What you'll need

The email address of the person who will upload the files
An active protection in Codekeeper. For Escrow, deposits open once every party has signed the agreement.

Need a hand? Our technical specialists can walk you through setup and your first deposit. Email contact@codekeeper.co or contact support.

Activate the integration

In the Codekeeper app, select Activate on the ShareFile integration.

Name the uploader

Enter the email address of the person who will make the deposit.

They receive a folder invitation

That person is invited to a ShareFile folder set up for your deposit.

Upload to the folder

Files uploaded to the folder go into your deposit.

Say how access is granted, in plain words. Production's security paragraph for this page: "In partnership with Sharefile, a secure content collaboration and SFTP Platform, we facilitate secure file transfer for customers who prefer to manually push or upload material into escrow." The first card says the same thing plainly. The encryption card uses confirmed facts only (AES-256 at rest, TLS in transit), and ISO/IEC 27001:2022 is the only certification claimed: production's integrations hub also shows ISO 9001, 27017, 27018, SOC, PCI and CSA badges, which aren't confirmed. "Industry-standard technologies" and "multi-layered security" are dropped because they say nothing checkable. The mint strip is production's Secure Upload alternative ("Deposit your Sharefile assets manually with our Secure Upload feature"), with the trade-off production leaves out: an integration keeps the deposit current on its own, an upload doesn't. "Just upload your assets and we'll do the rest!" is dropped as vague, and so is the old-UI screenshot (deposit-assets.png). The button goes to the tech team briefing, which covers the deposit methods.

Security

How the connection stays secure.

A dedicated upload folder

We invite the person you name to a ShareFile folder. ShareFile is a secure file-sharing and SFTP platform, and what's uploaded there goes into your deposit.

Encrypted in transit and at rest

Traffic between ShareFile and Codekeeper is encrypted with TLS, and deposits are encrypted at rest with AES-256.

Certified security

Codekeeper is ISO/IEC 27001:2022 certified, audited by BSI. Policies and audit summaries are in the Trust Center.

Prefer to upload in the app? Use Secure Upload.

Upload files straight to your deposit from the Codekeeper app, with no folder invitation to manage. Either way, the deposit is encrypted and checked.

Read the tech team briefing

Step 4, the proof: connect the integration to recovery. Production says only "ensuring the most recent version is always ready for recovery". Readiness is shown, not implied: every protection includes an automated check and a Software Resilience Certificate; Escrow Pro, Resilience Pro and Continuity Pro add Agentic Verification (four rebuilds a year in the Codekeeper AI Verification Lab, a Recoverability Certificate) and monitoring between runs, which compares the deposit with the live repositories and flags what changed. All from MESSAGING §6. The daily sync stays flagged ⚑.

Why it matters

A current deposit is one you can recover from.

Recovery starts from what's in the deposit. Uploading to the ShareFile folder whenever the application changes means the version we hold is the version you run.

Updated with each upload

Each upload to the ShareFile folder goes into the deposit, so it holds what you last sent.

Checked and certified

Every protection includes an automated check of what's deposited, with a vault report and a Software Resilience Certificate.

Rebuilt to prove it

With Escrow Pro, Resilience Pro and Continuity Pro, Agentic Verification rebuilds the deposit in the Codekeeper AI Verification Lab, with four rebuilds a year that you start, and issues a Recoverability Certificate.

Changes flagged between runs

On those levels, we also compare the deposit with your live repositories and flag what changed, so you know when to rebuild.

How Agentic Verification works

Keep platform searchers moving. Integration pages are mostly reached from search ("ShareFile escrow", "ShareFile backup"), and production gives them nowhere to go but the demo button. Eight related integrations: other file sharing options come first, then the most-used integrations. Each card shows production's method label.

Related integrations

Codekeeper also connects with.

GitHubOAuth integration

GitLabOAuth integration

BitbucketOAuth integration

Azure DevOpsOAuth integration

GitHub EnterpriseCustom integration

GitLab Self-ManagedCustom integration

Bitbucket ServerCustom integration

Amazon CodeCommitCustom integration

More integrations, plus Secure Upload for anything else. See all integrations

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

The questions a tech lead asks before connecting. Answers come from production's integrations hub FAQ, the deposit video guide ("OAuth and Custom Deposits allows for daily update checks"; "choose the desired asset… repeat this process") and the kit FAQ ("Deposits open once the agreement is signed"; "no per-deposit fees", flagged in to-confirm). There's no cost question on purpose: production says integrations carry "no additional cost" while also selling an Advanced Integrations add-on. Confirm, then add the answer.

Questions

Before you connect ShareFile.

How often does the deposit update?

Whenever files are uploaded to the ShareFile folder: each upload goes into the deposit. Nothing syncs automatically, so plan an upload whenever the application changes, or connect the platform that hosts the code instead.

What exactly gets deposited?

The files your nominated uploader puts in the ShareFile folder. Each upload adds to the deposit, so upload everything the deposit needs. The agreement lists what should be deposited, and the automated check confirms what's there.

Who can upload?

The person whose email address you enter when you activate the integration. They receive an invitation to the ShareFile folder, and what they upload goes into the deposit.

When can we start depositing?

As soon as the protection is active. For Escrow, deposits open once every party has signed the agreement.

Does uploading through ShareFile prove we could recover?

It gets the files into the deposit, which is where any recovery starts. The proof comes from the automated check and the Software Resilience Certificate, and with Escrow Pro, Resilience Pro or Continuity Pro, from Agentic Verification: a rebuild in the Codekeeper AI Verification Lab and a Recoverability Certificate.

The same close on every page. Integration pages close on the same two actions as every page. Visitors who arrive from a platform search see the whole story only if they're invited to take the next step. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Keep your ShareFile deposit ready to recover.

Book a demo and we'll walk through the connection with you. Not ready to talk? See the evidence a rebuild produces.

Book a demo Get the sample evidence pack