🌼 daisybeeRelease Challenge
Daisybee · Independent Challenge

You shipped it.
Daisybee tries to
reproduce it.

Your own machine can say a build is reproducible. Independent Challenge asks a harder question: can a Daisybee-controlled isolated worker rebuild the exact release from your declared source and recipe?

Independent Challenge · £59 ↗Start with free Preflight
1 · Create capsule locally
2 · Worker rebuilds offline
3 · Roots compared
4 · Worker signs result
Customer

Source + exact release

A local Challenge Capsule commits to your source tree, shipped release, build command and approved container image.

Daisybee worker

Isolated rebuild

No local fallback. The build runs in a fresh container with networking disabled, capabilities dropped and resource limits applied.

Portable result

Signed receipt

The worker compares Merkle roots, records divergence, and signs the receipt with its Ed25519 key for offline verification.

Independent Challenge
£59

One release. One independent rebuild.

Includes capsule validation, isolated rebuild, exact root comparison, changed-file diagnostics when possible, signed Independent receipt and HTML report.

Unlock Independent Challenge · £59 ↗
Why pay more than £19?

Because this run is not on your machine.

The £19 Full Challenge tests your build under controlled variations. The £59 tier moves the challenge onto Daisybee infrastructure and returns a worker-signed result.

Next: three independent workers agreeing on the same release root.

Important scope. A MATCH means the identified Daisybee worker reproduced the exact expected release root using the recorded capsule, command and container image. It does not prove that the software is secure, bug-free, non-malicious, authored by a particular person or legally owned. v0.17 is a single Daisybee worker result, not yet a multi-party witness result.