Ship new features to a few people first.
Start with a small group, widen the rollout once it holds up, and switch it off without a deploy if it breaks. It runs on the same SDK as your analytics.
3 flags free.
Kill a bad release from the dashboard.
Flip the switch and browsers drop the feature on their next refresh, with no deploy.
Give a customer's whole team the feature at once.
Roll out by organization, so everyone at the same company sees the same thing.
Give beta testers early access.
Target by email, plan, or any property you send, and reuse the same group on every flag.
- i•••@databuddy.ccfree
- m•••@gmail.compro
- k•••@outlook.comfree
- s•••@proton.mepro
- j•••@databuddy.ccfree
- t•••@gmail.comfree
Turn off a whole feature with one switch.
Make smaller flags depend on a parent, and switching the parent off takes them all down together.
Roll out flags from your editor.
Your agent can list, create, and update flags and target users over MCP, and every change shows a preview and waits for your yes.
Frequently asked questions
Have a question that isn't listed here? Email support@databuddy.cc.
Plan your setup and measurement
- Connect feature flags and analytics
Plan how a rollout will be evaluated alongside the product events it is meant to change.
- Plan custom event measurement
Compare event tracking options before defining the actions your product needs to measure.
- Migrate PostHog SDK calls
Review compatible imports and the behavior that changes before replacing an existing integration.