Multiple script formats
Supports SQL, XML, YAML, and JSON.
Generate SQL scripts
Automatically generate SQL script output for review.
Precisely undo one change or an entire set of changes safely and easily.
Works with Maven, Gradle, Ant, Jenkins, TravisCI, Spring and more.
Handle more types of schema changes with enhanced stored logic capabilities.
Automatic drift detection
Automatically detect differences between database schemas using JSON output.
Use more complex SQL queries with native SQL*Plus execution.
Organize, monitor, and visualize database change activity in real time.
Database release automation
Automatically control what, when, and where database changes are deployed.
Detailed status views
View your database release pipeline and the steps along the way.
Deployment & rollback reporting
A full report about your database deployments and rollbacks.
Database deployment dashboard
Monitor the status of every database deployment across the enterprise on a centralized dashboard with LDAP integration.
Access to detailed guides and step-by-step videos for implementing database CI/CD at any pace.
Database code packager
Package database and app code together to easily enable end-to-end database continuous deployment.
Automatic database recovery
Automatically revert a database in your CI/CD environment to its last known good state.
Database change forecasting
Understand the impact of database changes before they’re deployed.
Ensure database standards and compliance requirements are being met with the database rules engine.
Frequently asked questions
Liquibase Community 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 Business and Liquibase Enterprise are commercially licensed. Contact Sales for specific license details.
You can get the Liquibase open source project source code from GitHub.
Database connections are the number of databases in each environment connected to Liquibase. View an example of how we count database connections.
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.
Here’s what Liquibase users have to say
“Liquibase is like Git for databases.”
“We can’t afford any bottlenecks in our CI/CD process. [Liquibase Enterprise] helps us bring automation to the operations side of DevOps, clearing the path from development to production for the entire application, including the database.”