Liquibase review

Liquibase is downloadable database change management software, not a hosted database or a hosted API service. It sits alongside an application’s code in the development and deployment workflow: teams define database changes, order them under version control, then deploy them through CI/CD or developer self-service. The homepage names SQL, XML, JSON, and YAML as change-definition formats.

That puts Liquibase between application changes and the databases those changes affect. It is intended to replace manually ordered scripts with versioned changes that can be deployed and rolled back. The Community edition supports over 60 databases, while the broader platform describes coverage across 70+ databases. Liquibase Secure adds governance and change intelligence for teams that need policies, controls, and risk review across pipelines. The homepage describes integration with build tools, but does not position Liquibase as a separate hosted database service.

Build around versioned change definitions in SQL, XML, JSON, or YAML. The homepage names GitHub Actions, Jenkins, and GitLab CI/CD as build-tool integrations, and says Liquibase can be embedded into a product or build tool. That gives teams a workflow surface for CI/CD and developer self-service rather than a documented hosted REST API.

The homepage does not name SDKs or programming languages. These file formats are ways to describe database changes, not a list of supported application-language SDKs. If your integration depends on an SDK, language-specific package, or API contract, confirm support in Liquibase’s docs before committing to it. The site links to Docs and Downloads, and its Community section invites contributors. Its stated capabilities include version control, automated deployment, and rollback; teams still need to test change behavior against their target database and deployment process.

Community is free software. It supports change definitions in SQL, XML, JSON, or YAML and over 60 databases. Seat and usage limits are not published, so confirm any constraints that matter to your deployment before relying on the free plan at scale.

Liquibase Secure has four listed plans: Starter, Team, Business, and Enterprise. The pricing page lists 250 database targets for Starter, 500 for Team, 750 for Business, and 2,000 for Enterprise. Team covers one application and one database type; Business covers multiple applications and two database types; Enterprise covers four database types. Starter is for companies under $1B annual revenue. Prices are quote-based, and monthly versus annual billing is not published.

Each Secure plan requires a Professional Services package. Additional database types and capacity are available, and Change Intelligence is an add-on for Team, Business, and Enterprise. Their prices and overage costs are not published. Ask for a quote that covers target counts, database types, services, add-ons, and any overages.

Liquibase describes Community as free software and offers it as a download. Its homepage says teams can embed it into products and build tools such as GitHub Actions, Jenkins, and GitLab CI/CD. That supports a workflow where change management runs within a team’s own delivery stack, rather than requiring a separate hosted Liquibase server.

The homepage does not name Community’s software license. Check the license terms directly before distributing or modifying it. Liquibase promotes version control, and its change definitions can be kept with application code in Git. That gives teams an exit path for the change files themselves, but does not make switching automatic: another tool may require changes to those definitions and a plan for existing deployment history. The vendor does not describe a one-click export or migration utility. Ask what data and history can be exported if you plan to use Secure governance features.

The main production risk is the migration process, not simply the choice of tool. Test changes against the database engine and version you run in production, and review long-running or data-heavy migrations before deployment. In one Reddit thread, a developer described a migration that stalled after a staging deployment was stopped, followed by a six-hour production outage. Other commenters stressed testing and clear ownership of deployments.

A separate Reddit thread raised concerns about Liquibase sending usage analytics to its servers after an upgrade from 4.27 to 4.30; a commenter said analytics can be disabled. Teams with strict network or compliance controls should review the relevant settings and outbound traffic policy before rollout. Liquibase Secure offers governance and change intelligence, but those features do not replace access controls, testing, or an incident plan. The vendor’s listed Secure target counts are plan capacities, not published reliability or performance guarantees.