> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/feature-flag/feature-flags.md). # Feature Flag Introduction When you deploy code to the production environment, the associated feature immediately becomes visible to users.\ Using Feature Flags, you can separate deployment from release to manage the entire lifecycle of a feature. {% hint style="success" %} You can test features in the production environment by keeping them accessible only to designated individuals before showing them to all users. {% endhint %} ![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-1ef028684f834f9473928efee261a87e06c001b4%2F22eb818-Frame_18042_ade984031a63c1ce.png?alt=media) {% hint style="info" %} Feature Flags are for teams like these! * Product managers/PM/PO who want to release features gradually * QA teams who want to test in a specific environment before feature release * System administrators who want to manage and control system functionality by toggling specific features on and off {% endhint %} {% hint style="success" %} Feature Flags are most recommended for developers, but they are not for developers only. Many other roles can make broad use of them as well. {% endhint %} ### Use Cases


Release Management Learn what Feature Flags are and why you need them.	https://hackle.io/ko/post/intro-to-feature-flag-1/
Gradual Rollout Explore how Feature Flags are used and operated.	https://hackle.io/ko/post/intro-to-feature-flag-2/
System Stability Management Learn how to manage Feature Flags safely.	https://hackle.io/ko/post/intro-to-feature-flag-3/
System Impact Measurement Measure how a feature change affects your system.	https://hackle.io/ko/post/ff-system-impact-measurement/
Blue-Green Deployment See how to run blue-green deployments with Feature Flags.	https://hackle.io/ko/post/blue-green-with-ff/
Business Impact Measurement Check how a feature change affects your business metrics.	https://hackle.io/ko/post/ff-business-impact-measurement/
Beta Test Release a feature to a limited set of users and validate it.	https://hackle.io/ko/post/ff-beta-test/

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hackle.io/en/feature-flag/feature-flags.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.