Change Details

There are two licensing models for running enterprise Metabase. With the standard model, you configure a license key via UI and Metabase makes an outbound web request (to AWS) periodically to validate the key. There is also an airgapped model, with different pricing, where you're provided a jar to install that is tied to your license key and the jar handles the license-period validation. https://www.metabase.com/docs/latest/paid-features/activating-the-enterprise-edition We are currently licensed for the first version but are running the open source version essentially airgapped. This blocks us from switching to enterprise. We do have the option of routing the request through a proxy. This requires significant configuration and testing. We can do that work in a sandbox if have a test key (preferable) or are sure we don't invalidate the production key by using it on more than one instance.

There are two licensing models for running enterprise Metabase. With the standard model, which is what we are licensed for now, you configure a license key via UI and Metabase makes an outbound web request (to AWS) periodically to validate the key. There is also an airgapped model, with different pricing, where you're provided a jar to install that handles licensing and time-validation. In this model, each upgrade requires a new jar. https://www.metabase.com/docs/latest/paid-features/activating-the-enterprise-edition We are running the open source version essentially airgapped, which blocks us from switching to enterprise. We have the option of routing the request through a proxy, but it requires significant configuration and testing. We can do that work in a sandbox if have a test key (preferable) or are sure we don't invalidate the production key by using it on more than one instance.

There are two licensing models for running enterprise Metabase. With the standard model, With the standard modelwhich is what we are licensed for now, you configure a license key via UI and Metabase makes an outbound web request (to AWS) periodically to validate the key. There is also an airgapped model, with different pricing, where you're provided a jar to install that handles licensing and time-validation. In this model, where you're provided a jar to install that is tied to your license key and the jar handles the license-period validationeach upgrade requires a new jar. https://www.metabase.com/docs/latest/paid-features/activating-the-enterprise-edition We are currently licensed for the first version but are running the open source version essentially airgapped., Thiswhich blocks us from switching to enterprise. We do have the option of routing the request through a proxy., Thisbut it requires significant configuration and testing. We can do that work in a sandbox if have a test key (preferable) or are sure we don't invalidate the production key by using it on more than one instance.