The software runs but the data is gone
A rebuilt application cannot resume operations if transaction history, customer records, and risk data remain on inaccessible vendor systems.
DATA ESCROW
Software can be rebuilt from an escrow deposit. Data cannot be recreated from code. If a vendor holds your transactions, customer records, risk models, or operational dataset, Castler provides independent custody and a verified export path.
WHAT IT IS
Data escrow is an independent custody arrangement in which a vendor deposits operational data, or the pipelines and schemas required to produce a full export, with a neutral third party.
Data escrow is different from backup. Backup protects against corruption or infrastructure failure. Escrow protects the beneficiary against vendor failure, including scenarios where the vendor cannot or will not cooperate with extraction.
Verification confirms that every export is complete, structurally valid, readable, and loadable into a clean environment.
THE PROBLEM
A rebuilt application cannot resume operations if transaction history, customer records, and risk data remain on inaccessible vendor systems.
Proprietary formats, missing keys, unsupported database versions, or undocumented schemas can make a delivered export unusable.
Quarterly or annual exports can create an unacceptable operational gap for institutions processing continuous transactions.
THE CASTLER APPROACH
Castler validates the structure and usability of each data deposit, records the evidence, and aligns deposit frequency to the institution's recovery tolerance.
Open-format database exports
Schema definitions and version history
Data dictionary
Referential integrity maps
Export pipeline code
Transformation and ETL logic
Record counts and checksums
Partition and operational metadata
Agents validate record counts, referential integrity, schema alignment, and checksums. A sample load runs in a clean database environment on every deposit, with full load tests on an agreed schedule.
Signed integrity evidence for each deposit, with structural validation, load-test result, timestamp, version, and chain of custody. Deposits can run daily, weekly, or through incremental streaming custody.
REGULATORY MANDATE
EU DORA
Critical functions require data availability and recoverability controls for third-party ICT services.
Evidence mapEU NIS2
Essential and important entities must manage data integrity and availability risks involving third parties.
Evidence mapSEBI CSCRF
Market institutions must protect data availability and recovery for critical third-party systems.
Evidence mapISO 22301
Business continuity systems must identify and protect critical information assets held by third parties.
Evidence mapFREQUENTLY ASKED
Supported open formats include PostgreSQL, MySQL, and MSSQL dumps, Parquet, Avro, ORC, CSV with schema, JSON with schema, and XML. Proprietary formats require a documented conversion pipeline.
Yes. Incremental and delta deposits are available when daily full exports are impractical, while maintaining a reconstructable dataset in custody.
No. Backup is an internal operational control. Data escrow is an independent continuity right protecting against vendor failure. Both are required for different risks.
Yes. Data is encrypted in transit and at rest. Key custody and release controls are defined in the agreement and access is restricted to valid release conditions.
GET STARTED
A 15-minute briefing. We identify critical vendor-held data outside current escrow scope and map the recovery requirements that apply to your sector.
Book a 15-min briefing