The IT Nerd

Liquibase today announced a major expansion of its global partner ecosystem and the appointment of Phil Robinson as Vice President of Global Channels and Alliances. The move builds on strong momentum for Liquibase Secure and growing enterprise demand for governed database change as AI, modernization, security, and compliance reshape software delivery.

Robinson brings more than two decades of channel, alliance, and enterprise open-source experience to Liquibase. Most recently, he served as Vice President of Global Channels at Digital.ai, where he helped redesign and relaunch the company’s channel program globally. Before that, he spent more than eight years at Atlassian, where he built and scaled global alliance programs with GSIs and Federal SIs, including Accenture, Deloitte, PwC, and Capgemini. His experience also includes leadership roles at Magento, Alfresco, and Hewlett Packard Enterprise across open source, cloud, systems integration, and enterprise software.

Trusted by 20 of the Fortune 100 and supported by a global community with more than 100 million downloads, Liquibase is investing in partners to help enterprises close the database delivery gap and build new services around Database Change Governance.

Robinson will lead Liquibase’s global partner strategy across partner recruitment, enablement, joint marketing, and partner-led services around Database Change Governance, while deepening the company’s engagement with cloud marketplaces and government partners.

AI is exposing the database delivery gap

Modern application and data delivery has accelerated in waves. Agile increased release velocity. Cloud spread applications, databases, and data platforms across more teams, tools, and environments. Enterprises responded by investing in CI/CD, automated testing, infrastructure-as-code, and security controls. But database change often remained governed through tickets, manual reviews, disconnected scripts, and processes that varied across teams, tools, and database platforms.

That disconnect has made the database one of the last major constraints on modern application and data delivery. Application code, infrastructure, and security increasingly move together, while database change is still treated as a separate process in many organizations. The result is fragmented governance, slower releases, and limited visibility into what changed, who approved it, and whether it is safe to deploy.

AI is not creating the database delivery gap. It is exposing it. As AI assistants and agents generate more software, they also increase the volume and speed of database change flowing through delivery systems that were never designed to operate at that scale. The challenge is no longer simply automating deployments. It is keeping database change synchronized with application code, infrastructure, and security before it reaches production.

The governance gap is widening. According to Liquibase’s 2026 State of Database Change Governance Report, 96% of organizations now have AI interacting with production databases, and 70% ship database changes weekly or faster. Yet only 28% enforce governance through automated controls and evidence, while 39% say they cannot reliably track what changed where.

For partners, this represents a significant opportunity to help customers modernize database delivery, govern AI-assisted development, strengthen compliance, reduce production risk, and bring database change into the same DevSecOps practices already established for application code. As enterprises look to scale AI safely, they need partners who can help modernize the processes that AI is exposing as bottlenecks.

Database Change Governance provides the control plane that keeps database change synchronized with application code, infrastructure, and security across the software delivery lifecycle. Liquibase Secure operationalizes that control plane across development teams, CI/CD pipelines, AI agents, and more than 65 database platforms, enabling enterprises to accelerate software delivery without sacrificing governance.

Why this is a partner opportunity now

For partners, this shift is a chance to become indispensable to their most complex customers. As database change outruns the ability to govern it, enterprises need a partner who can restore control at the exact point where developer velocity, compliance, and AI readiness collide. Liquibase provides an opportunity for partners to turn that challenge into a repeatable practice spanning advisory, implementation and managed services, reaching every environment a customer runs, from mainframe to cloud to lakehouse.

At the center of the opportunity is Liquibase Secure, which helps enterprises automate, secure, and govern database change across complex environments. With policy checks to deliver standardized change, advanced drift detection, structured audit trails, always-on evidence gathering, and more, Liquibase Secure gives developers, platform teams, security leaders, and compliance teams a governed path for every database change.

Liquibase already works with a robust group of consulting, cloud, public sector, and technology partners. Under Robinson’s leadership, the company plans to expand partner coverage both geographically and into specific industry sectors, creating clear paths for partners to build solutions and deliver Liquibase Secure, Database

Organizations interested in joining the Liquibase partner ecosystem can learn more at liquibase.com/partners.

Today, Liquibase is proud to release the open source Liquibase CVE Library (Common Vulnerabilities and Exposures Library) to foster security and transparency across the Liquibase Community. The free, publicly available library helps users of older versions of Liquibase Community identify existing vulnerabilities and get a clearer sense of their security posture. By tying vulnerability data directly to Liquibase releases, the CVE Library helps teams see their risk exposure, compare versions, and take informed action to secure the software they run.

