Version control for the database. The CI/CD discipline of code - automation, review, rollback - applied to the one place most teams still deploy by hand.
Above: the Liquibase wordmark. In the style of Vincent Musi — a plain tool photographed against a dark field, because the work it does is anything but plain: it keeps the world's largest banks from breaking their own databases.
For years, engineering teams automated everything about shipping software - except the database. Application code flowed through pipelines with tests, reviews, and one-click rollbacks. Then a change hit the database, and someone opened a terminal, pasted in SQL, and hoped.
Liquibase closed that gap. It is an open-source library, first released in 2006 by engineer Nathan Voxland, that treats every schema change - a new column, an index, a constraint - as a tracked, reviewable, reversible artifact. Changes live in text files (XML, YAML, JSON, or plain SQL), tagged by an id and an author, so multiple developers and branches never collide. On first run it quietly stamps two bookkeeping tables into your database and starts keeping score.
In 2012 a company called Datical formed in Austin, Texas, to build enterprise tooling and support around the project. In 2020 it did the sensible thing and renamed itself after the software everyone already trusted: Liquibase.
“A database-independent library for tracking, managing and applying database schema changes.”
Versions, applies, and audits database schema changes across every environment, so what runs in production matches what was reviewed.
Millions of open-source users and thousands of teams - including 9 of the world's 10 largest banks and much of the Fortune 2000.
Manual database edits cause outages and failed audits. Liquibase catches out-of-process changes as they happen and names the source.
Liquibase runs an open-core model: a free engine that drives adoption, and a commercial platform that adds the governance regulated enterprises will pay for. In September 2025, Liquibase 5.0 formalized the split.
The free, open-source core. Changelogs, rollback, diff reporting, and CLI/Maven/Ant/Spring integrations across 60+ databases. Downloaded 100M+ times.
The enterprise edition (formerly Liquibase Pro). Policy checks, drift detection, structured logging, targeted rollback, and audit-ready compliance reporting.
Schema management, change history, and policy enforcement inside the editor - developers ship safely without leaving their IDE.
Turns plain-English descriptions into production-ready Liquibase XML, powered by a new Liquibase MCP Server.
Governed schema change management brought to Databricks SQL and the Lakehouse, via a 2025 partnership.
Extends governed change into ServiceNow, GitHub, Harness, and Terraform through orchestration APIs, plus AWS Marketplace distribution.
Liquibase's commercial pull is strongest in regulated industries - banking, insurance, and government - where a bad schema change costs money and a compliance finding. "Auditable" is not a nice-to-have there; it is a line item.
The competitive field includes Redgate's Flyway, DBmaestro, and, most often, hand-rolled in-house migration scripts. Liquibase's edge is neutrality: one changelog format that speaks to 60+ platforms, so a team standardizes once instead of per database.
The free engine seeds adoption in every corner of the industry; revenue comes from Liquibase Secure subscriptions sold to organizations that need policy enforcement, drift detection, and audit trails. Third-party estimates put annual revenue near $7M, on roughly $27M raised across seed through a 2019 Series C, from investors including Mercury Fund, S3 Ventures, and Scaleworks.
Nearly 20 years of continuous work on database change has produced deep SQL-parsing know-how - some of it patented - and a Java engine that runs cross-platform against dozens of database dialects. The company's advantage is durability: it has solved the same unglamorous problem better than anyone else, for longer.
Nathan Voxland creates and releases the Liquibase change management library.
An Austin company forms to build enterprise products and support around Liquibase.
Datical closes its first outside round to commercialize the platform.
A $10M Series C brings total funding to roughly $27M.
Datical adopts the name of its open-source project and introduces a tiered product model.
New enterprise edition, VS Code extension, AI Changelog Generator, and a Databricks partnership.
Wrote and open-sourced Liquibase in 2006.
Co-founded Datical / Liquibase.
Co-founded Datical / Liquibase.
The company's stated mission is "to accelerate global innovation by uniting teams across the data journey." Internally it runs on six principles - delight customers with surprises, pursue excellence while accepting imperfection, operate with urgency, keep a growth mindset, engage in difficult conversations, and align actions with the mission. In 2025 it expanded operations across EMEA and APAC.
“Fast database change. Fluid delivery. Radical team.”
It tracks, versions, and applies database schema changes across environments using changelogs, bringing CI/CD-style automation, review, and rollback to the database.
Yes - Liquibase Community is free and open source, downloaded over 100 million times. Liquibase Secure is the paid enterprise edition with governance, security, and compliance features.
More than 60 platforms, including PostgreSQL, Oracle, SQL Server, MySQL, Snowflake, and Databricks, all through a single changelog format.
Changes can be written in XML, YAML, JSON, or plain SQL, and each change is tracked by an "id" and "author" tag.
No. The company was founded as Datical in 2012 and rebranded to Liquibase in 2020, adopting the name of its widely used open-source project.