Document updated on Jun 8, 2023

Switching to Community or Enterprise

If you are considering upgrading to KrakenD Enterprise or downgrading to KrakenD Community, these are the things you should have in mind.

Downgrade to Community

If you are a KrakenD Enterprise Edition user and you want to switch to the Community Edition, these are the guidelines you should follow to keep your installation working.

• Obtain the Community Edition and replace it by the Enterprise one
• Make the configuration migration as described below
• Start the server with the modified (if necessary) configuration

Configuration migration

You can run a configuration file designed for the KrakenD Enterprise in a Community Edition straight away, except if you have one of the following options that you should remove and will make your server panic during startup:

• Dynamic routing.
• Endpoint with wildcards (/*)

If you have any of the components above, remove them from the configuration.

The other Enterprise-only features are ignored and not loaded into the server, so whatever you leave or remove them from the configuration makes no difference to the server. Still, you should delete them to avoid confusion when reviewing the configuration later, as none of these actually work.

Upgrade to Enterprise

To upgrade a Community configuration to an Enterprise one, no configuration changes are needed. The only steps required are:

• Obtain KrakenD Enterprise
• Add the LICENSE file to your project
• Start the new server

If you use the same version, everything you configured on the Community Edition works in the Enterprise Edition.