NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
Why the video hub changed. Production's /video-guides lists 11 films with filters named after the old products (Software, SaaS, AI and Continuity Escrow) and three learning paths. Most of those films were made for the previous line-up. This rebuild separates them honestly: the films that still explain things well, the October launch films (which production's hub doesn't show at all), and an archive of films made for the earlier line-up, marked as such.
  • 15 production URLs: 11 films, 3 learning paths and 1 duplicate. /video-guides/how-to-guarantee-software-continuity serves the same film as /video-guides/how-to-build-software-resilience (its canonical points there). Redirect it, not least because of "guarantee" in the URL.
  • The learning-path pages render "Loading..." as their H1 in the capture; check they work without JavaScript.
  • The film pages aren't rebuilt here (see templates/REWRITE-GUIDE.md), except "What is software escrow?", which another writer is building as the template example.
Video guides

See how it works. In a few minutes.

Short films on what escrow is, how agreements and deposits work, and how to set things up in the Codekeeper app, plus the films on our October line-up.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • Films from one to five minutes
One film to start with. "What Is Software Escrow?" (2:09, YouTube fWni8qOcWTA) is the entry point most visitors need, and its page is being rebuilt as the template for the other film pages. It loads from youtube-nocookie only when played. Two lines in the film conflict with the brief: "encrypted and secured in military-grade vaults" (MESSAGING §5 bans "military-grade") and "frameworks like DORA, NIS2, and ISO standards all recognize software escrow as essential protection" (unsourced, and a compliance claim). Re-cut those two lines, or replace the film, before launch. It never mentions Validated, Verified or Certified.

Start here

What is software escrow?

Two minutes on how escrow works: you agree what's deposited and when it's released, the vendor deposits, and a neutral party holds it until a release condition is met.

  • Who's involved: the vendor, the customer and the escrow agent
  • What a release condition is, with common examples
  • What the customer can do after a release
The October films, which production's hub doesn't list. The five launch films exist (MESSAGING §10) and play on their product pages, so each card links to the page where the film sits rather than embedding it twice. Posters are the kit's own files. Upload them to YouTube as well if the team wants them here as guides. 16 Oct: Continuity Pro added; base Continuity is everything in Resilience, without Agentic Verification, so the Continuity card now says "Everything in Resilience". 18 Oct: the four solution films (Escrow, Resilience, Continuity, Agentic Verification) are re-made in the launch film's style, with the same file names and new posters; the Continuity film now shows rebuilds for Continuity Pro only.
The production films that still explain things well, and the learning paths. Cards link to production's film pages. Each film was reviewed against its transcript:
  • What is a software escrow agreement? (1:42): "Our data centers ensure the highest level of security" is an absolute; otherwise sound.
  • What is SaaS escrow? (2:57): "you never lose service" and "regulators under DORA, NIS2, and ISO frameworks specifically require documented continuity measures" conflict with the brief. Re-cut, or replace with the suggested "SaaS: what we deposit" film.
  • What is AI escrow? (3:34): describes "verification testing" that "rebuilds your complete environment" and handing "Software Resilience Certificates… to regulators as proof"; names OpenAI, Anthropic, Google, AWS Bedrock, Azure OpenAI, LangChain, Make and n8n; says DORA and NIS2 "require documented AI continuity measures". Re-cut or replace.
  • How to configure a software escrow agreement (2:36) and How to deposit your assets (2:02): old UI; the first sets an "escrow agreement liability SLA", an add-on that isn't in the October list. Re-shoot when the new UI ships.
  • Learning paths: "Getting started" opens with the old-model film "How to Build Bulletproof Software Resilience"; "Ensuring continuity" holds two old-model films and promises "uninterrupted software availability". Rebuild the paths around the October films. Fact-check, 7 Oct: the "Ensuring continuity" card said a hosted service is "kept available"; it now uses the agreed wording ("kept paid and switched on for an agreed period").
Filters replace production's product-name filters (Software, SaaS, AI and Continuity Escrow) with what the film does.

Video guides

Explainers, how-tos and learning paths.

