🌼 daisybee
HomeSample PDFCreate · £5
Evidence for software releases

Prove exactly
which build shipped.

A release tag tells people what you intended to publish. Daisybee gives you a portable cryptographic record of the actual folder you shipped — without uploading the release files.

Create Evidence Certificate · £5 ↗View sample PDF ↗
Files stay on your deviceFull local receiptPublic verificationOptional Bitcoin/OpenTimestamps proof
Use cases

What can you seal?

📦

Desktop / mobile build

Seal the distributable folder, installer bundle or packaged release.

🎮

Game release

Record the exact build sent to a store, tester, publisher or customer.

🧩

Plugin / package

Keep evidence for a versioned plugin, library, model bundle or downloadable tool.

How it works

A record you can verify later.

1

Hash locally

Your browser calculates SHA-256 for every file and builds a deterministic Merkle root.

2

Record one root

Daisybee commits the compact root; filenames and individual hashes are not published.

3

Keep portable evidence

Download the full receipt, PDF certificate and evidence bundle and verify again later.

£5

One release. One Evidence Certificate. Verification remains free.

Create certificate ↗
What you receive

Evidence package.

Local receipt with paths, sizes and SHA-256 hashes.

Merkle commitment recorded on Daisybee Gardennet.

PDF certificate with certificate ID and QR verification link.

Privacy-safe public verification record.

Evidence ZIP plus optional OpenTimestamps proof.

Important limit

Proof, not a legal verdict.

A Daisybee Evidence Certificate is cryptographic evidence that a particular commitment was recorded. By itself it does not establish legal authorship, copyright ownership or entitlement to a work. Keep your full receipt and original files.

Gardennet is experimental and resettable. The portable receipt and optional Bitcoin/OpenTimestamps path are designed to make the evidence useful beyond a screenshot of one private database.

FAQ

Before you buy.

Does this replace Git tags or signed releases?

No. It is designed to complement existing provenance tools, especially for finished folders and bundles.

Do I upload my binary or source code?

No. File hashing happens in your browser; the server receives compact release metadata and the Merkle root.

Can someone verify it later?

Yes. With the original release folder and full receipt, the Merkle root can be rebuilt and checked.