Attackers need only to find a single exploit to breach a network and IT infrastructure, making comprehensive CVE libraries increasingly invaluable to security teams seeking to stay ahead of Mythos-class threat capabilities by patching all known weaknesses before they can be targeted.

To date, the Liquibase Community project has been downloaded over 100 million times.

How does the Liquibase CVE Library work?

Every time Liquibase ships a new release, automated security scanning tools analyze both the Docker image and the Liquibase binary for known vulnerabilities. Scanning also runs against previously published images, maintaining an up-to-date view of the evolving threat landscape and catching anything that surfaces post-release. The site organizes everything by image and version. You can see a high-level security grade and CVE counts for the latest release, drill into any specific version for the full vulnerability list, or use the comparison tool to see exactly which CVEs were resolved, or introduced, between two releases.

Which environments are supported?

• Docker images: The official Liquibase Community Docker image.
• Liquibase binary: Vulnerabilities in the Liquibase JARs themselves, regardless of how you install it.

What you’ll see

For each vulnerability, the CVE Library shows:

• CVE ID, Severity, and CVSS score: Presented with clear information and links to learn more.
• Affected package: The specific details needed to understand what is vulnerable.
• Fix available: The package version that resolves it, if one exists; and where applicable, the first Liquibase image version where the CVE no longer appears.
• Component type: Additional vulnerability details to help understand the risk.
• First-party vs. third-party: Whether the vulnerability is in Liquibase’s own code or an upstream dependency.

The full list is filterable by severity, component type, and keyword search, and can be exported as CSV or PDF. (Please also see figures with press release link on Business Wire, linked above.)

Part of a broader commitment to the Community

The CVE Library doesn’t stand alone. Since September of 2025, Liquibase has released a steady stream of enhancements and fixes for the Liquibase Community. Recently, in May of 2026, Liquibase standardized on two clear paths to updates: quarterly Community releases and continuous nightly builds on GitHub (available at github.com/liquibase/liquibase/releases/tag/nightly). The CVE Library now makes that ongoing work readily visible so users don’t have to just trust that issues are being addressed, they can see it, release by release.

For teams that need enterprise assurance

The Liquibase CVE Library gives Community users clear visibility into known vulnerability exposure. For organizations running Liquibase in regulated, mission-critical, AI-enabled, or enterprise production environments, visibility is often the first step. Liquibase Secure provides a fully supported enterprise distribution with SLA-backed support, tested components, policy checks, drift detection, structured audit logs, and governance controls for teams that need to reduce risk while maintaining delivery velocity.

Take a look and get involved

The Liquibase Community thrives because people around the world step up to contribute. Here’s how to get in touch and take part:

• Explore the CVE Library today at https://cve-library.liquibase.com.
• Ask questions or start a discussion on the Liquibase Forum.
• Report a bug or request a feature in the GitHub issue tracker at github.com/liquibase/liquibase.

Liquibase today announced Liquibase Secure 5.2, a major release introducing Agent Safe Governance for AI-generated database change. Liquibase Secure 5.2 helps enterprises validate, track, and govern database change before and after production, whether created by humans or AI.

Liquibase also announced that Liquibase Secure earned five 2026 TrustRadius Top Rated Awards across Database DevOps, Build Automation, Release Management, Database Management, and Version Control. TrustRadius Top Rated Awards are based entirely on customer reviews, with no paid placement or analyst opinion, and recognize products that meet criteria for review recency, customer rating, and category relevance.

Companies are moving faster across applications, infrastructure, data products, and AI initiatives. But every application, data product, and AI model still depends on database change. That creates a new pressure point: database changes can now be generated in seconds, while many enterprise controls still rely on tickets, manual reviews, disconnected scripts, and after-the-fact audit trails.

According to Liquibase’s State of Database Change Governance report, 96% of organizations allow AI to interact with production databases. As tools such as Cursor, Claude, GitHub Copilot, and other AI assistants become part of the developer workflow, database changes are no longer created only by humans. But faster creation does not mean those changes are safe to deploy.

Agent Safe Governance is Liquibase’s answer to that shift. AI can help create a database change, but it cannot bypass the checks, approvals, audit trails, schema lineage, drift detection, and recovery controls enterprises require before production.

AI is changing how database changes are created. Liquibase Secure governs how they reach production.

