API access
Provide the ability to create, edit and delete identities via our API as well as reading the current feature flag status for a given identity.
Features that we are working on at the moment or planning to tackle in the future.
We are currently working towards our public beta for which we are going to implement all features from the "Explore" plan.
Provide the ability to create, edit and delete identities via our API as well as reading the current feature flag status for a given identity.
Segments allow you to group identities and then target that segment specifically. Imagine have a set of early access users that you can put in a segment and enable features for these users first.
You can now create identities against which you want to target your feature flags. Identities are usually going to your users or visitors but you can also use identities to target other systems and services. All they need to have is a unique identifier.
Introduce the ability to create, edit and delete environments. This allows you to develop and test a freature on a test environment before enabling that feature flag on production. On creation, you can also sync all feature flags from another environment.
Introduce the ability to create, edit and delete basic feature flags and enabling and disabling them. This does not include any custom rules, triggered feature flags or scheduling capabilities yet.
Once the public beta is running, our focus will be to implement the remaining features that will enable teams to scale the feature flag usage.
This will allow you to target feature flags based on more complex rules than just adding and removing identities.
Instead of enabling feature flags manually for specific identities, this feature will allow you to enable feature flags on a specific date or even roll out feature gradually.
Similar to scheduled feature flags, this feature will allow you to enable a feature flag by a threshold trigger. For example, our system will regularly visit your health check and enable a kill-switch feature flag when a certain load is reached.
Introduce feature to limit which user can access which part of the platform. This will allow slightly larger teams to collaborate better.
For each feature flag, get a detailed history of how and when a feature flag was enabled or disabled. This will be useful for auditing purposes.