CASTLER SRP · PRICING
Every tier includes the one before it, then adds one more layer of evidence. Nothing is removed as you step up. All prices are per application, per year.
Secure escrow custody and documentation with in-region cloud storage across AWS, Google Cloud Platform or Microsoft Azure, folder-structure inspection and a detailed deposit report. Answers: Do we have an escrow arrangement in place?
1 Application / Year
$1,000
Up to 10 Applications / Year
$5,000
More than 10 applications
Talk to UsEverything in Cloud Storage, plus service and infrastructure detection, compilation to a working executable with logs, SBOM and CBOM generation, one verification per year. Answers: Is the code we hold real, complete and buildable?
1 Application / Year
$2,500
Up to 10 Applications / Year
$10,000
More than 10 applications
Talk to UsEverything in Standard Verification, plus independent rebuild, deployment and run of the software, engineer-signed Proof of Recovery per verified release, subsequent verification on new releases, multi-location storage. Answers: If the vendor disappeared tomorrow, could we run the business on this?
1 Application / Year
$5,000
Up to 10 Applications / Year
$30,000
More than 10 applications
Talk to Us* Physical vault storage is available for customers in India
Prices are per application, per year. Each layer includes everything in the layer before it — nothing is removed as you step up. For estate and partner pricing, use the Talk to Us button on the relevant product.
WHAT'S INCLUDED
| Cumulative scope | Cloud StorageBase custody layer | Standard VerificationAll of Cloud Storage, plus: | Premium RecoverabilityRecommendedAll of Standard, plus: |
|---|---|---|---|
| Secure escrow custody and documentation — 1 application | Yes | Yes | Yes |
| Cloud storage (AWS / Google Cloud Platform / Microsoft Azure), data localised in-region | Yes | Yes | Yes |
| Folder-structure inspection and detailed deposit report [1] | Yes | Yes | Yes |
| Multi-location storage with auto-sync | — | — | Yes |
| Service and infrastructure detection report [2] | — | Yes | Yes |
| Source code compiled to an executable, with logs [3] | — | Yes | Yes |
| SBOM / CBOM generation — included by default [4] | — | Yes | Yes |
| Independent rebuild, deployment and run of the software [5] | — | — | Yes |
| Engineer-signed Proof of Recovery per verified release | — | — | Yes |
| Subsequent verification on a new release or code change [6] | — | — | Yes |
| Verifications included per year | None | 1 | 1 |
| Best suited for | Contractual cover | Audit evidence | Full continuity |
WHAT THE DIFFERENCE BUYS
CLOUD STORAGE
Answered. The deposit exists, is held securely in-region, and its structure has been checked on arrival. Nothing has been opened, built or run.
STANDARD VERIFICATION
Answered. The deposit has been inspected, its dependencies inventoried, and it has been compiled into a working executable with logs and a bill of materials.
PREMIUM RECOVERABILITY
Answered. Castler has independently rebuilt, deployed and run the software, and signed a Proof of Recovery.
WHAT LAYER 1 ALONE CANNOT TELL YOU
WHAT LAYER 2 ADDS ON TOP
Why it matters: This is the first point at which anyone independently tests whether the escrow would work. It converts a contractual promise into documented evidence — the form in which RBI, SEBI, IRDAI, DORA and FCA expect source-code arrangements to be demonstrated, not merely asserted.
WHY ‘IT COMPILES’ IS NOT ‘WE CAN OPERATE IT’
WHAT LAYER 3 ADDS ON TOP
Why it matters: At Standard Verification, recovery still begins with a discovery project — run during the outage, under pressure, with the vendor gone. At Premium Recoverability the path has already been walked once and documented. That is the difference between holding code and holding a business that can keep operating.
THE FAILURE-MODE MATRIX
Escrow arrangements rarely fail because the contract was wrong. They fail because the deposit was never tested, and the gap only surfaces at the moment of release.
| Failure mode at the moment of release | Cloud Storage | Standard Verification | Premium Recoverability |
|---|---|---|---|
| Deposit is corrupt, encrypted without keys, or unreadable | Detected | Detected | Detected |
| Repository incomplete — source files or modules missing | Partially detected | Detected | Detected |
| Dependencies undeclared, or held in private vendor repositories | Not detected | Detected | Detected |
| Source code does not compile; no usable build can be produced | Not detected | Detected | Detected |
| Build instructions absent, incomplete or incorrect | Not detected | Detected | Detected |
| Undisclosed third-party or open-source licence exposure | Not detected | Detected | Detected |
| Weak, deprecated or non-compliant cryptography in the stack | Not detected | Detected | Detected |
| Build succeeds but the application will not install or start | Not detected | Not detected | Detected |
| Environment and infrastructure configuration missing | Not detected | Not detected | Detected |
| Database schema, migrations or reference data missing | Not detected | Not detected | Detected |
| Hidden runtime dependency on a vendor-hosted service or licence key | Not detected | Not detected | Detected |
| No deployment path — the system has never been stood up by anyone but the vendor | Not detected | Not detected | Detected |
| Deposit silently goes stale after a mid-year vendor release | Not detected | Partially detected | Detected |
Cloud Storage
You are handed a deposit. Whether it is complete, buildable or operable is unknown until your team opens it. Discovery, gap analysis and remediation all begin from zero during the incident, with no one left to ask.
Standard Verification
You know the deposit is genuine and that it compiles. Environment configuration, deployment and data remain unsolved, so a live service still has to be engineered from a working build under time pressure.
Premium Recoverability
The rebuild has already been performed and signed off by a Castler engineer on an identifiable release. Recovery becomes the repetition of a documented procedure rather than an investigation.
Has anyone outside the vendor ever compiled and run the deposited code? If the answer is no, the arrangement has never been tested, and the first test will be the day it is needed.
WHAT YOU RECEIVE
Castler · Certificate of Recoverability
Aurora Core · Release 24.11.3
A. Mehta, Verification Engineer
castler.io/verify/POR-2026-04821
Engineer-sealed Certificate of Recoverability
HOW WE COMPARE
| Castler SRP | Escode | Vaultinum | Codekeeper | Escrow London | EscrowTech | PRAXIS | |
|---|---|---|---|---|---|---|---|
| Custody / Storage · annual pricing1 application / year | $1,000 | ~£1,600+ | ~€960–€1,320 | ~$1,668 | $1,895 | ~$2,590 | $5,500+ |
| Up to 10 applications / year | $5,000 | Quote only | Quote only | ~$16,680 | ~$18,950 | Quote only | ~$45,000+ |
| Verification / Recoverability · annual pricing1 application / year — full recoverability | $5,000 | Quote only | Quote only | Quote only | $9,000–$10,000 | Quote only | Quote only |
| Up to 10 applications / year | $30,000 | Not available | Not available | Not available | ~$90,000–$100,000 | Not available | Not available |
| AI-agent-led verification | Yes | No | No | No | No | No | No |
| Signed Proof of Recovery | Yes | No | No | No | No | No | No |
PRICING FAQ
Castler SRP is sold per application, per year. Choose Cloud Storage, Standard Verification, or Premium Recoverability, then select pricing for one application or up to 10 applications. Each product includes every layer before it, and the whole contract renews on one date.
Your subscription begins on the date payment is received. That is your contract start date, and your renewal date is exactly 12 months later regardless of when you deposit your first codebase. This keeps your renewal simple and predictable.
An application added during the contract year is covered until the shared contract end date, then renews with the rest of your subscription. If the additional application moves you beyond your current application band, the pricing team will confirm the required adjustment.
Yes. You can move from Cloud Storage to Standard Verification or Premium Recoverability during the contract year, or expand beyond your current application band. The pricing team will confirm the difference due, and your renewal date stays the same.
Each product answers one additional operational question. Cloud Storage confirms the arrangement exists. Standard Verification tests whether the deposit is complete and buildable. Premium Recoverability proves the software can be independently rebuilt, deployed and run. Nothing is removed as you step up.
No. Cloud Storage, Standard Verification and Premium Recoverability are cumulative product layers. Cloud Storage covers custody and deposit documentation. Standard Verification adds build verification, infrastructure detection, SBOM and CBOM. Premium Recoverability adds independent rebuild, deployment and engineer-signed Proof of Recovery.
Premium Recoverability is priced per application, per year: $5,000 for one application or $30,000 for up to 10 applications. Each application receives one full verification cycle per contract year, with subsequent verification available when a new release or material code change is submitted.
Every Cloud Storage deposit includes secure escrow custody and documentation, in-region cloud storage across AWS, Google Cloud Platform or Microsoft Azure, folder-structure inspection, and a detailed deposit report confirming the integrity of what was received.
No. There is no setup fee on any Castler SRP product. You pay the annual contract fee and onboarding begins immediately.
GET A WRITTEN QUOTE
Share your tier, application count, jurisdiction and verification cadence. This routes directly to the pricing team.