Skip to content

What is FlagPal?

FlagPal is a feature management and experimentation platform. That's a fancy way of saying: it lets your team control which features your users see, test new ideas safely, and measure whether those ideas actually work.

Think of FlagPal as a set of switches and dials for your product โ€” you can flip a switch to turn a feature on for some users and off for others, set a dial to route 50% of traffic to version A and 50% to version B, and read the gauges to see which version is winning.


Why Do Teams Use FlagPal?

The Old Way: Ship and Pray

In the traditional way of building software:

  1. You build a feature
  2. You deploy it to everyone
  3. You cross your fingers and hope it works
  4. If it breaks, you scramble to roll back

This is risky and stressful โ€” especially for big changes.

The FlagPal Way: Ship with Control

With FlagPal:

  1. You build a feature with a flag attached
  2. You deploy the code, but the feature is turned off
  3. You turn it on for a small group first (say, 5% of users)
  4. If it works well, you gradually roll it out to everyone
  5. If it breaks, you turn it off instantly โ€” no deployment needed

This gives you confidence to ship faster, because mistakes are easy to undo.


The Four Key Concepts

FlagPal is built around four ideas. Don't worry if they sound technical โ€” we'll explain each one in detail. Here's the quick version:

๐Ÿšฉ Feature Flags

A Feature Flag is like a light switch for a specific feature in your product. It has a name, a type (on/off, a number, text, etc.), and rules for when it should be on or off.

Example: A flag called new_checkout_flow that is either true (show the new checkout) or false (show the old one).

Learn more about Feature Flags โ†’


โœจ Experiences

An Experience is how you deliver a specific set of feature values to users. It lets you define which users should see a feature turned on or off.

Example: Turn on new_checkout_flow for users who are in your beta program.

Learn more about Experiences โ†’


๐Ÿงช Experiments

An Experiment is an A/B test. You split your users into groups (variants), show each group a different version of a feature, and measure which version wins.

Example: Show Group A the old checkout (flag = false) and Group B the new checkout (flag = true). Measure which group has a higher purchase rate.

Learn more about Experiments โ†’


๐Ÿ“Š Metrics

A Metric is something you want to measure โ€” like the number of purchases, signups, button clicks, or revenue. You attach Metrics to Experiments to find out which variant is performing better.

Example: A metric called Purchase Completed that counts how many times users complete a purchase.

Learn more about Metrics โ†’


Who Uses FlagPal?

FlagPal is useful for anyone involved in building or managing a software product:

Role How they use FlagPal
Product Manager Roll out features gradually, run experiments, measure results
Developer Integrate the API, manage technical flags
Designer Test different UI variations with real users
Data Analyst Measure experiment outcomes and report results
QA Tester Turn on features for testing without affecting production users

You don't need to be a developer to use FlagPal โ€” the interface is designed for the whole team, and we provide multiple SDKs (plugins) for different platforms to ensure seamless integration for anyone.


Ready to Get Started?

Now that you know what FlagPal is, let's set you up: