Releases & Feature Flags
Bundle features into named releases, draft release notes with AI, and optionally require every shippable surface to sit behind a feature flag.
A release is a named bundle of features that ships together, such as v2.3.0 or a themed launch. Releases are separate from cycles: features land in your main branch when their cycle's pull request merges, and a release can ship once all its features have merged.
Feature flag governance is an optional layer on top, for teams that want every new surface gated or explicitly exempted.
Create a Release
Assign Features
Draft Release Notes
Ship
Flag governance is set at organisation level and is off by default:
No flag registry or scanning.
Flag decisions are encouraged but not enforced.
Every feature must be flagged, unflagged with an audited exemption reason, or marked as a migration.
When a policy is enabled, Bynary:
Generates a typed flag registry file in your repository.
Scans committed code for ungated routes and pages and shows violations on the build dashboard.
Checks flag hygiene during review.
Tracks flags through rollout, soak, live and cleanup.
Do I have to use releases?
No. Cycles create pull requests whether or not their features belong to a release.
Does Bynary deploy my release to production?
No. Bynary stops at preview. Your own pipeline takes merged code to production.
Do I need a third-party flag provider?
No. Flags are managed in Bynary and in the generated registry. Third-party providers are not currently integrated.