“AI agents are becoming part of how developers work, but they should not have a free pass to change production databases,” said Pete Pickerill, Co-Founder at Liquibase. “Agent Safe Governance means AI can help create a database change, while Liquibase Secure validates it, tracks it, checks it against policy, preserves schema lineage, detects drift, and controls how it moves to production. That is the balance enterprises need: faster development without turning database change into an unmanaged risk surface.”

Liquibase Secure 5.2 uses the Liquibase MCP server to connect AI-assisted workflows to govern database change management. Developers and AI assistants can create Liquibase-formatted changelogs, schema updates, rollback logic, and AI-generated DDL, while Liquibase Secure applies policy checks, governance workflows, drift detection, and audit-ready evidence before changes reach production.

Liquibase Secure 5.2 Brings Agent Safe Governance to the Database Layer: Liquibase Secure 5.2 gives enterprises one control plane for every database change, human or AI. The release connects new AI-assisted workflows with the proven governance controls enterprises already rely on to validate, track, and secure database change.

AI-assisted database change authoring through the Liquibase MCP server: The Liquibase MCP server connects AI-assisted workflows to Liquibase Secure, helping developers and AI assistants create structured, reviewable, and governed database changelogs, schema updates, rollback logic, and AI-generated DDL. AI can assist with authoring, but Liquibase Secure governs the path to production.

Change Intelligence and schema lineage for human and AI-generated change: Liquibase Secure gives teams visibility into the full lifecycle of every database change. Change Intelligence helps teams understand what changed, who or what created it, where it ran, whether controls were followed, how the schema changed over time, whether drift exists, and what evidence is available for audit or investigation.

Policy checks and drift detection as the governance foundation: Liquibase Secure applies policy checks before deployment to help teams block risky operations, enforce standards, support separation of duties, and validate compliance requirements. Drift detection helps identify when environments no longer match the approved database state, including manual updates, emergency fixes, shadow changes, or AI-assisted changes that bypass governed workflows.

Expanded enterprise database coverage: Liquibase Secure 5.2 deepens support for complex enterprise database estates with new capabilities for Teradata, MongoDB, and DynamoDB. These enhancements help teams extend governed change across the databases that power mission-critical applications, data products, and AI systems.

Machine-Readable Vulnerability Intelligence with VEX: Liquibase Secure 5.2 adds Vulnerability Exploitability eXchange, or VEX, support to provide machine-readable vulnerability assessments for Liquibase products. Published through the Liquibase VEX repository, included alongside SBOM files inside the Secure distribution, and available as standalone files on the Liquibase download site, VEX helps enterprise security teams understand vulnerability context, integrate with automated scanners, and streamline security response.

One Control Plane. Every Database. Every Change. Human or AI. Liquibase Secure 5.2 extends Liquibase’s role as the enterprise control plane for database change. It helps organizations govern database change across human developers, AI assistants, CI/CD pipelines, and production environments.

For regulated industries, this is already a board-level issue. Financial services, healthcare, insurance, retail, media, and technology organizations must prove that database changes are reviewed, approved, traceable, recoverable, and compliant. AI does not remove that requirement. It raises the stakes.

With Liquibase Secure 5.2, enterprises can move from reactive database control to continuous governance, with one consistent way to manage database change across applications, data products, and AI systems.

Liquibase Secure’s five 2026 TrustRadius Top Rated Awards reinforce the same customer demand driving this release: database change needs to move faster, stay governed, and remain trusted across increasingly complex enterprise environments.

Availability

Liquibase Secure 5.2 is available now. Learn more about Agent Safe Governance and Liquibase Secure 5.2.

Liquibase today announced The Financial Services Playbook for Governed Database Change, a new executive guide designed to help financial institutions modernize and secure one of the last major control gaps in enterprise technology delivery: database change.

Built for CIOs, CTOs, platform engineering leaders, database architects, and compliance teams, the playbook examines how banks, insurers, payment processors, fintechs, and capital markets firms continue to face a growing governance gap between highly automated application delivery pipelines and still-manual database change processes.

Field research for the Playbook was conducted across hundreds of financial services engagements spanning enterprise banks, regional institutions, credit unions, global insurers, payment processors, fintechs, and capital markets firms.

Among key findings:

