Everything a rollout needs
Product
Gates
A gate is on or off for each person. The kill switch turns it off at once, rollouts go by percent with stable SHA-256 bucketing, every version is kept, and Restore brings an old one back.
new-homeKill switch- v12 hz: 10% to 20%current
- v11 jk: off to 10%Restore
Configs
Serve a number, text or JSON instead of on or off. Each config has a type, and JSON values are checked against a shape you set.
- max-itemsnumber20
- welcome-texttextWelcome back
- themeJSON{ "color": "black", "size": 14 }
Parameters
Code reads a name like checkout.buttonColor. The console maps that name to a constant, a gate, a config or an experiment in each environment.
flagship.get('checkout.buttonColor', 'blue')- devconstant "blue"
- prodexperiment button-test
Experiments
Split people into groups and read the lift, its confidence interval, the p-value and a sample ratio check. The page says how many people are still needed, then offers Ship, Don't ship or Keep running.
button-testShip green- Lift
- +4.2%
- Interval
- +1.1% to +7.3%
- p-value
- 0.008
- Sample ratio
- ok
- People still needed
- 0
ShipDon't shipKeep runningSegments
Group people into a list or a rule, like plan in pro. Give a gate to a segment, not to a list of names.
segmentinmac-developers- hz
- al
- jk
- mr
- tn
- pw
ruleplan in proEnvironments
Each environment has its own rules and keys. Mark an environment protected to require a reason for every change.
dev
on
staging
on
prod (protected)
on
Reason (prod)
Ship to Mac beta
Events
Exposure is recorded automatically. Count the events your apps send and use them as goals in experiments.
whats-new-opened4,210
export_clicked1,284
checkout-done640
And the rest
- whats-new
- Webon
- Macon
- iOSoff
Channels
One gate serves web, Mac and iOS. Make it visible to some channels, or give one its own rule.
- idhabz
- id in beta-testers
- segment in mac-developersmatched
- percent 25
Answer: on
Check a person
Type an id and see the exact rule that decided the answer.
- values
Server
rules
segments
other ids
Your app
{ "max-items": 20 }
Rules stay on the server
The app gets only the values it asked for. Rules, other people and segment lists never leave the server.
- Readervieweditkeys
- Writervieweditkeys
- Ownervieweditkeys
Members and teams
Readers look, writers change content, owners manage keys and access.
habz whats-new prod
10% -> 20% reason: widen
jk dark-mode staging
off -> on reason: qa pass
al whats-new dev
segment + mac-dev reason: try it
Audit log
Every change is recorded with its reason and the before and after values.
TypeScript
await flagship.isEnabled('whats-new')
flagship.get('max-items', 10)
resulttrue20cached offlineSDKs
TypeScript and Swift. Read a gate, config or parameter with a default. The SDKs never throw and answer from their cache when offline.
Request access
Open a ticket and your workspace owner adds you.