Vendor onboarding
Castler establishes the agreement when the vendor contract is signed, not after go-live.
SOFTWARE ESCROW AGREEMENT
Castler sets up your software escrow contract when the vendor contract is signed: one executed agreement between the vendor, the beneficiary and Castler, and a deposit that stays current through every release.
Tripartite agreement
Software escrow agreement
Software vendor
Depositor
Enterprise
Beneficiary
Castler
Escrow agent
Agreed clauses
First deposit pending
Before the application becomes a live dependency
Illustrative interface
Clause
What it covers
What to check
Parties
The vendor, the beneficiary and Castler as escrow agent, bound by one executed agreement with defined obligations
Is the escrow agent a party, not only a storage provider?
Deposit materials
Source code, build inputs, runtime configuration, documentation and release history
Is the list specific enough to rebuild the software?
Deposit schedule
Every release captured from the vendor's repositories, with the schedule kept in the agreement record
Does the deposit follow production releases?
Storage
Encrypted custody in the agreed cloud region, or a physical vault in Delhi, Mumbai or Bangalore for India customers
Does the region meet your residency needs?
Access
Named parties get only the permissions the agreement gives them, and every action is logged
Who can see or request the deposit?
Release conditions
The trigger events you negotiate, with the release process defined in advance
Does it name every event you would act on?
Changes
Custom clauses, obligations and amendments handled in one record and signed digitally
Who approves a change?
Castler lists insolvency, acquisition, discontinuation and support failure as trigger events, plus any other condition you negotiate. The agreement then defines the steps that follow:
Declaration of the trigger
Notification to the parties
Evidence
Approvals
Controlled release of the deposit
Castler establishes the agreement when the vendor contract is signed, not after go-live.
Captured before the application becomes a live dependency.
GitHub, GitLab, Bitbucket, Azure DevOps or private Git feeds the deposit. Each version records its timestamp, commit hash, release identifier, depositor and source repository.
The release process in your agreement runs.
Ask these before you sign any software escrow agreement:
Question
How Castler answers it
Is the escrow agent a party to the agreement?
Yes. Castler signs as escrow agent, with defined obligations.
Are the release conditions specific?
Insolvency, acquisition, discontinuation, support failure and other negotiated conditions are written in.
Does the deposit follow production?
Repository integrations capture every release, so nothing is re-filed by hand.
Is the escrow in place before go-live?
Castler sets it up at vendor onboarding.
Can the deposit be rebuilt and run?
Optional. Castler Software Recoverability rebuilds and deploys the deposit, and a named engineer signs a Proof of Recovery.
Castler's escrow agreement software manages the whole agreement in one operating record:
Agreement record
Standard templates and custom clauses
Digital signing
Obligations and deposit schedules
Agreement changes
An audit trail of who deposited what and when
Source code or software escrow for critical applications, including updates and programme fixes
Source-code access or escrow for critical software used by non-bank payment system operators
Escrow and continuity controls for critical third-party applications
Software escrow and source-code availability for critical insurance applications
Updates and fixes belong in the agreement, and repository capture keeps them in the deposit. An agreement can satisfy the contractual custody element. Regulators now also ask for proof of recovery.
Installed software uses a code escrow agreement. Other assets use another escrow type:
A software escrow agreement gives you the legal right to the deposit. Castler Software Recoverability then adds the proof that the deposit can be rebuilt and run, using the agreement and deposit you already hold. Custody starts at $2,000 per application per year.
FAQ
Yes. The vendor, the enterprise beneficiary and Castler as escrow agent sign one agreement.
Yes. Castler manages standard templates and custom clauses in your software escrow contract.
Repository integrations capture every release, and each version is kept with its commit hash and release identifier.
In the cloud region in your agreement, subject to availability. India customers can also choose a physical vault in Delhi, Mumbai or Bangalore.
It can satisfy the contractual custody element. Many frameworks also expect recovery evidence, so Castler adds a signed Proof of Recovery on top.
SOFTWARE ESCROW AGREEMENT
Book a 15-min Demo. We will map your critical vendors, walk through the clauses and show you how the agreement is managed.
Book a 15-min Demo