How trusted builds and releases work
Follow source from an approved snapshot to a verifiable production release.
Last updated 2026-09-02
What you'll achieve
- Trace source to production
- Distinguish preview from release
- Recover from a failed release
From source to artifact
BlinkHost binds a build to an exact source snapshot, reviewed application manifest, dependency root and versioned runtime image. Reproducible dependency evidence, policy checks and artifact digests are recorded before an artifact can become release evidence.
Release safety
A production release references an immutable artifact rather than a mutable working directory. Protected-environment approvals and workspace roles are evaluated before activation. If preparation fails, existing production traffic stays on the previous active release. Rollback selects earlier verified evidence; it does not rebuild unknown source.
What to inspect
Use the deployment detail page or CLI to inspect the source identity, artifact digest, status, runtime resources and failure code. A successful browser preview is development feedback, not proof that a production release was activated.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.