
Overview

Product video
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
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Pricing
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.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
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.
Standard contract
Customer reviews
Easy to use, but we were not able to delete some of the tables because of a security issue
What is our primary use case?
I have worked on the Liquibase commands, Liquibase updates, Liquibase storeback, and some basic commands from Liquibase. We were using the Docker image installed from the AWS CI/CD, downloading this Liquibase image, and updating the command from AWS DevOps.
What is most valuable?
I'm not very into data engineering, but Liquibase is the first tool I have worked on from a data perspective. We were using the SQL server, which our clients found somewhat complex. So, they opted for Liquibase because it is easy. The solution is easy to use, and it has very clear documentation.
What needs improvement?
We were not able to delete some of the tables because of a security issue.
For how long have I used the solution?
I have done the POC project with Liquibase for six months.
How are customer service and support?
Whenever we face any issue, we contact the Liquibase support team, who are very supportive and give us quick responses.
How was the initial setup?
The solution's initial setup is easy if we use the Docker version. We have done a POC on our local tool. It was easy to install Liquibase in our local CLI.
What's my experience with pricing, setup cost, and licensing?
Liquibase is an open-source solution. If you are using Liquibase, you need to update its license. I think Liquibase is affordable for our organization.
What other advice do I have?
We were not able to delete some of the tables because of a security issue. We reached out to Liquibase because we thought the issue was from the Liquibase side, but it was from our end. We restarted the security team from our organization, which sorted our issue. My last project was a finance project, and they were relying on Liquibase only for database deployments.
I would recommend the solution to other users. Liquibase is very easy to use if you do CI/CD deployment for the database. The solution's commands and documentation are very easy to understand. The solution is very easy to learn, and I was able to learn it in two weeks. Liquibase is a user-friendly open-source tool.
Overall, I rate the solution a seven out of ten.
Offers integration with multiple databases, stable product and reduced our manual intervention
What is our primary use case?
People automate code-based technologies, but there can be a lack of automation for databases. This tool is used for database automation in DevOps.
What is most valuable?
It can be integrated with multiple databases like MySQL, MSSQL, and PostgreSQL. The biggest benefit is automating database scripts and manually backing up the database.
It has a rollback capability, but it has not impacted our operations. It's pretty normal.Â
What needs improvement?
It has been improved a lot in terms of automation, but there is still room for improvement.
There is a lot of improvement to be made in terms of automation documentation. This tool is pretty much new for everyone.Â
Compared to Jenkins, a CI tool where you integrate your code and run it for quality checks, which has alternative tools like TeamCity, Liquibase is one of the biggest tools for database automation.Â
There is documentation available on the website, but it should be improved.
For how long have I used the solution?
I have been using it for one and a half years.
What do I think about the stability of the solution?
It is a stable product.Â
What do I think about the scalability of the solution?
It is scalable and performs the same if I add more users. Currently, we have around 650 to 850 members.
How are customer service and support?
We are a service-based company working for a large client in the banking sector, so we didn't get a chance to talk with the Liquibase support team.
How was the initial setup?
For the very first time, the initial setup was a medium complex. One thing we faced issues with is that Liquibase does not show the exact error, which added to the complexity.
Suppose it fails with an error. It won't display the exact error on the CI side. For example, if you integrate Liquibase with Jenkins and your database scripts fail due to syntax errors, it won't show the exact error. It's not user-friendly in that aspect.
What was our ROI?
It will be useful for teams to automate and reduce manual work. It's not only for one specific team; it's across the team.
We saw tangible benefits from using Liquibase in terms of costs and resource savings.Â
We reduced our manual intervention by not having to reach out to multiple teams. For example, when executing scripts, we had to reach out to the database team every time we developed a new script to deploy it.Â
By using Liquibase, we write the script and compile it. If the build succeeds, we go back to our deployment tool and update our Active Directory so that it will be deployed into the desired environment. This reduces a lot of manual intervention.
What's my experience with pricing, setup cost, and licensing?
The pricing is fair.Â
What other advice do I have?
I would recommend using it. To learn Liquibase, one should have some database knowledge. If the person is from a DBA background, they would be able to learn quickly. But if they are from an application or infrastructure role, it's medium complex.
Before getting started, you should thoroughly go through the documentation and follow the latest changes deployed by the Liquibase product team.Â
Basically, when using the product, you should be able to understand it and stay updated on the latest releases.
Overall, I would rate the product a nine out of ten. Organizations should have this kind of tool to reduce manual intervention. The one point they could improve on is documentation, which they haven't clarified, and they need to work on that a lot.