Here’s what Liquibase users have to say
"Liquibase is like Git for databases."
"One of the best things to come out of implementing Liquibase Enterprise is that our DBA developers are spending much less time in deployments and are able to focus on other things."
Frequently asked questions
Targets (previously referred to as “database connections”) are the number of data sources in each environment managed with Liquibase. Liquibase is licensed per target to support a wide range of database platforms and configurations. View example configuration.
Liquibase offers volume discounts and alternative pricing models to fit your business. Contact us for details on alternative pricing models for SaaS companies or volume pricing for architectures and enterprises that leverage targets at a high rate.
Yes. Liquibase offers volume discounts and alternative pricing models to fit your business. Contact us for details on alternative pricing models for SaaS companies or volume pricing for architectures and enterprises that leverage targets at a high rate. We’re happy to work with your team on pricing. Contact us for details.
Liquibase Open Source (Community Edition) is released under the Apache 2.0 license. The main Liquibase jar file also contains a commercially licensed Liquibase Pro code that is only active when a license key is entered.
Liquibase Enterprise is commercially licensed. Contact Sales for more details.
You can get the Liquibase open source project source code from GitHub.
Liquibase works better because it understands your changes. For example, a database comparison program would simply see the “person” table on integration has a “firstname” and a “lastname” column, but on live, the “person” table has a “name” column. It would report that you need to drop the “name” column and add a “firstname” and a “lastname” column. While this would leave you with the correct schema, you would lose everyone’s name in the process. With Liquibase, you would have a changeset that says “rename ‘name’ to ‘lastname’ and add a ‘firstname’ column” or, even better, “split the name column on a space and place the values in new ‘firstname’ and ‘lastname’ columns, then drop the ‘name’ column.” Knowing why they are different allows you to make changes to a production database without the fear of losing valuable data.
Yes. Since each change is independent, database changes that have been made in a different branch and then merged in will run the next time you run Liquibase. If you encounter a problem with the order that the statements are in, simply reorder the changelog files.
Yes. Premium support is available. Contact us and we’ll make sure you get the support you need.