Download Google AlloyDB JDBC Driver

Download the Google AlloyDB JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the Google AlloyDB JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Google AlloyDB. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each Google AlloyDB driver uses its own syntax — see the connection details below.

The Google AlloyDB JDBC driver

Google AlloyDB is a fully managed, PostgreSQL-compatible database service on Google Cloud, combining the familiarity of PostgreSQL with Google's advanced storage and computing technologies. It is designed for demanding transactional and analytical workloads, offering up to 4× faster transactional throughput and 100× faster analytical queries than standard PostgreSQL. AlloyDB includes a built-in columnar engine and supports the pgvector extension for AI-powered similarity search.

The Google AlloyDB JDBC URL

• Required File(s): postgresql-xxx.jar (PostgreSQL JDBC Driver)
• Java Driver Class: org.postgresql.Driver
• JDBC URL: jdbc:postgresql://{HOST}:{PORT}/{DB}
• Website: Google AlloyDB

AlloyDB uses standard PostgreSQL port 5432. Connect via the AlloyDB Auth Proxy for secure access outside your VPC, or use Private Service Connect for VPC-internal connectivity. The standard PostgreSQL JDBC driver is fully compatible with AlloyDB's PostgreSQL-compatible interface.

Reaching an AlloyDB Instance

An AlloyDB instance has a single static IP address, private to its VPC unless public IP was turned on. A laptop is outside that VPC, so one of the three routes below is needed before DbSchema sees anything.

Through the AlloyDB Auth Proxy

This is the route Google recommends, and the one that needs no change to the instance. The proxy runs on your machine, authenticates with your Google credentials and presents the database locally.

1. Let the proxy out. Its host needs outbound access to port 5433 on the instance's IP address, and to port 443 for everything else.
2. Start the proxy and note its local port. It listens on 127.0.0.1 from port 5432 upward, one port per instance.
3. Point DbSchema at the proxy. Host localhost, port the one above, and the database user and password as usual. To DbSchema this looks like a PostgreSQL server on your own machine.

Through a public IP address

1. Enable public IP on the instance, then add your address under Authorized external networks as a CIDR block. Authorized networks exist for public IP only — with the Auth Proxy they are neither needed nor available.
2. Paste the URL into DbSchema. In the Connection Dialog set Connection Mode to Edit the JDBC URL Manually and paste the string you copied. The user and the password are entered in the first tab, not in the URL.

Through a host inside the VPC

• Or reach the server through SSH. When the database port is deliberately closed to the internet, press Setup SSH Tunnel... in the Connection Dialog and connect through a host that is exposed. The database host and port are then the ones seen from the SSH host — often localhost. See the SSH tunnel guide.

DbSchema and Google AlloyDB

DbSchema connects to Google AlloyDB using the standard PostgreSQL JDBC driver, visualizing AlloyDB's PostgreSQL-compatible schemas including columnar engine acceleration and pgvector extension tables, supporting both OLTP design and analytical workload optimization.