1) The digital backbone of your organisation

CI/CD pipelines, container orchestration, identity & access management, observability, iPaaS, ETL — every component influences your uptime. But so do domain registrations, DNS routing, SSL certificates, and registry dependencies. If your domain or TLD service becomes inaccessible, your entire digital presence can disappear instantly.

With Software Escrow, you safeguard source code, build scripts, Infrastructure-as-Code (e.g., Terraform), deployment guides, and operational runbooks.

With SaaS Escrow, you secure service continuity — including payment fallback arrangements to cloud providers and access to administrative environments.

With Data Escrow, you protect datasets and schemas that fall outside your direct control, such as multi-tenant SaaS data.

With Domain & TLD Escrow, you safeguard:

• Domain registration data and transfer authorisation codes

• DNS zone files and routing configurations

• Registrar credentials (secured and controlled)

• Registry-level data escrow arrangements (where applicable)

• Procedures to transfer or restore domain control

This ensures that your organisation retains control over its digital identity and online availability — even in cases of registrar failure, dispute, insolvency, or operational blockage.

The result: your platform — including its public access layer — remains operable, even if a vendor, integrator, registrar, or service provider drops out.

2) Continuity & risk mitigation

Incidents cost money and trust. With an escrow arrangement in place, critical materials — source code, containers, configurations, documentation, and domain control assets — can be released in a controlled and contractually defined manner during a major incident. Internal or external engineers can then restore services, re-establish DNS control, and reduce MTTD/MTTR, protecting SLA commitments.

Typical scenarios include:

• Vendor ceases operations or is acquired

• Subscription or contract conflict threatens system or domain access

• Registrar failure impacting domain availability

• Critical proprietary component requires internal patching

• Cloud tenant suspension or account lockout

Escrow ensures you are not dependent on a single external party for operational continuity.

3) IP protection and custom software

Using custom modules, integrations, or proprietary frameworks? Escrow records rights and access clearly: the developer keeps the intellectual property; you gain guaranteed access when needed. This combines innovation with control and prevents “hard” rewrites under time pressure.

4) Compliance & standards (NIS2, ISO 27001, SOC 2)

Escrow provides demonstrable support for business continuity management and information security controls. It strengthens evidence for:

• Supplier risk management

• Change and release governance

• Recovery and fallback procedures

• Digital resilience planning

• Domain and infrastructure dependency controls

Verification reports and update logs can support audits under NIS2, ISO 27001, SOC 2, and other regulatory frameworks.

5) What we safeguard

• Source code (repos, tags, build instructions), dependencies, licenses

• CI/CD pipelines, IaC, secrets‑rotation processes (excluding production secrets)

• Runbooks, SRE procedures, on‑call routes, RTO/RPO assumptions

• Multi‑cloud/region information and fallbacks for PaaS/SaaS components

• Data models, schemas, migrations, and test data

6) Verification & updates (Active Escrow)

We verify periodically. Examples include:

• VerifOne – integrity check of the deposit

• VerifTwo – build/compile/test in the current environment

• VerifThree – clean‑room rebuild + installation + functional smoke tests

This ensures you don’t face surprises for the first time during an incident.

7) IT procurement checklist

• Is access to source code, IaC, and runbooks contractually secured?

• Is there a payment fallback to cloud providers?

• Are verification frequency and release criteria clearly defined?

• Does the arrangement align with your RTO/RPO and BCM plans?