Database change governance vendor gives Snowflake shops a way to standardize deployments, catch drift, and burn down committed capacity in the process
As more enterprises pour their most important workloads into Snowflake, a quiet problem tends to follow them: the way changes get made to the platform hasn’t always kept up with how much depends on it. Liquibase, which positions itself as the leader in Database Change Governance, is aiming to close that gap. The company announced that Liquibase Secure is now available on the Snowflake Marketplace.
Change in Snowflake Goes Well Beyond Tables and Views
It’s easy to think of database change as adding a column or tweaking a view. In a modern Snowflake environment, the reality is much broader. Teams are modifying roles, shares, stages, warehouses, tasks, and other objects that determine who can access data, how it moves, and how it’s used.
That expanded scope raises the stakes considerably. Yet in many organizations, the processes behind those changes still lean on manual SQL scripts, direct edits in production, and workflows that don’t talk to each other. Add more teams, more environments, and more business-critical workloads, and those habits become progressively harder to control.
What Liquibase Secure Brings to the Table
Liquibase Secure is designed to pull all of that activity into a standardized, version-controlled delivery process. Rather than replacing the tools teams already rely on, it plugs into existing CI/CD and DataOps pipelines and adds a governance layer on top. According to the company, Snowflake customers can use it to:
- Automate delivery: Push changes through version-controlled workflows tied into current CI/CD and DataOps practices.
- Block risky changes early: Apply automated policy checks that enforce organizational standards before anything reaches production.
- Spot drift: Identify out-of-band changes and flag when an environment no longer matches its expected state.
- Stay audit-ready: Keep a traceable record of what changed, when, and how it was deployed.
- Recover faster: Rely on traceable, reversible changes and rollback procedures when a deployment goes wrong.
The pitch here is consistency. Instead of each team inventing and maintaining its own change process, organizations get a single governed path to production, while existing development, infrastructure, and DataOps tools keep doing what they were built to do.
Snowflake’s Perspective
Snowflake is clearly on board with the direction. “As organizations expand their use of Snowflake across critical data and AI initiatives, strong governance controls and operational consistency become top priorities,” said Rodrigo Rocha, Vice President, Global ISV & Enterprise Technology Partnerships at Snowflake. He added that Liquibase Secure’s availability on the Snowflake Marketplace gives customers another way to govern changes within their Snowflake environments.
Buying Made Simpler with Capacity Drawdown
There’s a practical procurement angle, too. Liquibase Secure is available now on the Snowflake Marketplace, and eligible customers can apply Marketplace Capacity Drawdown toward their purchase. In plain terms, that lets them use a reserved portion of their existing committed Snowflake capacity for eligible Marketplace buys, which can smooth budgeting and streamline purchasing.
One Approach Across a Mixed Database Estate
Few enterprises run on a single database technology, and Liquibase is betting that matters. Liquibase Secure supports more than 65 database platforms, so organizations can apply the same Database Change Governance approach to Snowflake and the rest of their database landscape rather than stitching together separate processes for each.
The Bottom Line
Data platforms are becoming the foundation for analytics and AI, and the cost of an uncontrolled change is rising accordingly. By putting Liquibase Secure in front of Snowflake customers through the Marketplace, and letting them pay with committed capacity, Liquibase and Snowflake are lowering the barrier to bringing discipline to a part of the data lifecycle that too often runs on ad hoc scripts and good intentions.
