Coming soon! A Pro version of the Flipper gem for entirely local installations.

Get Updates

Documentation

Upgrade from Open Source to Cloud

Learn how to safely upgrade from only using the self-hosted version of Flipper to using Flipper Cloud to manage your feature flags.

If you are already using the open source version of Flipper, migrating to Cloud is easy without any code changes. You can use the UI or the flipper gem to migrate all your feature data in a few minutes.

Via the Flipper UI

The easiest way to migrate to Cloud is via the Flipper UI.

Since version 0.27, the Flipper UI supports exporting your feature data to a JSON file. Go to Settings and then click Download.

Viewing import and export in self-hosted UI
Viewing import and export in self-hosted UI

Once you have the exported file, go to Import / Export for the Flipper Cloud environment you'd like to import into. From there, you can upload the file and import your features.

Via the flipper gem

If you don't have the Flipper UI installed, you can use the flipper gem to export your features to a JSON file.

File.write("flipper.json", Flipper.export.contents)

Once you've exported the file, you can go to Import / Export for the Flipper Cloud environment you'd like to import into. From there, you can upload the file and import your features.

Via Flipper Cloud

In addition to importing and exporting file backups, Flipper supports syncing between adapters. This avoids the need for exporting and importing a file.

From a console or script, you can import your current adapter into Flipper Cloud:

require 'flipper/cloud'

# Get the currently configured instance of flipper with whatever adapter you are using.
current_flipper = Flipper.instance

# Or if you need to initialize flipper with a specific adapter or configuration
# current_flipper = Flipper.new(Flipper::Adapters::ActiveRecord.new)

# makes cloud identical to memory flipper
# note: this will wipe out whatever is in cloud
Flipper::Cloud.new(token: "<your-token-here>").import(current_flipper)

Warning: do not configure the FLIPPER_CLOUD_TOKEN environment variable in your application prior to running the import. This will cause your application to use the Flipper Cloud adapter which will sync your current adapter with whatever is currently in Cloud (and could result in data loss).

Ready to try it out?

Get audit history, rollbacks, advanced permissions, analytics, and all of your projects in one place.


Prefer our Cloudless option?

You can choose from several tiers to sponsor Flipper on GitHub and get some great benefits!

The Friday Deploy

Get updates for all things Flipper—open source and cloud.

Have questions? Need help?

Email us any time or head on over to our documentation or status page for the latest on the app or API.

Ready to take Flipper for a swim?

No credit card required. 14-day free trial. And customer support directly from the developers.