review galore

Review · Database systems

Liquibase review

A capable free migration tool; governance plans require a vendor quote and professional services.

7.2/10Review Galore score

We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money

The bottom line

Good free change management; Secure plan costs and services need a quote.

A team of 1–10 can use Liquibase Community for free to define and order database changes in SQL, XML, JSON, or YAML. It supports over 60 databases, but seat and usage limits are not published, so confirm fit before standardizing it across a larger team.

Liquibase Secure adds governance and change intelligence, but its plans are quote-based and require professional services. Reddit users describe successful automated workflows as well as migration and analytics concerns, so process and policy choices matter as much as the tool.

Good fit if

  • Teams versioning database changes
  • Small teams starting with free migrations
  • CI/CD database deployment workflows

Skip it if

  • Teams needing published seat pricing
  • Teams avoiding required services
  • Teams wanting zero migration process work
Liquibase homepage
Liquibase homepage, captured Nov 10, 2026

ScoresHow it rates

  • Features8
  • Ease of use6
  • Value for money8
  • Support5
  • User sentiment6

What works

  • Community edition is free
  • Supports SQL, XML, JSON, and YAML
  • Supports over 60 databases
  • Automates changes through CI/CD
  • Includes rollback support

What doesn't

  • Community seat and usage limits are unpublished
  • Secure plan prices require a quote
  • Professional Services package is required for Secure
  • Secure plan target limits vary
  • Reddit users raise analytics and deployment concerns

01Who Liquibase is for

Liquibase fits teams that need a repeatable way to manage database changes alongside application development. For a team of 1–10, Community is a practical starting point: it is free, supports over 60 databases, and lets developers define changes in SQL, XML, JSON, or YAML. It can suit a small engineering group that wants changes ordered and version-controlled before adding deployment automation.

The main job is keeping database changes organized as they move through development and deployment. Liquibase also supports rollback, while its Secure plans add governance and change intelligence for teams that need more controls. That makes it relevant to teams moving from ad hoc database edits to managed changes and CI/CD. The budget catch is that Secure prices are quote-based, and each Secure plan requires a Professional Services package. A small team should start with Community and ask the vendor for a full Secure quote before budgeting for governance.

02Liquibase free plan and trial

Liquibase Community is free software. The pricing page lists change definitions in SQL, XML, JSON, or YAML and support for over 60 databases. It does not publish seat or usage limits, so a small team should confirm whether its intended deployment pattern fits before relying on Community at scale. No free trial is listed for the paid Secure plans.

Community is the lowest-cost way in, and may be enough if your team needs to define, order, and manage database changes without Secure governance or change intelligence. The paid Starter plan is aimed at smaller companies starting with governance, but its price is not published and a Professional Services package is required. Ask Liquibase whether Community covers your team’s expected use and what the complete Starter cost would be.

03What a small team pays for Liquibase

Community costs $0 per plan, so one person, a team of three, or a team of five pays nothing for the software. The pricing page does not publish Community seat or usage limits, however, so free does not necessarily mean every team size or usage pattern is covered.

Liquibase Secure has no published per-seat price, monthly rate, or annual rate. The plans are quote-based, so we can’t calculate what one person or a three- or five-person team would pay, or compare monthly with annual billing. Starter is for smaller companies under $1 billion in annual revenue and lists 250 database targets. Team covers one application, one database type, and 500 targets; Business covers multiple applications, two database types, and 750 targets. Each Secure plan requires a Professional Services package, whose cost is also unpublished. Additional database types and capacity, Change Intelligence for Team, Business, and Enterprise, and overages may add cost. Get a written quote with these items spelled out before comparing plans.

Full Liquibase pricing breakdown →

04Getting started with Liquibase

Setup effort depends partly on whether your team already has a migration process and which change format it prefers. Liquibase supports SQL, XML, JSON, and YAML, so teams can choose among those formats rather than adopting one required definition language. Its core workflow is to order and version database changes, then automate deployments through CI/CD or developer self-service.

Reddit users describe different ways to introduce it: one team keeps migrations in plain SQL, reviews each migration in a GitHub pull request, and runs CI checks before merging; another recommends beginning with manual runs and automating gradually. These examples point to process work, not just installing a tool. A team should decide who can change schemas, how migrations are reviewed and tested, and how deployments are approved. Product materials describe CI/CD automation, but the exact setup steps and integration list should be confirmed in Liquibase’s docs for your environment.

05When small teams outgrow Liquibase

A team may outgrow Community when it needs paid governance or change intelligence, or when its required capacity is beyond what a free plan can support. The catch is that Community seat and usage limits are not published. Secure plans list target limits—250 for Starter, 500 for Team, 750 for Business, and 2,000 for Enterprise—but add-on capacity and overage costs are not published. Ask for those figures before choosing a plan.

Reddit users also point to operational risks that a tool alone cannot solve. In one thread, a team described production trouble after a migration was stopped and the database changed manually; another commenter described automated tests and staged rollout practices. A separate discussion raised concerns about anonymous usage analytics, while a commenter said it could be disabled. For a growing team, review analytics settings and agree on migration testing, deployment ownership, and production access. If Secure’s required services or quote-based pricing do not fit the budget, Community may remain the practical choice.

From the threadsWhat users say

Reddit sentiment is mixed: users describe long-running, successful use and practical CI workflows, but also report costly migration mishaps and raise concerns about usage analytics. Several comments emphasize that disciplined testing and deployment ownership are essential.

Long-term use
I've personally used Liquibase for over 10 years and have had no issues that I didn't create myself
r/devops · view thread
CI workflow
We use liquibase and it is mostly good
r/devops · view thread
Migration risk
Once we made staging read only access we had 0 issues
r/devops · view thread
Analytics concerns
For us, this meant a compliance breach as we aren't allowed to connect to unknown servers and send data
r/java · view thread

Questions people ask

Is Liquibase free?

Yes. Liquibase Community is listed as free software and supports change definitions in SQL, XML, JSON, or YAML, plus over 60 databases. The vendor does not publish Community seat or usage limits, so ask whether your team’s intended use is covered before rolling it out broadly.

What does Liquibase Secure cost?

Liquibase does not publish Secure plan prices or monthly and annual billing rates. The plans are quote-based, and each Secure plan requires a Professional Services package whose cost is also unpublished. Request a complete quote that includes any add-ons, capacity, and overages you may need.

Which database change formats does Liquibase support?

Liquibase Community supports change definitions in SQL, XML, JSON, or YAML. Teams can use a format that fits their existing development workflow; Reddit users describe using both plain SQL and XML. Check your chosen format against your team’s database and migration practices.

Can Liquibase roll back database changes?

Rollback support is listed as a Liquibase feature. A rollback plan is still something your team should review and test as part of its migration process. Reddit users emphasize the importance of testing changes and managing deployments carefully, especially when production database access is involved.

What does Liquibase Secure add?

Liquibase Secure adds governance and change intelligence capabilities. The Secure plans list different application, database-type, and database-target allowances, and some include Change Intelligence as an add-on. Prices are quote-based, and professional services are required, so ask the vendor to map your needs to a plan.

Sources

  1. Liquibase homepage
  2. Liquibase pricing, compiled via web search from g2.com, schemasmith.com, liquibase.com
  3. Reddit: Liquibase starts sending data to their servers
  4. Reddit: Experience with Liquibase and similar software
  5. Reddit: Liquibase & Springboot