• The problem is universal. Manual database change execution is the industry baseline, not a maturity problem at lagging organizations.
• Compliance is the accelerant. SOX, PCI DSS, SOC 2, and DORA are driving purchase decisions. When auditors flag deficiencies, budget materializes.
• The DBA bottleneck is structural. Executive mandates to remove DBA involvement from routine changes are appearing at the largest institutions.
• The proven path is pilot, platform, enterprise. Start with two to five applications, build the pipeline through platform engineering, then scale.
• Multi-database reality is the baseline. Oracle, SQL Server, PostgreSQL, Snowflake, DynamoDB, Databricks. Partial coverage is not governance.

Organizations that close this gap deliberately will set the standard. The rest will be forced to catch up by their auditors, their regulators, or a production incident.

Drawing on field research from hundreds of financial services engagements, the playbook argues that manual database change execution remains the industry norm, even at highly mature institutions. It outlines how mounting regulatory scrutiny from frameworks including SOX, PCI DSS 4.0, SOC 2, DORA, and emerging operational resilience requirements is accelerating demand for governed database delivery pipelines.

The playbook also addresses a growing concern around AI adoption in software delivery.

Liquibase recently explored that emerging threat in its analysis: Banks Focus on AI Models. Mythos Class Attackers Focus on Your Databases.

Rather than focusing narrowly on tooling, the playbook walks readers through the operational realities financial institutions face today, including DBA bottlenecks, fragmented deployment tooling, audit evidence reconstruction, schema drift, and growing separation-of-duties concerns.

The guide also details a practical maturity path for organizations seeking to modernize database governance.

• The governance gap: why database delivery remains structurally different from application delivery
• How governance failures create operational, audit, and regulatory exposure
• The evolving role of DBAs, platform engineering, and compliance teams
• An eight-principle target operating model for governed database change
• A phased rollout strategy covering pilot, platform, and enterprise adoption
• A framework for evaluating build-versus-buy governance approaches
• Metrics financial leaders can use to justify modernization investments
• The impact of AI-generated SQL and hybrid cloud database environments on governance strategy

TL;DR: FinServ Operational Resilience Is At Risk

Manual database change execution is throttling data security and is the FinServ industry baseline, not a maturity problem at slow-adopter organizations.

Organizations that embed governance directly into database delivery pipelines now will gain operational resilience and regulatory advantages. Institutions that delay modernization risk being forced into reactive remediation by data loss or corruption incidents, by audit pressures, and by competitive market forces.

The executive summary of The Financial Services Playbook for Governed Database Change is available now from Liquibase: https://www.liquibase.com/resources/ebooks/financial-services-playbook-for-governed-database-change

Liquibase today unveiled Liquibase Change Intelligence and a new suite of Liquibase Secure Deployment Connectors, expanding how enterprises understand, govern, and operationalize database change across modern delivery environments.

The new capabilities are designed to help teams understand database changes, monitor delivery performance, identify risk earlier, resolve issues up to 95% faster, and centralize audit evidence, while extending governed database change into the systems where developers, DBAs, and change teams already work, including ServiceNow, GitHub, Harness, and Terraform.

The announcement addresses a persistent gap in enterprise delivery. While application and infrastructure changes have become more automated, observable, and standardized, database change still too often moves through ticket attachments, side-channel SQL, manual approvals, and inconsistent execution paths. The result is slower investigations, weaker auditability, and more risk around outages, data integrity, and compliance.

Change Intelligence helps teams see what changed and respond faster

Liquibase Change Intelligence is designed to give teams a clearer view of what changed, how changes are moving across environments, where drift is emerging, and what requires attention next.

It brings together deployment activity, environment-level change status, drift signals, policy outcomes, and operational history so teams can answer critical questions faster: What changed? Where did it fail? Which environments are out of sync? Is drift increasing? What needs to be fixed now?

When failures occur, Change Intelligence is designed to help teams investigate with greater speed and context through AI-driven analysis that identifies likely causes and provides remediation guidance. Instead of forcing teams to reconstruct events from scattered logs, tickets, and tribal knowledge, it gives them a more direct path from issue to understanding to action.

Change Intelligence is also designed to help organizations centralize audit evidence for what changed, who approved it, where it ran, and what happened. That gives engineering, security, and compliance teams a more structured and accessible record of database change activity, reducing reliance on screenshots, manual evidence gathering, and fragmented reporting.

New connectors extend governed database change into the tools teams already use

Liquibase also unveiled a new suite of Liquibase Secure Deployment Connectors designed to extend governed database change into the platforms many enterprises already use to plan, approve, and deliver work.

