Database change is no longer just an execution problem. It has become a visibility gap, a governance challenge, and an increasing source of operational risk.

Teams have far more mature ways to design, build, deliver, and track application code and infrastructure. But database change still too often runs through ticket attachments, manual approvals, disconnected logs, and one-off SQL execution. Evidence and audit trails have to be stitched together after the fact, and when teams need answers most, that fragmentation creates friction.

What changed? Where did it fail? Which environments are out of sync? What drifted? What evidence do we have? How do we fix it?

Those questions are getting harder to answer at exactly the wrong time. Release velocity is increasing, database estates are becoming more complex, data products are becoming more business-critical, and AI initiatives are raising the cost of inconsistent, weakly governed change at the database layer.

That is why we are introducing two major innovations in Liquibase Secure: Change Intelligence and Deployment Connectors for ServiceNow, GitHub, Harness, and Terraform.

These innovations solve different parts of the same problem. Change Intelligence gives teams a better way to understand database change, identify risk earlier, and triage failures faster. Deployment Connectors give teams a better way to operationalize governed database change inside the systems they already use. Together, they mark an important step forward in how enterprises understand, govern, and operationalize database change.

‍

Change Intelligence: A clearer way to see what changed and what to do next

It is not enough for database changes to run. Teams need to understand what changed, where risk is building, and what needs attention next.

That is the role of Change Intelligence.

Change Intelligence is designed to help teams understand database changes across environments, monitor delivery performance, identify risk earlier, resolve issues faster, and automatically capture audit evidence in one place. It brings together deployment activity, environment-level change status, drift signals, policy outcomes, and operational history so teams can move from scattered signals to a clearer picture of what is happening across the database layer.

This matters because database delivery rarely breaks in neat, isolated ways. A failed deployment can look like a broken release. Drift can sit unnoticed until an environment mismatch causes downstream issues. A routine audit question can trigger a scramble across tickets, logs, screenshots, and tribal knowledge. The problem is not that teams lack data. The problem is that the data is fragmented, hard to interpret, and difficult to use when speed matters.

Change Intelligence changes that equation. It is designed to give teams one place to understand what changed, how those changes are moving across environments, where operational exposure is expanding, and what requires attention next. It is also designed to help teams investigate failures with greater speed and context through AI-driven analysis and remediation guidance. Instead of manually reconstructing the story from disconnected logs and operational breadcrumbs, teams get a more direct path from issue to understanding to action.

That changes the operating model for database delivery. Database change is no longer just something teams execute and hope they can explain later. It becomes something they can monitor, triage, and govern with far greater clarity.

It also changes the audit conversation. Change Intelligence is designed to automatically capture and centralize audit evidence for what changed, who approved it, where it ran, and what happened across the delivery lifecycle. That gives engineering, security, and compliance teams a more structured and accessible record of database change activity without the usual screenshots, manual evidence gathering, and fragmented reporting.

The result is not just more visibility. It is a more usable layer of intelligence for database delivery, helping teams see where the database estate is under pressure and what needs attention next.

‍

‍

Deployment Connectors: Governed database change in the systems teams already use

Understanding database change more clearly is one part of the challenge. Operationalizing governance inside real enterprise workflows is the other.

That is where Deployment Connectors come in.

We are introducing new connectors for ServiceNow, GitHub, Harness, and Terraform to extend governed database change into the systems many teams already rely on to plan, approve, provision, and deliver work.

This matters because one of the biggest barriers to stronger database governance is not intent. It is workflow friction. Most organizations do not want to replace the systems their teams already know. CIOs want flexibility without more fragmentation. 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 connectors are designed to deliver.

With ServiceNow, teams can bring database change into the existing system of record for approvals and change management. ServiceNow continues to manage requests, approvals, and process controls. Liquibase Secure turns those approved changes into governed, auditable deployments, replacing manual SQL execution and disconnected handoffs with a more consistent and traceable path to production.

With GitHub, teams can bring database change into the same pull request and workflow model already used for application code. GitHub remains the system of record for source control, collaboration, and code review. Liquibase Secure adds policy checks, validation, deployment history, and database-specific governance tied to commits and branches, giving teams a more consistent way to review, promote, and audit database change alongside application change.

