Feature flags for teams that ship a change to a few people first.

What we do

Name the flag. Every change gets one name and one owner. When the change is in for everyone, the name is deleted. A flag that stays is only a setting nobody owns.

Turn it on for a slice. The rest of the product keeps the old path. The people still on that path do not have to sit through a launch to learn the new one.

Watch one number. If it stays quiet, the flag opens further. If it moves the wrong way, the switch comes off. Off is the old path, and it does not need a new deploy.

How a rollout works

The team picks the change, the person who owns it, and the number that would make them turn it off. Flagholm holds those three. The flag starts closed. A small group is let in. The number is read before the group grows.

The number is chosen before the flag opens. Orders, errors, refunds, or support tickets are the usual ones. Flagholm does not invent that number. The owner does.

Pulling the flag back does not ship new code. After the change is the normal path, the flag is removed so the next change has a clean name. The studio does not run the launch meeting. The flag is the record of who decided, and of the number they trusted.

The company

Flagholm Ltd is a software company in Nigeria. Seyi Adebanjo is Founder and CEO. Write to [email protected] and say what the change is, who owns it, and which number would turn it off.