New capabilities aim to help enterprises reduce downtime risk, accelerate issue resolution, and extend governed database change into the tools teams already use
As AI accelerates the pace of software delivery, the database layer is feeling the pressure — and for many enterprises, it remains the weakest link in the governance chain. Liquibase, which positions itself as the leader in Database Change Governance, is looking to close that gap with two significant new innovations under its Liquibase Secure platform.
Introducing Change Intelligence
The first is Liquibase Change Intelligence, a new capability designed to give engineering, DBA, and compliance teams a unified view of database change activity across environments. Rather than piecing together what happened from scattered logs, ticket attachments, and tribal knowledge, Change Intelligence combines deployment activity, drift signals, policy outcomes, and operational history into a single, coherent picture.
When something goes wrong, the platform uses AI-driven analysis to surface likely causes and provide remediation guidance — with the goal of helping teams resolve issues up to 95% faster than traditional investigation methods.
Beyond incident response, Change Intelligence is also designed to centralize audit evidence, capturing what changed, who approved it, where it ran, and what the outcome was. That kind of structured, accessible record matters increasingly to security and compliance teams who can no longer afford to rely on screenshots and manual evidence gathering.
“Teams should not have to piece together the lineage of a database across environments from scattered logs, tickets, and tribal knowledge,” said Pete Pickerill, co-founder of Liquibase. “Change Intelligence is designed to help teams understand what changed, spot risk earlier, and move faster with AI-driven analysis and remediation guidance when failures happen.”
New Connectors for ServiceNow, GitHub, Harness, and Terraform
The second major announcement is a new suite of Liquibase Secure Deployment Connectors, built to bring governed database change directly into the platforms enterprise teams already rely on — without requiring them to rebuild existing workflows.
The four new connectors address different parts of the enterprise delivery stack:
- ServiceNow — Connects database change to existing approval processes, so that approved tickets result in governed, auditable deployments rather than manual SQL handoffs.
- GitHub — Integrates database change into the pull request and workflow model already used for application code, adding policy checks, validation, and deployment history tied to commits and branches.
- Harness — Preserves existing CI/CD pipelines while layering in stronger governance, visibility, and compliance-grade auditability around database changes.
- Terraform — Extends infrastructure-as-code practices to the database layer, connecting Liquibase Secure to Terraform-managed instances with versioned changeSets and a complete audit trail.
“CIOs are asking for flexibility without more fragmentation,” said Mirek Novotny, Senior Director of Product at Liquibase. “They want solutions that fit the way teams already work, support the breadth of their database environments, and still create a consistent standard for governance. That is exactly what these innovations are designed to deliver.”
Why This Matters Now
The timing is deliberate. AI is generating and pushing more changes through delivery systems at higher speed and greater scale — but when database change remains inconsistent or poorly governed, that risk doesn’t stay contained at the database layer. It ripples into applications, analytics, and AI-driven systems that depend on trustworthy data.
Liquibase’s pitch to CIOs is straightforward: better database change governance isn’t just an operational improvement — it’s foundational infrastructure for AI readiness.
Availability
Liquibase Change Intelligence, the Liquibase Secure Deployment Connectors, and related capabilities are expected to begin rolling out in fall 2026. Additional details will be shared closer to availability.
