Concepts

An index of the RocketFlag concepts so understanding the terms used in the app is clear.

Published on: 13 May 2025

Table of contents

Projects

A project in RocketFlag is a space for you to store flags which relate to that project. Think of it as a container for all your project’s flags.

A project can be named anything you like and it can also have an environment associated with it to make it easier to identify if you have multiple environments per project.

Once you’re logged in, you’ll be able to create new project with this button.

Flags

A flag in RocketFlag is the core of feature flagging. Your application will use this flag to determine what to show to your users!

A flag will have multiple properties attached to it, in order to make it work. Most of them, you can configure yourself.

If you’ve configured a project and are viewing all the flags in that project, then you can create a flag using the button in the project page.

Flag Properties

Flag ID

This is the automatically assigned identifier associated with the flag. You used this in API calls to the RocketFlag service in order to get back a response.

Flag Name

This is used to help identify the flag as the APIs will work with the flag’s ID for the most part.

Traffic Percentage

This value will determine how many times the API will respond with a true value, should the flag be enabled.

For example, let’s say the traffic is set to 80%. This means each time this feature flag is queried, it will have an 80% chance to be true.

You might want to use this setting for feature flags where you’re not confident about the release or if you want to test the release with production traffic on a certain threshold of traffic. For instance, you might want to turn on the flag for 1% of traffic to observe logs and metrics before dialling it up to a higher value. This number can be changed as often as you like.

Traffic percentage not set to 100% means that each time the API is called may result in a different response.
Enabled

Whether or not this flag is turned on for use or not. Disabling a flag will mean it will always return false from the API when checking if it can be used or not.

Cohorts

You can set special identifiers on a flag. When your application then queries the flag, you can pass the query the cohort or identifier you want, such as a logged in user’s email address or id and then provide a different response based on if that identifier is in the set cohort.

This is just a comma separated list that you can enter when creating or updating a flag. For example:

 user@example.com,id:12345,qa-team@example.com
Tip:

Cohorts are a great way to only enable certain features for specific users. For example you might want to enable a feature for users in a “early access” group. Or perhaps enabling a new feature for validation and testing in production where you don’t want to affect all your other users yet.

Read next: RocketFlag Flags API