Prove delivery before the invoice dispute starts.
Show exactly what was delivered, and when, without exposing source code. Seal a milestone, repository tree or release artefact with a record the client can verify.
Evidence record
Software & Delivery
The problem
What makes this hard to prove today
Most evidence problems are not about whether a file exists. They are about whether you can show what it was, when it existed and that it has not changed since.
Git dates can be rewritten
Author and committer dates are easy to amend or rebase, so a commit history alone is weak proof of delivery.
Clients dispute the delivery date
A late-delivery claim can appear after the work is already in use, putting the final invoice at risk.
Code can be reused after rejection
Proving what was delivered helps when a client claims the work was built independently in-house.
Supply-chain artefacts need provenance
Binaries, SBOMs and vendor drops need a verifiable record of what was received and when.
What you get
An evidence pack you can actually use
IP Vault produces the sealed record. Your team keeps control of the files and decides who receives the verification link.
A timestamped delivery certificate
Seal the exact repository tree or deliverable before handover.
A manifest the client can check
File list, tree hash and AST metadata are captured in the record.
A public verification link
Attach it to the invoice or handover email so the client can check the record.
Release and SBOM attestations
Seal build artefacts or an SBOM without handing over the source.
How it works
Three steps, no new storage platform
Package the milestone
Select the repository archive, release artefact or deliverable that is being handed over.
Seal the delivery record
The files are hashed and the manifest is timestamped through both time anchors.
Send the link with the invoice
The client can verify the record while the code remains under your control.
Regulatory context
Built for software delivery and supply-chain evidence
IP Vault evidences delivery and integrity. It is not an escrow service and does not replace your contract, acceptance process or payment terms.
Who it is for
Built for teams that have to show their work
Common questions
The short answers
Do we have to upload our source code?
Can the client verify it?
Does it work with CI/CD?
Can we seal a release without revealing it?
Create the record now, decide who sees it later
Start with a single protection run. Keep the archive, share the verification link, and add revisions when the work changes.
Other solutions