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 Cassandra 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 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.