Codekeeper Transaction services
Book a demo Start a deal
How it works

One deal object. Every party in the room.

From the first invite to the 3-year evidence tail — here is what actually happens in a deal, step by step. One side buys, the other is invited free.

Start a deal See the report design
Project Meridian · Tech data room
Live sync on
Repositories 23 connected via GitHub · synced 14 min ago Live sync
Databases 4 schemas · fingerprinted on connect Validated
Infrastructure / IaC Terraform · 3 environments mapped Live sync
Contracts & licenses 61 agreements · classified and parsed Validated
Credentials 17 secure references · never plaintext Referenced
Domains 9 domains · registrar records attached Validated
Readiness score 92 / 100 · scannable
The walkthrough

A deal, start to finish.

01

Invite the counterparty — free

Start

One side buys the package; the other joins by magic link with no seat fees. Counsel, advisors, and investors join with role-scoped access — each party sees exactly what their role and the deal stage permit.

02

Guided onboarding

Pre-scan

The seller is walked asset-type by asset-type with per-type validators. Connectors link git hosts, cloud, and registries directly — a typical seller reaches a scannable room in under a day.

03

The room goes live — and stays live

In-deal

Connectors keep the room synchronized with the source platforms for the whole deal. Every change lands as a new immutable version and triggers a delta scan. No stale materials, ever.

04

Reports, at the tier the deal demands

In-deal

Automated Scan Report in 72 hours; analyst verification in about a week; expert deep-dive in about two. Every claim links to evidence, and every section states its coverage.

05

Q&A and finding resolution

In-deal

Diligence questions live next to the material they reference. Both sides respond in-app, remediations are verified by the next delta scan, and the audit trail records everything.

06

Escrow with release conditions

In-deal

Neutral custody of deal materials with conditions configured per deal — closing confirmation, dual sign-off, or date-based. Verification tiers prove the deposit builds or deploys.

07

Closing: the sealed IP Package

Closing

A mandatory full scan gates closing. Code, chain-of-title evidence, license manifest, executed transfer agreements, and asset schedules are sealed into one independently stored package.

08

Structured handover

Post-close

Checklist-driven transfer of every asset — repos, domains, credentials, cloud accounts, contracts — with per-item verification and dual sign-off. No more email checklists.

09

The 3-year evidence tail

Post-close

The R&W evidence vault retains the sealed record of what was represented at closing. Escrow converts to a standard Codekeeper subscription in one click.

Guided onboarding

A scannable room in a day.

Structure in, automation out. The wizard walks the seller asset-type by asset-type — repositories, infrastructure, contracts, licenses, credentials, documentation — and validates every material before it counts as "in the room." Wherever a connector exists, onboarding connects instead of uploads. That's also what makes the room dynamic.

The readiness score doubles as progress: sellers see exactly what's missing for a full-coverage report, and buyers see coverage transparency printed in the report itself.

Per-type validators
Format, completeness, and readability checked at upload or connect time — before anything counts as "in the room."
Connector-first
Git hosts, cloud providers, and package registries connect rather than upload — the same connectors that keep the room live.
Normalization on ingest
Agreements are parsed and classified, repos fingerprinted, manifests extracted — clean input for every downstream scanner.
Readiness score as progress
The same score used in deal-readiness mode — visible to the seller as a to-do list and to the buyer as coverage.
High LIC-02 · AGPL-3.0 dependency in the billing service
Evidence: SBOM entry · billing/package.json:41 · scan of 12 Aug, 09:14 UTC
Buyer · Meridian Capital
Is this dependency load-bearing, or can it be replaced before closing?
Seller · Northlight Systems
Replaceable — swap to a MIT-licensed alternative is scheduled this sprint. Will re-scan after merge.
Delta scan on next sync will verify the remediation automatically.
Findings, not PDFs

Questions live next to the material they reference.

Every finding links to its evidence, and both sides respond in-thread — a resolution workflow, not a static report. When the seller remediates, the next delta scan verifies it and the finding closes itself. The audit trail records all of it.

Invite the other side. We'll handle the room.

Scannable room in a day. Automated report in 72 hours. Sealed IP Package at closing.

Start a deal Book a fund demo