With Harness, teams can preserve the pipelines they already use while adding stronger governance, centralized visibility, and compliance-grade auditability around database changes. Harness remains the orchestration layer for pipeline execution and delivery flow. Liquibase Secure becomes the database execution engine, governance authority, and intelligence layer, bringing policy enforcement, drift visibility, change history, and deeper analytics into the process without forcing teams to change how they work.

With Terraform, teams can extend infrastructure as code to the database layer in a way that keeps responsibilities clear. Terraform provisions and configures database infrastructure. Liquibase Secure connects to those Terraform-managed instances through existing pipelines, enforcing database policies, applying versioned changeSets, and maintaining a complete audit trail of how each database evolves over time. Terraform remains the source of truth for infrastructure, while Liquibase Secure becomes the source of truth for database change.

That distinction matters. ServiceNow manages process. GitHub manages source and collaboration. Harness orchestrates delivery. Terraform provisions infrastructure. Liquibase Secure governs database change across all of them, bringing policy enforcement, traceability, audit evidence, and change intelligence into the workflows teams already use. Across those workflows, Liquibase Secure supports more than 65 database platforms, helping enterprises standardize governance without sacrificing flexibility.

The goal is not to force teams into a new process for the sake of process. The goal is to extend governed database change into the systems teams already use, while strengthening traceability, standardization, and audit evidence across the delivery lifecycle.

That is a meaningful shift because, for years, organizations have had to choose between flexibility and consistency, between meeting teams where they are and enforcing stronger governance, and between moving fast and creating a record that stands up to operational scrutiny. Deployment Connectors are designed to reduce that tradeoff.

‍

Why these two innovations belong together

Change Intelligence and Deployment Connectors are not separate stories. They are two essential parts of a platform approach to deliver database change governance.

One helps teams understand database change more clearly. The other helps teams operationalize governed database change where work already happens. One closes the gap between signal and understanding. The other closes the gap between governance and execution.

Together, they help enterprises move toward a better way of managing database change, not as a series of one-off exceptions and not as a manual process sitting outside modern delivery, but as a governed, observable, auditable part of how software and data actually move.

That is why this matters beyond the product announcement itself. It points to where database change management is headed. Not just more automation, but more understanding, more accountability, more usable evidence, and more governance inside real workflows.

‍

Why this matters even more in the age of AI

As AI initiatives expand, more changes are being generated, reviewed, and pushed through delivery systems at higher speed and greater scale. That raises the stakes.

AI systems depend on data that is accurate, consistent, and well governed. When database change remains inconsistent, weakly governed, or hard to trace, the risk does not stay isolated at the database layer. It carries into applications, analytics, automation, and AI-driven systems.

This is why database change needs a stronger operating model now. Teams need a better way to understand what changed, investigate failures and drift, create and access audit evidence, and do all of that without forcing developers, DBAs, platform teams, and change teams to abandon the systems they already use.

That is what these innovations are designed to deliver. By helping organizations understand database changes more clearly, catch risk earlier, resolve issues faster, centralize audit evidence, and extend governed database change into existing workflows, Liquibase Secure is creating a stronger operational foundation for data integrity, operational accountability, and reliable AI initiatives.

‍

What’s next

Change Intelligence and Deployment Connectors represent an important next step for Liquibase Secure and for the teams responsible for keeping database delivery fast, controlled, and auditable.

If your team is focused on improving visibility, reducing delivery risk, strengthening audit readiness, or bringing more consistency to database change without adding more workflow friction, this is where to start.

Explore each innovation here:

• ‍Change Intelligence
• Deployment Connectors

The next phase of database change will not be defined by execution alone. It will be defined by how well teams can understand change, govern it, and operationalize it at enterprise scale. That is what’s next for Liquibase Secure.

Register for the April 22nd webinar to see how it works live.

*** This is a Security Bloggers Network syndicated blog from Liquibase: Database DevOps authored by Liquibase: Database DevOps. Read the original post at: https://www.liquibase.com/blog/whats-next-for-liquibase-secure-change-intelligence-and-new-deployment-connectors