Check release status feature by feature

LaunchDarkly introduced Release Autopilot in a November 4 announcement, positioning it as automation for controlling how deployed changes reach users. The company promotes trial access now but gives November 16 as the planned general-availability date. Teams should distinguish an evaluation from a completed rollout.

The pricing comparison marks change classification, automatic flag insertion and automatic archival as beta. Other release functions appear separately in the plan table. A single product announcement therefore does not establish the same release status or terms for every step of the workflow.

Automation still needs a release policy

The product page describes a GitHub app that assesses pull requests and recommends flags and release plans. Engineers can review those recommendations before flags are added. Repository settings determine which projects use the automation, while release plans specify environments, approvals and deployment signals.

LaunchDarkly says guarded releases monitor selected metrics and can roll back when a regression is detected; a notification-only mode is also described. CGH’s assessment is that choosing meaningful metrics and approval boundaries remains an engineering decision. Automatic rollback cannot measure an important failure that the team has not represented in its guardrails.

Budget beyond the initial evaluation

The current plan table lists limited free access for Developer customers and says the listed Foundation release-management capabilities are free until February 2027. It does not establish an unlimited, permanently free Release Autopilot service. Model-provider keys or LaunchDarkly inference may be used where supported, so teams should confirm inference costs and account eligibility before enabling automation.

The reviewed materials do not specify country-by-country availability or a precise launch time. They also describe Release Autopilot as working alongside existing deployment pipelines. CGH reviewed public issuer information without connecting a repository, running a release or independently verifying the company's performance claims.