Sold by: Liquibase
Liquibase helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. Without automation, CI/CD fails at the database.
4.4
Overview
Liquibase Pro on AWS is brought to you by the creators of Liquibase and is billed through your AWS account.
Liquibase delivers the repeatable process teams need to easily create, validate, trace, and audit database changes from development through production - reducing security risks and costly errors that often happen when manually making changes to the database.
Using Liquibase helps teams identify and resolve issues early in the process - when they are much cheaper and easier to fix.
For more information on pricing based on database targets, please visit https://www.liquibase.com/counting-database-connections .
Highlights
- Create, version, deploy, roll back, and track database changes throughout the CI/CD pipeline
- Empower developers to validate database code on-demand and within automation against predefined, customizable rules set by DBAs and security teams
- Protect your database against malware and ransomware with database drift detection alerts
Details
Sold by
Delivery method
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/12 months |
|---|---|---|
10 DB Targets | 10 database targets for Liquibase Pro | $5,000.00 |
15 DB Targets | 15 database targets for Liquibase Pro | $7,500.00 |
20 DB Targets | 20 database targets for Liquibase Pro | $10,000.00 |
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
Liquibase provides support for Liquibase Pro Monday through Friday, excluding U.S. holidays, 8am - 5pm CT (GMT-6). Support plan can be upgraded to Premium support (24x7). See https://www.liquibase.com/support for more information
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Database Change Management
Create, version, deploy, roll back, and track database changes throughout the CI/CD pipeline
Code Validation and Compliance
Validate database code against predefined, customizable rules set by DBAs and security teams
Drift Detection and Security
Detect database drift and generate alerts to protect against malware and ransomware
CI/CD Pipeline Integration
Integrate database change automation into existing CI/CD workflows
Change Auditing and Traceability
Audit and trace database changes from development through production environments
Schema Registry
Centralized storage for schema changes with auto-generated documentation for database schemas.
Continuous Integration Testing
Automated simulation and review of database migrations during CI process to detect destructive changes and constraint violations before deployment.
Deployment Visibility
Single pane of glass interface to monitor and view the status of schema migrations across multiple environments with detailed deployment logs.
Migration Management
Central repository for storing and managing migration directories with simplified deployment process to production environments.
Deployment Tool Integration
Seamless integration with modern deployment platforms including Kubernetes and Terraform for automated schema migration deployment.
Automated Data Contracts
Automatically creates and enforces data contracts to assign ownership and govern data quality with cross-team collaboration.
Data Lineage Tracking
Uses lineage tracking to build a comprehensive knowledge graph for understanding data flow and dependencies across the pipeline.
Proactive Data Quality Detection
Analyzes and profiles data to detect potential issues early through advanced analysis and semantic understanding before they impact operations.
Environment Consistency Validation
Provides profiling and environment diff tools to maintain data integrity across staging and production environments.
CI/CD Pipeline Integration
Integrates with CI/CD pipelines to oversee SLAs, manage governance, and provide full control and visibility over data quality management.
Standard contract
Customer reviews
Chethan R.
Reliable Version-Controlled Schema Changes with Easy Rollbacks
Reviewed on Mar 31, 2026
Review provided by G2
What do you like best about the product?
Tracks and manages database schema changes reliably using version control
Supports multiple databases with consistent deployment workflows
Easy rollback and automation for safer releases
Supports multiple databases with consistent deployment workflows
Easy rollback and automation for safer releases
What do you dislike about the product?
Steep learning curve for complex change sets and configurations
Debugging failures and error messages can be unclear
XML/YAML syntax can feel verbose and hard to maintain
Debugging failures and error messages can be unclear
XML/YAML syntax can feel verbose and hard to maintain
What problems is the product solving and how is that benefiting you?
Eliminates manual database change tracking by version-controlling schema updates
Ensures consistent deployments across environments (dev, test, prod)
Reduces errors and speeds up releases with automated migrations
Ensures consistent deployments across environments (dev, test, prod)
Reduces errors and speeds up releases with automated migrations
Miguel R.
Incredible DB Change Tracking with Easy CI/CD Integration
Reviewed on Mar 16, 2026
Review provided by G2
What do you like best about the product?
Incredible for tracking the changes in a DB, the integration with the DB is easy, easy to use in Ci/CD pipelines.
What do you dislike about the product?
It just give you one error at the time, so if you have multiple you will need to run it every time.
What problems is the product solving and how is that benefiting you?
DB CI/CD deployment
reviewer2796066
Automated database syncing has reduced manual effort but still needs a more intuitive first use
Reviewed on Feb 06, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for Liquibase is syncing different databases. I have an RDS cluster with different databases, and when there is a change in one database, I sync the other databases with the same changes.
I created a Jenkins pipeline with designed workflows. Using that pipeline, if there is a change in one database or multiple DDL or DML changes occur, developers can use the pipeline to make changes directly in one database and sync to other databases.
How has it helped my organization?
Liquibase has positively impacted my organization by reducing the time spent syncing databases.
Manual overhead has been significantly reduced, making Liquibase a valuable tool for us.
What is most valuable?
Liquibase's best features handle all the overhead of syncing. We do not have to plan any DML or DDL changes manually and apply them to the database. It also reduces the risk of inconsistent changes.
Liquibase reduces the risk of inconsistent changes in my experience by syncing the database easily, and there is no manual intervention required.
What needs improvement?
Liquibase could be improved in several ways. Some facilities could be enhanced, and for first-time users, it could be more intuitive rather than overwhelming.
For how long have I used the solution?
I have been using Liquibase for more than two years.
What other advice do I have?
Liquibase is overall good software, but for first-time users, it could be more intuitive. Everything else works well. I would rate this review as a six.
reviewer2797194
Database-as-code has transformed how we track schema changes and manage controlled migrations
Reviewed on Jan 16, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Liquibase is database-as-code, which we use for creating table schemas, maintaining migrations, and ensuring that in production, if rollbacks happen, then it's more controlled than running raw SQL.
I can give you a quick specific example of how I've used Liquibase for migration. Although we have not used it for rollbacks until now, we do use it for managing our scripts during migration.
Liquibase is a database-as-code provider, and that is pretty much how we use it.
What is most valuable?
The best features Liquibase offers include CI/CD integration, which we really appreciate because we didn't have a lot of issues integrating it into our existing CI pipelines, and the changeset and changelog, which are the source of truth that effectively tell us how the database changes are taking effect.
The CI/CD integration helped my workflow by improving visibility with the changelog and changeset. For the CI part, Maven and Gradle builds are already available, so we just use the Maven plugin and it was pretty straightforward.
There is something called Liquibase Validate as well, which helps with pre-deployment checks. We use the update SQL command for dry-run approvals.
Liquibase has positively impacted my organization by providing a way to manage database migrations instead of maintaining raw SQL, which comes with the issue of not being able to track certain schema updates or new table creations. With Liquibase, you have that history through the changelog and changeset tables, which maintain that history of changes.
What needs improvement?
Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly. While we create one file per feature, rollbacks are not magical and require significant consideration, and large diff operations can also be very slow, affecting performance.
We only use MySQL for now, so there's nothing related to any exotic database features, and we're not consuming anything on that side either.
For how long have I used the solution?
I have been working in my current field for about two years.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Sanket O.
A good database change management tool
Reviewed on Sep 19, 2025
Review provided by G2
What do you like best about the product?
It helps to manage the database changes and when the time for rollback comes, it automatically reverses the changes
What do you dislike about the product?
The format in which the changeset is required to be written can sometimes be too tedious
There are also scenarios where scripts can be dependent on each other, in that case defining dependencies is quite complex
There are also scenarios where scripts can be dependent on each other, in that case defining dependencies is quite complex
What problems is the product solving and how is that benefiting you?
For each release developers used to sit and create a consolidated script file, which was a time consuming activity moreover when there was a need of roll back the code, tons of efforts were required to be taken to roll back the database
To solve this we started using the Liquibase, we have setup a pipeline with the help of which it becomes very easy to maintain the versions
To solve this we started using the Liquibase, we have setup a pipeline with the help of which it becomes very easy to maintain the versions