For teams using ServiceNow, the connector is designed to bring database change into the existing approval process so approved tickets can result in governed, auditable deployments instead of manual SQL execution and disconnected handoffs.

For teams using GitHub, the connector is designed to bring database change into the same pull request and workflow model already used for application code, adding policy checks, validation, and deployment history tied to commits and branches.

For teams using Harness, the connector is designed to preserve existing pipelines while adding stronger governance, centralized visibility, and compliance-grade auditability around database changes.

For teams using Terraform, the connector is designed to extend infrastructure as code to the database layer, connecting Liquibase Secure to Terraform-managed instances through existing pipelines while enforcing database policies, applying versioned changeSets, and maintaining a complete audit trail over time.

Together, the connectors are designed to remove one of the biggest barriers to stronger database governance: the belief that teams need to rebuild their workflows to get it. Instead, Liquibase is extending governed database change into the systems teams already use, while strengthening traceability, standardization, and audit evidence across the delivery lifecycle.

Built for a new era of AI, data integrity, and operational accountability

The new capabilities reflect a broader shift in how enterprises are thinking about AI readiness and operational risk.

As AI initiatives expand, more changes are being generated, reviewed, and pushed through delivery systems at higher speed and greater scale. But when database change remains inconsistent, weakly governed, or hard to trace, the resulting risk does not stay isolated at the database layer. It carries into applications, analytics, automation, and AI-driven systems.

By helping organizations better understand database changes, catch drift earlier, investigate failures faster, and centralize audit evidence, Liquibase is giving enterprises a stronger operational foundation for trusted applications, data products, and AI initiatives.

Availability

Liquibase Change Intelligence, Liquibase Secure Deployment Connectors, and related capabilities are expected to begin rolling out in fall 2026. Additional details will be shared closer to availability.

Liquibase, the leader in Database Change Governance, today released the 2026 State of Database Change Governance Report, new research on how enterprises are managing database change as AI becomes embedded across production systems, analytics, and delivery pipelines. The report finds that AI interaction with enterprise databases is now widespread, while governance automation and consistent enforcement have not kept pace with the speed and scale of change. (The report and graphic are linked at bottom.)

For CIOs, the issue is not that AI touches production data. The issue is whether the organization can prove control at the database layer when change is frequent, environments are heterogeneous, and AI introduces new pathways for change and access. At AI scale, manual governance struggles to keep up. That is where risk compounds and then surfaces as data quality failures, audit friction, and outcomes leaders cannot explain.

Key survey findings:

• AI interaction: 96.5% of respondents report at least one AI or LLM interaction with their production databases, including analytics and reporting, training pipelines, internal copilots, and AI-generated SQL.
• Change velocity: 68.1% deploy database changes weekly or faster, including 10.8% deploying multiple times per day and 18.8% deploying daily.
• AI-era risk: 64.3% cite data quality issues as a top AI-related risk, and 46.5% cite ungoverned AI-generated SQL as a key concern.
• Estate complexity: Organizations report an average of five database and data platform types, and 29.1% manage ten or more database types.
• Governance gap: Only 28.1% report database change governance that is standardized and consistently enforced, while 42.3% remain at Ad hoc or Emerging. Only 7.7% report fully automated governance using policy as code with real-time enforcement.
• Audit pressure compounds the challenge. The report finds 95.3% of respondents undergo multiple compliance or database audits per year, with more than one in five facing seven or more audits annually.

The report highlights a widening operating gap. Enterprises are shipping database change continuously across diverse platforms, while governance often depends on documentation, manual review, and fragmented evidence. In an AI era, those approaches do not scale. As AI automations and AI-generated changes increase, the cost of inconsistent enforcement rises, and the blast radius of a single unmanaged change expands across downstream analytics and AI systems.

What customer behavior telemetry shows at AI scale:

Anonymized Liquibase Secure product telemetry, separate from the survey results, reveals the following.

• Governance is the default: 99.25% of Liquibase Secure sessions run with governance enabled, a necessary baseline as AI increases the volume of proposed change.
• Standardization enables automation: Nearly 86% of observed changelog activity is in XML and YAML, supporting machine-readable change definitions that AI-scale delivery can validate and enforce.
• Controls must exist before CI: About 90% of sessions run outside CI, reinforcing that as AI accelerates change, governance has to shift left into the developer workflow.
• Adoption starts with proof: Reporting is among the most exercised capabilities, reflecting early demand for audit-ready traceability as AI makes decisions harder to defend without evidence.

