Liquibase review

Liquibase manages database changes: you define changes, keep them in version control, and use Liquibase to order and deploy them. The Community offering supports change definitions in SQL, XML, JSON, or YAML. The product is a change runner and control layer, not necessarily a migration generator: commenters in one r/Backend thread describe Liquibase and Flyway as tools that execute scripts rather than generate them.

The feature set covers team workflows as well as deployment. The product information lists branching and merging, control over when and where changes are deployed, and rollback support. Liquibase’s homepage also describes governance features in Liquibase Secure, its enterprise offering. That distinction matters when comparing plans: the available pricing information names Community and four paid plans, but does not specify which individual governance features come with each tier.

Liquibase suits teams that want database changes treated as versioned deployment artifacts rather than ad hoc edits. Its support for SQL, XML, JSON, and YAML gives teams a choice of formats, while automatic ordering helps manage the sequence in which changes run. The listed feature set also includes branching and merging, deployment controls, and rollbacks.

Those controls can support automated releases, but they do not replace careful migration design and testing. In one r/devops thread, a user who had used Liquibase for more than 10 years said it worked well for automated deployments and rollbacks, and described using it to create production-like environments quickly. Other commenters in the same thread pointed to problems when teams manually changed database schemas or ran poorly planned migrations. That is a process risk, not a Liquibase-specific fix: the tool can organize changes, but teams still need clear ownership and sound deployment practices.

For organizations that need governance beyond the Community feature set, Liquibase also presents Liquibase Secure as an enterprise option. The product information describes the category of features, but does not give enough detail to compare them against specific plan prices.

The main buying problem is price opacity. Liquibase lists no monthly or annual prices for its paid plans, and says Liquibase Secure requires a quote. Community is free, but seat and usage limits are not published. Paid tiers require a Professional Services package, whose cost is also not published.

The listed database-target caps are concrete, but the rest of the limits may affect the real bill. Starter supports up to 250 targets and is for companies under $1 billion in annual revenue. Team covers one application, one database type, and up to 500 targets; Business covers multiple applications, two database types, and up to 750 targets; Enterprise lists four database types and up to 2,000 targets. Additional database types and capacity, overages, and the Change Intelligence module for Team, Business, and Enterprise have no published prices.

There is also a trust concern to assess. A Reddit thread about usage analytics described an unexpected external connection as a compliance problem; commenters said analytics can be disabled, while disputing what data is sent. Teams with strict network rules should verify the current behavior and opt-out controls before upgrading.

Liquibase’s paid prices are not published, so there’s no reliable dollar figure—or calculable jump between tiers—to compare before requesting a quote. The pricing information lists Community as free; it does not publish seat or usage limits for that plan.

Paid plans all require a Professional Services package, whose price is also not published. Starter is for companies under $1 billion in annual revenue and allows up to 250 database targets. Team covers one application, one database type and up to 500 targets. Business covers multiple applications, two database types and up to 750 targets. Enterprise allows up to four database types and 2,000 targets for enterprise-wide standardization. The pricing information does not state prices for any of them.

Budget for potential extras, too: additional database types and capacity, overages, and the Change Intelligence module for Team, Business and Enterprise have no published costs. Monthly and annual billing prices are not published. Get the full quote, required services cost and overage terms before comparing Liquibase with your current stack.

The published material describes Liquibase as a way to define, version, order and deploy database changes, with changelogs in SQL, XML, JSON or YAML. If your existing changes use one of those formats, check how much of your current history and deployment process can carry over; the available information does not document a migration path or promise automatic conversion.

Lock-in and exit details are also unclear. The published material does not say whether Liquibase provides a data or changelog export, what formats an export supports, or how to preserve deployment history when leaving. Confirm those points against your own changelogs before switching. Paid-plan caps and required Professional Services may also affect the move, but their costs are not published.

No Reddit posts or comments were included in the published material, so we can’t substantiate reasons users leave or report community migration experiences. Ask Liquibase for a migration and exit plan, including how it handles your database types, branching and rollback needs.