> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fujiflag.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fujiflag.com/_mcp/server.

# FujiFlag Documentation

> Ship safely with feature flags, environment values, experiments, and surveys.

# FujiFlag Documentation

FujiFlag lets your team separate deploying code from releasing it. Create a
feature flag, choose its value for each environment, and read that value from
your application with a lightweight SDK.

## Start here

1. [Create your first feature flag](/get-started/quickstart)
2. [Understand projects, environments, and flags](/get-started/concepts)
3. Install the [JavaScript SDK](/sdks/javascript) or [React SDK](/sdks/react)

## What you can do

* Turn a feature on or off without another application deployment.
* Set distinct flag values for development, staging, and production.
* Use read-only API keys in an application to retrieve values safely.
* Add polling and caching when your application needs refreshed flag values.

## Find the right guide

Use a basic feature flag when the same value should apply to every user in an
environment. Use targeting or a percentage rollout when evaluation needs
context. Use an experiment when variants must remain stable for the same
subject. Use surveys to collect structured feedback from an eligible audience.

Each feature has a dedicated guide as it becomes publicly available. The
[documentation architecture](https://github.com/haris-syed/FujiFlag/blob/main/fern/DOCS_INFORMATION_ARCHITECTURE.md)
records the planned map and the product evidence required before a page joins the
public navigation.