A practical roadmap and scorecard for CIOs

Beyond the survey findings, the report provides a staged operating model for moving from ad hoc database change to standardized, enforced, and observable governance, without slowing delivery. It also introduces a CIO-ready scorecard that pairs reliability metrics (MTTD and MTTR) with coverage metrics for automated controls, audit evidence, and AI-governed change, so leaders can measure progress and risk reduction over time.

Here’s a link to a summary of the 2026 State of Database Change Governance Report.

Liquibase, the leader in Database Change Governance, today announced the release of Liquibase Secure 5.1, extending modeled Change Control to Snowflake. With 5.1, enterprises can govern Snowflake control plane changes with the same rigor and automation they already apply to schema evolution, closing a critical gap in data platform security, compliance, and AI readiness. Liquibase Secure 5.1 also expands database platform coverage, including new support for additional cloud and enterprise data stores.

Snowflake has become mission-critical infrastructure for analytics, data products, and AI initiatives. As organizations scale DataOps and internal developer platforms, Snowflake changes are no longer isolated technical updates. They are platform-level changes that impact trust, availability, and every downstream consumer. Yet many of the most consequential changes still happen outside standardized governance, often delivered as scripts with limited visibility, weak enforcement, and evidence that is difficult to assemble when it matters most.

Modeled Change Control for Snowflake

Liquibase Secure 5.1 treats key Snowflake control plane changes as first-class, modeled change types, rather than opaque scripts. That modeling enables precise policy enforcement, object-aware drift detection, and audit-ready evidence at the level where access, movement, and execution are defined.

With Liquibase Secure 5.1, data platform teams can govern Snowflake changes across access and security configuration, data sharing and movement, platform and cost controls, and automated execution, using standardized workflows across environments and teams.

Key outcomes include:

• Stop risky Snowflake control plane changes before they reach production
• Standardize how Snowflake changes are delivered across environments and teams
• Automatically generate audit-ready evidence for every change
• Detect drift and out-of-band updates to governed Snowflake objects
• Recover faster with traceable, reversible changes and tested rollback procedures

This closes a long-standing gap for organizations that govern schema evolution, yet still struggle with over-permission creep, ungoverned data movement, and control plane drift that can undermine security posture and AI initiatives.

Built for DataOps, data products, and AI readiness

As Snowflake increasingly powers feature engineering, model training, and AI-driven decisioning, the blast radius of ungoverned change grows. A single access change can expose sensitive training data. An unreviewed sharing update can expand compliance scope. An execution change can silently alter business-critical logic. Liquibase Secure 5.1 helps data platform teams keep Snowflake predictable, auditable, and reliable as usage scales, without turning governance into a bottleneck.

Expanding database support across Liquibase’s industry-leading coverage

Liquibase Secure continues to deliver broad database coverage across 60+ platforms, from mainframe DB2 to cloud-native data stores. Liquibase Secure 5.1 expands support for Snowflake, Databricks, and MongoDB, and adds new platform support for Couchbase, AWS Keyspaces, DataStax Enterprise, and AlloyDB for Google Cloud. This breadth helps enterprises standardize change governance across heterogeneous environments using a single platform instead of stitching together siloed tools and processes. Teams can apply consistent workflows and generate unified, audit-ready evidence across their database estate, reducing operational overhead while preserving the flexibility to adopt new technologies without rebuilding governance each time.

Enterprise partnership, not just tooling

Liquibase brings more than a decade of frontline experience helping enterprises govern database change at scale. In addition to the platform, Liquibase provides hands-on professional services, a dedicated customer success organization, and ongoing advisory support to help teams operationalize Change Control across their delivery model.

Availability

Liquibase Secure 5.1 is available now. To learn more about Change Control for Snowflake and Database Change Governance, visit liquibase.com.

Liquibase today announced fiscal year 2025 momentum driven by accelerating new customer demand, record Liquibase Community adoption, and continued operating discipline.

Late 2025 outages across major internet services were a reminder that change can cascade at scale into widespread disruption. As AI pushes more automation downstream, database changes increasingly require enforcement before production and evidence after release.

Database Change Governance is the enforcement and evidence layer for database change. It prevents risky changes from reaching production and produces proof of what ran, where, and when after release, so teams can ship faster without sacrificing control. Without it, a breaking schema change can ripple across applications, data products, and automated workflows.

FY25 momentum highlights

