Download pgpipe

Single static binary, ~21 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/v2.1.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: 87e5bdd2c07ad2a3b8aa2360e390d87cb2b87797ebc98efb6e25f7fe56147099	`pgpipe_2.1.0_amd64.deb`	5.9 MB	Download
Debian / Ubuntu (arm64) sha256: e1e947ee156eeca983da7148d4dd49765e1e105b413067357865aca8a278cf0d	`pgpipe_2.1.0_arm64.deb`	5.1 MB	Download
RHEL / Rocky / Fedora (x86_64) sha256: 9971293497760c2d7993744071a1b765743c52e6f30d366cd80c047e501a6e4f	`pgpipe-2.1.0-1.x86_64.rpm`	7.7 MB	Download
RHEL / Rocky / Fedora (aarch64) sha256: 381668d1bd84da299aff8e13c78146ebaf2fb5a7c502345c48747e1f974d12fc	`pgpipe-2.1.0-1.aarch64.rpm`	7.0 MB	Download

Verification & companion files

checksums.txt — SHA-256 for all binaries
THIRD_PARTY_LICENSES.txt — open-source notices

Debian / Ubuntu (.deb)

wget https://www.pghorizon.com/downloads/pgpipe/v2.1.0/pgpipe_2.1.0_amd64.deb
sudo apt install ./pgpipe_2.1.0_amd64.deb
sudo systemctl enable --now pgpipe

RHEL / Rocky / Fedora (.rpm)

wget https://www.pghorizon.com/downloads/pgpipe/v2.1.0/pgpipe-2.1.0-1.x86_64.rpm
sudo dnf install ./pgpipe-2.1.0-1.x86_64.rpm
sudo systemctl enable --now pgpipe

Upgrading from v1.x? Three things to know

Restart the service after the package upgrade. Installing the new .deb/.rpm over v1.x does not restart a running pipeline — the old binary keeps running until you sudo systemctl restart pgpipe.
pgpipe now validates destination unique keys at startup. A v1.x pipeline that ran while quietly quarantining 42P10 rows to the DLQ (destination table missing a matching PRIMARY KEY/UNIQUE constraint) will now refuse to start — deliberately. The startup error names every affected table and includes the exact ALTER TABLE … ADD CONSTRAINT … UNIQUE to fix it.
/metrics now requires a bearer token by default (the breaking change behind the major version). Update your Prometheus scrape config with the token pgpipe prints on first run — or set metrics.public: true to restore the old open behaviour.

Full v2.0.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 v1 is provided as-is, free of charge, with no support SLA. For commercial support and managed deployments, talk to us.