Assign feature owners
With feature owners, there's neve any question who to ask for updates or how to know if the team has plans for a given feature flag in the near future.
Know when flags are safe to delete
Flipper lets know the last time each flag was checked for each environment so temporary flags can be removed and deleted safely. Flipper lets know the last time each flag was checked for each environment so you always know when those temporary flags can be removed and deleted safely.
Tag related features
Temporary or permanent flag? Circuit breaker? Which area of the application does it affect? Tags help stay on top of all of your flags.
Leverage unlimited projects and environments
You can never have too many projects or environments, and you never have to worry about having too many. Keeping features organized is easier than ever.
Stay current with the latest features
Managing dependencies and versions is just part of the process, but with Flipper, it's a little easier. If Flipper, Rails, or Ruby ever start to fall behind the target versions, you'll know ahead of time to help plan for any necessary updates.
Unlimited team members
While Flipper UI provides a great interface for managing feature flags, it doesn't support multiple team members and the resulting audit history as individuals make changes. With Flipper Cloud, not only are team members connected with their activity, but each team member has their own personal environment so they can develop against the flag data they need without stepping on anybody else's toes.
Automated testing as a first-class citizen
Introducing feature flags means introducing alternative code paths, and that means testing those code paths. Flipper Cloud makes it easy to test your code with feature flags by providing a simple way to enable and disable features in tests.
class DocumentationControllerTest < ActionDispatch::IntegrationTest
test "returns 404 for documentation when feature disabled" do
test "renders documentation when feature enabled" do