Concepts

Use these terms consistently in FujiFlag. The dashboard and SDK documentation refer to a product capability as a feature flag. Some API and backend code uses config internally; it refers to the same flag model and is called out only when an API field or type requires that name.

Project

A project represents an application or service that uses feature flags. It contains its environments and flags.

Environment

An environment represents a deployment context, for example development, staging, or production. A flag can have a different value in each environment.

Feature flag

A feature flag has a name, a stable key, an optional description, and a type. Applications use the key to retrieve its value. Choose a key that describes the behaviour it controls, such as new-checkout, rather than a temporary ticket name.

Flag value

Each flag stores its value per environment. Changing an environment’s value changes the result returned to applications using an API key for that environment.

API key

An API key identifies the environment from which an SDK can read values. Use a separate key in every deployment environment and rotate a key if it is exposed.

Next step

Create a flag with the Quickstart, then review API-key guidance before connecting a production application.