Before you install Liquibase Secure server, ensure your environment meets the following requirements.

Liquibase Secure server

Liquibase Secure server is the central service that receives, stores, and displays the operation data your team's Liquibase extensions send it. The requirements below cover what it takes to run it.

System requirements

Scaling and availability

Liquibase Secure server runs as a single Docker Compose deployment on one host. It does not cluster across nodes, fail over automatically, or replicate its databases, so size the host for your expected volume rather than planning to add nodes later.

The primary database is the component that limits throughput, and it scales vertically. Give the host more CPU, memory, or disk as your operation volume grows.

Software requirements

Liquibase Secure server is a containerized application. Docker and Docker Compose are required regardless of installation method. The liquibase-platform CLI runs Docker Compose under the covers.

Supported host platforms

The installer bundle embeds its own runtime, so the registry serves a separate bundle for each host platform. Pull the bundle that matches the machine you run the installer on, and run uname -sm if you are unsure of its operating system and architecture.

Note: There is no native Windows bundle. On Windows, run the installer inside your WSL2 (Ubuntu) shell, which is where Docker Desktop and the installer run, and use the linux-x64 bundle.

Network requirements

The bundled reverse proxy is the only component that exposes ports on the host. All other services, including the databases, communicate over isolated internal Docker networks and are not reachable from outside the deployment.

The server must be reachable by two sets of clients:

• Liquibase CLI machines: Must be able to reach the server over HTTPS to send operation data

• Web app users: Must be able to reach the server over HTTPS to use the dashboard

Monitoring

The server does not export Prometheus or OpenTelemetry metrics. Monitor it with the health endpoints, its structured JSON logs, and your container runtime's own statistics.

Liquibase extension

The Liquibase extension is a plugin that runs on each machine executing Liquibase commands. It automatically collects operation metadata and reports it to Liquibase Secure server after each command completes. No changes to your changelogs or workflow are required.

To send operation data to the server, you need:

• Java 11+ (required to run the Liquibase CLI and extension JAR)

• Liquibase Secure 6.0+ installed

• Network connectivity from the CLI machine to the server API