.svg)
.svg){kind=icon}
Liquibase Pro:
Enterprise Grade Database DevOps
Scalable, reliable, and secure database change workflows across teams and environments.
Liquibase Pro
Enterprise grade change automation with CI/CD, observability, and governance
$500/target
Maximum 10 targets. Learn how to count targets.
.svg){kind=icon}
Custom
Contact us to discuss volume pricing and support options for Pro and OSS
Talk to Sales
.svg){kind=icon}
Compare features
.svg)
Change Management
Native SQL Dialect Support for PL/SQL, SQLPL, T-SQL, and more |  | |
Change format How scripts are formatted | SQL, XML, YAML, JSON | SQL, XML, YAML, JSON |
Change creation & management Where changes are created and how they are managed | CLI or 3rd party automation tools | CLI or 3rd party automation tools |
Smart database updates Automatically determine and deploy all changes that have not yet been deployed | | |
Targeted database updates Execute a specific change on the database | - | |
Preconditions Control the execution of an update based on the state of the database | | |
Set labels and contexts Determine which changes and sets of changes are eligible to deploy | | |
Change preview / dry run Review all raw SQL changes before you apply them | | |
Rollback Undo the most recently applied change or all changes back to a set point | | |
Advanced rollback Cherry pick changes to undo and automatically rollback when an error is detected | - | |
Native executors Run advanced changes with native executors SQL*Plus, PSQL, SQLCMD, and MongoSH | - | |
Stored logic Work with stored procedural code on select platforms, including Oracle SQL*Plus | - | |
Change generation Generate sets of changes based on the database | | |
Advanced change generation Generate sets of changes based on the database including stored logic | - | |
Snapshot Generate a schema snapshot | | |
Advanced snapshot Generate a schema snapshot including stored logic with advanced features | - | |
Remote files Run Liquibase files hosted remotely on Amazon S3 | - | |
Observability, compliance & governance
Diff Generate a comparison (or diff) between two databases to detect unexpected bugs | | |
Advanced diff & drift detection Automate notifications to alert your team when unexpected (potentially malicious) differences between databases are detected | - | |
Policy Checks Check the quality and security of your database code on-demand or in automation against a set of rules before deployment | - | |
Flows Orchestrate database change workflows and best practices for instant and consistent deployments | - | |
Structured Logging Structured and customizable logging that enhances observability and security with your BI tools and dashboards | - | |
Operations reports Portable reports for operational insights and error detection | - | |
Secrets management Built-in integration with AWS Secrets Manager and HashiCorp Vault | - | |
Installation, deployment & configuration
Installation Download and install Liquibase via CLI, API, Spring, Docker, Maven, Gradle, Ant, Debian/Ubuntu, and Red Hat/ CentOS | | |
Deployment Deploy changes manually or via automated processes | | |
Standard JDBC Pass credentials and connection attributes via CLI or properties files | | |
Command line & properties file Configure & specify details like database connection & classpath information using a single file, CLI, or Java system properties | | |
Support
Community support Get help with most of your Liquibase questions and issues in our community forum | | |
Standard support Get support via email — view details on Standard support hours and SLAs | - | |
Premium support Access to 24×7 support — view SLA details | - | Available |
Onboarding Training to get started | - | Available |
Technical Account Manager Personalized service and account reviews coordinated by a Technical Account Manager | - | Available |
Frequently asked questions
.svg){kind=icon}
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.
Example: Three MySQL schemas across Dev, Test, and Prod environments = nine targets
Example: Two Postgres databases across Dev, Test, and Prod environments = six targets
*For the following databases schemas are counted as targets: MariaDB, MySQL, Oracle, SingleStoreDB.
*For Casandra keyspaces are counted as targets.
*For pricing on Snowflake, Dynamo, and Databricks please Contact Sales.
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.
Liquibase Open Source is released under the Apache 2.0 license. The main distribution also contains 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, Liquibase works with git based workflows to meet your needs, whether that is a trunk based branching, release based or environment based branching. Learn more about Liquibase and GitOps here.
Yes. Premium support is available. Contact us and we’ll make sure you get the support you need.
Yes. Liquibase offers professional services to help design, plan, and implement based on your unique environment and requirements. Contact us to learn more.
Liquibase has helped us with implementing reliable version control and a CI/CD pipeline for our data warehousing needs. The space for database version control leaves a lot to be desired, but thankfully Liquibase has that covered! We have paired Liquibase with GitHub and GitHub actions to reliably ensure all of our environments are in sync and easily track our deployments.
As database administrator and consultant, Liquibase is a great tool. It frees up DBA time to manually sync database schema between DEV, TEST and PROD environments. By doing schema comparison programally, it gives me the peace of mind that all database objects are identical between different environments. We could also delegate the task to operation team.
"An ease of error-prone and quick database deployments both on-prem and on cloud integrated with CI/CD DevOps Automation."
Liquibase brought our database changes and data correction processes up to speed with our code deploys which were already automated. It allows us to rely on automated validation as well as fit into our current software development lifecycle processes and CM software using a central versioned artifact capable of being deployed through our current CD pipeline.
We use the Liquibase tool for DB deployment automations using the CICD process. It helped us a lot by reducing human error with the standard audit reporting structure integrated with it.
"Use Cases and Deployment Scope We use Liquibase to handle version control and source code control of SQL scripts and database changes and for the deployment and (if needed) rollback of the same. It's helped us go from arbitrary SQL changes that we tried to manually track, to having a reliable, repeatable, accurate account of what's in our database structure."
Liquibase addresses challenges related to database schema management, version control, collaboration, and deployment automation. Its scope of use cases spans software development, CI/CD, microservices, data migration, compliance. As applications evolve, the database schema might require refactoring. Liquibase supports the controlled refactoring of database structures while preserving data integrity.
"We use Liquibase to maintain our changelogs while transforming our data in snowflake and deploying it to test and prod. Liquibase changelogs help us keep up to date with our changes and do the rollback in case of any error. Liquibase also provides many validation features that will come in handy if you want to establish checks during your code deployment. It's a great product with excellent customer service."
Change log management organize and database changes in a systematic manner. Changes are organized into a series of change sets, each representing a specific change or a set of related changes.
I love the flexibility with the schema changes. I don't have to restrict my team to "only XML" way. It is possible to come up with schema changes in YAML and JSON, which is the order of game nowadays.
Get started with Liquibase today!
