Frequently asked questions about PGZen

PostgreSQL 14 through 18. PGZen follows PostgreSQL’s own officially supported major versions, tests every one of them before release, and tests the oldest and newest in continuous integration on every change. PostgreSQL 19 is tested separately as a prerelease and is not yet part of supported versions.

macOS 26.0 or later. PGZen is built directly on macOS 26’s native SwiftUI and Liquid Glass APIs — there is no legacy-OS fallback mode.

Yes. PGZen connects over direct TCP or through an SSH tunnel that authenticates with a password or an Ed25519 private key; RSA and ECDSA keys and SSH agents are not supported. TLS policies are disable, prefer, require, verify-ca and verify-full. See Compatibility for the details.

In the macOS Keychain, not in profile files. PGZen uses it when you connect to your database or SSH server. See the Privacy Policy.

Only to the database or SSH server you connect to, and to export locations you choose. PGZen has no backend that collects database content.

Only if you turn it on. Crash reporting is opt-in and disabled by default in Settings ▸ Privacy. Reports never include your SQL, bound values, query results, or credentials — the Privacy Policy lists what they do include.

$29.99 launch price, then $39.99. One purchase, no subscription. Those are US prices; the App Store sets the price in other countries, including local taxes. PGZen is sold only on the Mac App Store, and you can install it on every Mac signed in with the same Apple ID.

PGZen is a native Mac app made only for PostgreSQL. It rates every schema change for risk before you apply it, shows the exact SQL and values of every generated change, and includes ER diagrams, EXPLAIN plans and pg_stat_statements insights.