1. New ARR increased more than 85 percent year over year
2. Liquibase Community surpassed 15 million downloads in 2025
3. Liquibase launched Liquibase Secure and Liquibase 5.0 in FY25
4. Operating efficiency improved dramatically over the last few years, strengthening operating leverage and execution discipline.
5. Liquibase Secure won the 2025 DevOps Dozen Award for Best DevOps for DataOps and Database Solution
6. Liquibase was also named a finalist in three DevOps Dozen categories: DevSecOps, Database DevOps, and Mainframe Modernization
7. Expanded platform partnerships with Databricks and MongoDB to bring governed database change to modern data platforms and AI driven applications.

Liquibase also expanded its ecosystem partnerships to meet teams where database change is happening, inside modern data platforms and AI driven applications. In 2025, Liquibase partnered with Databricks to bring modern change management to the lakehouse and announced a strategic technology integration with MongoDB to bring governance to AI driven database changes.

Governance customers use in real delivery workflows

Liquibase Secure helps teams ship database change with guardrails and proof. Teams use Policy Checks to enforce policies before changes reach production, and Reports to generate audit ready evidence of what was applied, where, and when. Together, these governance capabilities integrate into automated deployments, reducing late stage surprises and making releases more predictable.

Customer feedback reinforces this. As one TrustRadius reviewer, a Senior Configuration Management Advisor, put it: “Liquibase fixes a problem everyone has but doesn’t know there’s an answer for.”

Industry recognition

Liquibase Secure was named the winner of the 2025 DevOps Dozen Award for Best DevOps for DataOps and Database Solution.

Leadership additions to scale the next phase

Liquibase strengthened its leadership team in FY25 to support product velocity, enterprise execution, and international growth.

1. David De Paula, VP International Sales, former VP Sales, EMEA and APAC at CloudBees
2. Mike Runco, VP Sales, North America, former VP of Sales at UnifyApps
3. Ryan McCurdy, VP of Marketing, former SVP of Marketing at Astronomer
4. Steve Surace, VP of Engineering, former VP of Engineering at Datto

Liquibase today announced that it’s opened the Liquibase 2026 Database Change Survey for IT community participation. The survey is designed for practitioners, leaders, and contributors across the applications/database ecosystem, from database administrators and developers to platform, security, and compliance teams.

This survey offers thee survey gives the readership community a voice and weigh-in opportunity on how database change governance is evolving and where the sector should focus next. The survey contains a total of 20 questions and will take about 5 minutes to complete. Respondents can provide their email for a chance to win AirPods Pro 3.

To participate, visit: https://www.liquibase.com/liquibase-2026-database-change-survey

Why This Matters to Readers: Last year’s report gathered insights from professionals across 25 countries and revealed a striking reality: fewer than 8% of organizations had achieved full DevOps maturity, while 29% remained in the early stages. The growing complexity of data environments continued to hold many teams back, and the rise of AI and ML has only intensified the challenge – 25% of immature organizations identified it as their top concern.

This year’s survey will reveal what’s changed in 2025 and help the global IT community identify emerging issues, understand their relevance to the reader’s particular organization, and assess the best practices needed to meet AI and ML challenges head-on.

Ryan McCurdy, VP with Liquibase, the leader in database DevOps, has just published “The Day a Database Permission Change Broke the Internet: A Cloudflare Story.” His analysis details how:

• A minor adjustment, routine in most organizations, touched a hidden part of Cloudflare’s architecture and awakened a dependency no one had considered dangerous.
• What happened next revealed how modern systems fail today: Nodes that loaded the expanded file went dark. Nodes that loaded the old file continued to serve traffic. The network oscillated, recovering for minutes at a time before failing again, as if trapped between two different realities.
• Once every shard of the ClickHouse cluster adopted new permissions, every file produced was oversized and every proxy that touched it entered the same panic.

The analysis details clearly and compellingly how the cascading failure occurred, and ways in which most data-driven organizations are at risk.

He notes:

“Cloudflare is one of the most capable engineering organizations in the world. Their systems are built to survive pressure that would overwhelm most companies. Their teams live in incident response. Their infrastructure is distributed, hardened, and instrumented with extraordinary detail. Yet the event that brought them down started with a quiet change in who could read what inside a database.”

He concludes by noting that the only real path forward is a new level of discipline at the data layer. Databases must be governed with the same rigor applied to application pipelines, and offers specific vendor-neutral recommendations.