Download pgpipe

Single static binary, ~25 MB. No runtime dependencies. Verify the SHA-256 checksum before running, especially on production hosts.

Run with Docker .deb / .rpm Cheatsheet Changelog

Run with Docker

The fastest way to try pgpipe.

A small Dockerfile + docker-compose.yml spin up a source database, a destination database, and pgpipe wired between them. The dashboard opens at http://localhost:8080.

1. Grab the files

# Make a working directory
mkdir pgpipe-demo && cd pgpipe-demo

# Pull the four files
BASE="https://www.pghorizon.com/downloads/pgpipe/v5.2.0/docker"
curl -fsSL $BASE/Dockerfile          -O
curl -fsSL $BASE/docker-compose.yml  -O
curl -fsSL $BASE/pgpipe.example.yaml -o pgpipe.yaml
curl -fsSL $BASE/init-source.sql     -O
curl -fsSL $BASE/init-dest.sql       -O

2. Bring the stack up

# Build the pgpipe image (pulls the published binary)
# and start everything in one go
docker compose up -d --build

# Watch pgpipe logs
docker compose logs -f pgpipe

# Open the dashboard
open http://localhost:8080

3. See replication in action

# Insert a row in the source database
docker compose exec source-db psql -U postgres source_db \
  -c "INSERT INTO public.greetings(message) VALUES ('hello from pgpipe');"

# A moment later, see it in the destination
docker compose exec dest-db psql -U postgres dest_db \
  -c "SELECT * FROM public.greetings;"

# Tear it all down (and delete data)
docker compose down -v

Logging into the dashboard

On the very first docker compose up, pgpipe generates a random admin password and prints it once to the logs. Open the dashboard at http://localhost:8080 and use these credentials:

# Just the password (cleanest, always works)
docker compose exec pgpipe cat /var/lib/pgpipe/pgpipe-admin.password

# Or grep the full first-run banner from the logs
docker compose logs pgpipe | grep -A 6 "FIRST RUN — DASHBOARD"

Username is admin. The password is auto-generated on first run, persisted to /var/lib/pgpipe/pgpipe-admin.password (mode 0600), and survives restarts. The "FIRST RUN" log banner only appears the first time — after that, the file is the only copy.

To set your own password instead, edit pgpipe.yaml → server.auth.password before bringing the stack up. For production, prefer an environment variable like PGPIPE_DASHBOARD_PASSWORD over a value baked into YAML.

Container image

Dockerfile

Alpine-based, multi-arch (amd64 / arm64), pulls the verified pgpipe binary at build time. ~50 MB final image.

Compose

docker-compose.yml

Source PG · Destination PG · pgpipe wired together. Production-safe defaults — no benchmark hacks.

Config

pgpipe.example.yaml

Annotated reference config: source, destination, ordering, batching, state backend, observability.

Running pgpipe against your own databases? Drop the source-db and dest-db services from the compose file and edit pgpipe.yaml with your real hostnames. The Dockerfile builds the same image either way.

Linux packages

Platform	File	Size	Download
Debian / Ubuntu (amd64) sha256: d04569f88e2029895c82d77897d4fe675c7b79edabd7d3316358191794f61968	`pgpipe_5.2.0_amd64.deb`	8.7 MB	Download
Debian / Ubuntu (arm64) sha256: d15fc78a1dae4c0b32c5b19e45d5631723bb9835014c8efa525f1fd98576b1fc	`pgpipe_5.2.0_arm64.deb`	7.5 MB	Download
RHEL / Rocky / Fedora (x86_64) sha256: 9e0ad5d43bc2b570165982d3a1aa64bec94dcf8f94ef78c955d7538a10bec29e	`pgpipe-5.2.0-1.x86_64.rpm`	11.5 MB	Download
RHEL / Rocky / Fedora (aarch64) sha256: 41ca96d558e6ee53548b9fe0c74db62d29229d04d4032f757cb5d4813a82d266	`pgpipe-5.2.0-1.aarch64.rpm`	10.5 MB	Download

Verification & companion files

checksums.txt — SHA-256 for all binaries
THIRD_PARTY_LICENSES.txt — open-source notices
CHANGELOG.md — release history and upgrade notes

Debian / Ubuntu (.deb)

wget https://www.pghorizon.com/downloads/pgpipe/v5.2.0/pgpipe_5.2.0_amd64.deb
sudo apt install ./pgpipe_5.2.0_amd64.deb
sudo systemctl enable --now pgpipe

RHEL / Rocky / Fedora (.rpm)

wget https://www.pghorizon.com/downloads/pgpipe/v5.2.0/pgpipe-5.2.0-1.x86_64.rpm
sudo dnf install ./pgpipe-5.2.0-1.x86_64.rpm
sudo systemctl enable --now pgpipe

Moving to v5.2.0? Four lifecycle changes to know

Removal is now three explicit operations. Choose Decommission pipeline, Remove software, or Erase local data by the outcome you need; none silently performs another.
Database decommission starts read-only. Stop the service and run pgpipe teardown to review exact source objects and a plan digest. Confirmed execution refuses active slots, changed plans, and shared or uncertain ownership.
Package removal preserves recovery material. apt remove and dnf remove keep configuration, state, external TLS paths, and the stable pgpipe account. Package scripts never connect to PostgreSQL.
Local erasure is guarded. Debian uses apt purge; RPM uses the digest-bound pgpipe local-purge preview and confirmation before dnf remove. Unknown paths, mounts, links, or live processes stop safely.

Full v5.2.0 changelog →

First time using pgpipe?

The Docker Compose quickstart gets you replicating in under a minute, with a sample source and destination already wired up.

See the quickstart

pgpipe is provided as-is, free of charge, with no support SLA. For commercial support and managed deployments, talk to us.