The page-specific offer on educational pages. Agreed 7 Oct: on explainers, video guides, magazine articles and role briefings, the mid-page offer is the matching guide instead of the sample evidence pack. Visitors who are still learning convert better on a guide about their question. The hero and closing section still carry Book a demo and Get the sample evidence pack. Guide source on production: the "resources-intro-to-software-escrow" item on /resources. Before launch: update the guide itself to the October line-up (it still uses the old product names and verification tiers) and connect this form to the HubSpot form that sends it. The video hub's audience is still learning what escrow is, so the introduction guide is the natural next step after a film.
Introduction to Software Escrow

Free guide

Introduction to Software Escrow

What software escrow is, what it protects you from, and how automatic deposits keep it current.

  • What a deposit holds and who can claim it
  • How release works when a vendor fails
  • Setting up deposits that update themselves
Enter your work email.
Enter your company.

Check your inbox.

The guide is on its way. (Example only: this kit sends nothing.)

Old-model films, kept findable but marked. These five were made for the previous line-up. Visitors and existing customers still search for them, so they stay listed, labelled "Earlier line-up", with a line on what has changed. Naming "Continuity Escrow" here is deliberate, as on the FAQ's existing-customers answers. Each conflicts with the brief:
  • How to Build Bulletproof Software Resilience (5:00): Software, SaaS, AI and Continuity Escrow; verification "as an add-on" with "certified proof"; Continuity Escrow "we take over payments… you never go offline"; "We protect your software so it never fails you". Shown here as "How to build software resilience", its URL and page title, because "bulletproof" is banned.
  • What Is Continuity Escrow? (3:20): "guarantee continuity", coverage "for three months as standard, or up to twelve months", the Validated, Verified and Certified tiers, "you never go offline" and "with Continuity Escrow you can meet them all" (DORA, NIS2, CPS 230). Replace with the Continuity film.
  • How to configure SaaS escrow (2:04): the "Continuity Protection Period" and "we will make payments on your behalf", from the earlier SaaS model.
  • An introduction to Codekeeper (1:45): "best prices guaranteed", "a potential saving of up to eighty percent", "release procedures are processed 24/7", "double-encrypted", "No lawyer required".
  • All new online platform (1:23): the V4 app launch, "the best prices guaranteed".
Recommendation: unpublish the last two now, and replace the first three as the suggested films are made. 16 Oct: Continuity Pro added; the Continuity Escrow card now says base Continuity is everything in Resilience, and Continuity Pro adds Agentic Verification.
The films to make next, from the video plan (MESSAGING §10). Each one replaces an archived film or fills a gap the guides can't. Shown as placeholders with a script outline; remove this section, or keep it hidden, before launch. Not listed: "Meet the team", which belongs on About and Book a demo.

Coming next

Films we're planning.

Suggested filmWhat happens on release dayAbout 60 seconds

A release condition is raised; legal review; the condition is verified; the beneficiary is authenticated; access to the deposit. Close on the two-to-three-hours line only if operations confirm it.

Suggested filmInside an Exit ExerciseAbout 75 seconds

Scoping, the clean-room rebuild from the deposit alone, functional tests of the business functions you nominate, the Tested Exit Report. No duration on screen.

Suggested filmSaaS: what we depositAbout 45 seconds

Code, infrastructure-as-code, data exports, credentials and the third-party services the application needs. Replaces "How to configure SaaS escrow".

Suggested filmAI: what we depositAbout 45 seconds

Models, weights, prompts, pipelines and vector stores, with no third-party product names on screen.

Suggested filmBackup in 60 secondsAbout 60 seconds

Connect, sync, restore: your own systems backed up and restorable from the dashboard.

Suggested filmA regulated customer's storyAbout 90 seconds

A named customer on what the certificate did in an audit. Needs a customer who agrees to be named.

The same close on every page. The video hub closes on the same two actions as every page, after visitors have seen how it works. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Seen enough? See it on your own software.

Book a demo and we'll walk through the applications you rely on. Not ready to talk? The sample evidence pack shows the proof first.

Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.