Don't just attest
a release.
Challenge it.
Daisybee rebuilds your shipped software under deliberately changed conditions and compares every result with the exact release you published. If it diverges, Full Challenge tells you which files moved and what likely caused it.
We try to make your release claim fail.
Take the shipped build
Daisybee commits to the exact output folder with a deterministic manifest and Merkle root.
Rebuild under pressure
Fresh paths, timezones, locale, hostname variables, parallel settings and filesystem insertion order deliberately change.
Explain divergence
A failed build is useful: Full Challenge identifies changed files, differing bytes and challenge-specific values found in output.
Release Preflight
Three high-signal tests tell you whether reproducibility risk exists before you spend anything.
✓ baseline rebuild
✓ repeat/fresh-path build
✓ timezone/path perturbation
Download Preflight ↓Full Release Challenge
All seven challenge conditions plus exact changed-file diagnostics, divergence hints, Challenge receipt, badge and public verification.
✓ full challenge matrix
✓ exact changed files
✓ probable environment leaks
✓ container image/digest record
✓ portable Challenge ID
✓ verification badge
Diagnosis, not another badge.
| Free Preflight | Full Challenge | |
|---|---|---|
| Build tests | 3 | 7 |
| Risk detected | ✓ | ✓ |
| Exact changed files | — | ✓ |
| Challenge-value hints | — | ✓ |
| Portable Challenge receipt | basic | full |
| Shareable result badge | preflight | full |
| Offline public verifier | receipt integrity | receipt integrity |
Challenge evidence is not a security audit.
A passing Release Challenge means the declared build reproduced the exact shipped content under the challenge conditions recorded in the receipt. It does not prove that software is secure, bug-free, non-malicious, legally owned, or reproducible under conditions that were not tested.
Container mode disables networking during builds and records the declared image/digest. Independent third-party witnesses are a planned higher tier and should not be inferred from a local/container result.