🎉 Hub is free for all users 🎉
See database release information in one place for changes that occur throughout your organization.
Monitoring for Developers
Get real-time information about your deployments and an overview of recent commands for the specific database you’re working on.
Quickly understand which changes have been made by your team and when in each environment so you can collaborate easily with your team.
What to expect during Beta
Our goal for Beta is to gather input from Liquibase users to help us shape Liquibase Hub into a tool you won’t be able to live without.
Once you sign up for a Liquibase Hub account, you’ll see instructions on how to connect your Liquibase activity to Hub.
⚠️ Important: You must be running Liquibase v4.1+ in order to connect to Hub. Download the latest version.
Getting started with Hub
Here’s a quick overview of the steps to connect your Liquibase changelogs to Hub:
Step 2: Run
This new command connects an XML or formatted SQL changelog to your Hub project.
Step 3: Make database changes
Make database changes like you normally do. You’ll see the data show up in your Hub project.
In the app
Once you’re in the Hub app, use the blue Feedback button located on the left side of the screen to leave comments, report bugs, and provide feedback. You can even point out specific parts of the page with this feedback tool. Neat! We also have a link to a survey at the top right.Liquibase Hub
In our chat
If you want to chat with people in real-time, head over to our Liquibase Discord chat and join our Beta channel.Beta Chat
Frequently asked questions
You must be running Liquibase v4.1. Download the latest version.
Once you sign up for a Hub account, you’ll get your first API key and instructions on how to connect your changelog to Hub.
Liquibase Hub is hosted on scalable cloud architecture. While we do make daily updates, this should not affect users or create any downtime.
In the event that Liquibase Hub does experience downtime, your Liquibase operations will not be affected. Downtime may result in the loss of operational information sent to Liquibase Hub, but will not impede the Liquibase operation itself.
While operational details may be lost if Hub downtime occurs, the next operation sent to the same environment will sync the details of that connection to Liquibase Hub so that the overall state of the connection remains in sync with what is displayed on Liquibase Hub.
Liquibase only sends information to Liquibase Hub when a Liquibase API key is provided.
The liquibase.hub.mode property setting allows users to send data based on this setting in liquibase.properties or the Maven POM file:
- all – Default. This setting allows helpful, critical data to help users understand the content of a changeset when troubleshooting or tracking the specific evolutions of your database schema. This sends all metadata described above plus the following:
- Changeset body from the changelog
- Generated SQL executed by the Liquibase core app
- Two types of logs: operation-event and change-event.
- meta – Sends only non-content data, such as changelog name, changeset name, comments, user, timestamps, Liquibase version, Liquibase integration, and similar meta settings. This setting is recommended for connections where sensitive information may be transmitted using Liquibase — typically DML scripts with PII or other sensitive data. Using this setting limits the users’ ability to use Hub in identifying an update failure should one occur.
- off – Sends no data to Hub, even if you have a valid API key in your defaults file.
We take data security very seriously. Here’s what we’re doing to keep Hub data secure:
- Data encryption in transit via secure HTTPS calls
- Data encryption at rest once stored in our database
- We use several other tools and procedures to protect against possible attacks.
Have more questions? We’re happy to answer your data security questions. Contact us to get answers.
All members and admins of an Organization have the same access to Projects, Operations reports, and other data.
We will be adding additional controls in the future to allow specific users or groups access to specific projects and their operational details.
The following commands send data to Liquibase Hub:
- update, updateCount, updateToTag
- rollback, rollbackOneChangeSet, rollbackToDate, rollbackCount
Liquibase communicates to Hub via secure https API calls.
Currently, only XML or formatted SQL changelogs are supported. We’re working on adding JSON and YAML soon.