Liquibase.io empowers organizations of any size to develop fast, efficient, and entirely governed Database DevOps practices. As a SaaS platform for automating data change management, Liquibase.io enables rapid adoption of Liquibase to drive organizational efficiency.
Liquibase.io provides centralized configuration and management of Liquibase with governance for database deployments. It has role-based access control (RBAC) to manage access and permissions for operational, reporting, and administrative capabilities.
By default, Liquibase.io manages and runs on Liquibase Pro, so you no longer need to worry about installing and maintaining local instances of Liquibase.
The long-term vision of Liquibase.io is to scale its database change management process for development teams.
Frictionless onboarding: Features an intuitive onboarding experience that makes getting started easy.
Authentication and authorization: Features secure authentication, which (in future releases) will handle a wide range of authentication mechanisms, such as single sign–on (SSO) and multi-factor authentication (MFA). It also supports Role-Based Access Control (RBAC) to make it easier for admins to manage users of Liquibase.io within their organization and to facilitate the administration of security at scale.
Centralized and reusable configurations: Features an organization or team with a centralized application that enables a group of collaborators (including developers and engineers, DBAs, infrastructure teams, and security teams) to manage their database changes.
Observability: Visibility into database changes, statuses, and corresponding logs. Traceability in who/what/when/how for changes.
Security Governance in detail
Liquibase.io tracks all user actions in an audit history to maintain accountability. Only an Administrator can review the audit history to see a record of change: who made this change and what they changed. Audit history enables root-cause analysis. For example, As a DBA, you investigate deployment errors by auditing the history of a job.
DevOps Managers must often reassure stakeholders that the systems and data are secure. Liquibase.io’s RBAC capability makes defining and managing user access and permissions for specific functionality easy.
Organizations no longer need to worry about installing and maintaining local configurations across multiple environments. Liquibase.io handles this so users can get started much faster.
Configuration requires only two steps: create a project and, within it, create a workflow to run on demand. Unlike self-managed installations that require manual upgrades to newer versions, Liquibase.io operates on the latest product release approximately two weeks after its initial release. We will always include the current API, Web, and Liquibase versions so you can check which version is associated with the latest release.
DevOps teams can build predefined workflows and apply them to the development CI/CD pipeline. They also define the connections (credentials) to resources (external services) so that when an application developer gains access to execute workflows, they can update the database by running a workflow without spending time on configurations. With RBAC, your organization's Administrator manages who has access to run workflows to make changes to the database.
Administrators have access to job logs that capture the output of any actions. For example, a diff command outputs a drift summary in the job logs. At Liquibase.io’s initial release, converting the output to an external file is not be supported. HTML operation reports such as Checks run report, Update report, and Rollback report.
Liquibase.io offers a series of REST APIs that can help to integrate Liquibase.io and Liquibase functionality into existing DevOps, Development, and Observability tools.