One Visual Model for Every Aurora PostgreSQL Schema

Aurora PostgreSQL keeps PostgreSQL wire compatibility, so DbSchema connects with the standard PostgreSQL JDBC driver and pulls tables, views, sequences, functions, and extensions into one design model — diagrammed, documented, and compared across environments.

Reverse engineer every schema in the cluster from a single connection
Build queries visually — the SQL runs on Aurora and plain PostgreSQL alike
Diff a dev cluster against production and apply only the changes you approved
The PostgreSQL JDBC driver arrives automatically on first connection

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema modeling an Aurora PostgreSQL cluster with ER diagrams and documentation

Trusted by teams at

Failover Is Automatic
Schema Alignment Is Not

Aurora replicates the data, promotes replicas, and even spans regions with Global Database. What it never does is tell you whether staging still matches production, or which of the cluster's schemas gained a column last sprint.

DbSchema adds the missing layer: one model of the whole cluster, focused diagrams per domain, and environment comparisons that end the guessing.

Understand, Query & Align
Aurora PostgreSQL Environments

The daily work of a cluster team, gathered in one desktop tool.

Reverse engineer Aurora PostgreSQL schemas into ER diagrams

Map Every Schema in the Cluster

Connect to the cluster endpoint and DbSchema lays out tables, views, sequences, and extensions as diagrams you arrange by bounded context.

Build Aurora PostgreSQL queries in the visual query builder

Compose Queries by Clicking

Join tables, add conditions, and aggregate visually. The builder emits standard PostgreSQL syntax, so the same query serves Aurora, Serverless v2, and self-hosted clusters.

Compare Aurora PostgreSQL environments and generate migration SQL

Diff Regions and Environments

Compare two clusters, or the model against a live one, and generate targeted migration SQL. Global Database primary and secondary regions fit as separate profiles in one project.

Schema Changes That Arrive
as Pull Requests

The design model is a file in your repository. A new column, an added index, a dropped table — each lands as a commit your reviewers can read. After the merge, DbSchema turns the approved diff into PostgreSQL DDL and carries it into the cluster you choose.

Aurora PostgreSQL schema synchronization between the Git model and cluster environments

Read Git Workflow Docs

Connecting to Aurora PostgreSQL

The cluster listens on the standard PostgreSQL port 5432, and the PostgreSQL JDBC driver downloads automatically — Aurora PostgreSQL is wire-compatible. The URL takes the form jdbc:postgresql://cluster.cluster-id.region.rds.amazonaws.com:5432/dbname; append ?ssl=true&sslmode=require to enforce TLS in transit.

IAM database authentication is supported: grant the user the rds_iam role and pass a short-lived RDS auth token as the password. Aurora Serverless v2 uses the same endpoint and port, since capacity scaling stays invisible to the JDBC driver.

Give Every Region the Same Schema

One installer, no account: free Community Edition plus a 15-day Architect trial.

Download Free

Frequently asked questions

Yes. Aurora PostgreSQL speaks the PostgreSQL wire protocol, so DbSchema connects with the standard PostgreSQL JDBC driver and exposes tables, views, sequences, functions, and extensions.

Aurora PostgreSQL uses the standard PostgreSQL port 5432, in a URL of the form jdbc:postgresql://cluster-endpoint:5432/dbname.

Yes. Grant the database user the rds_iam role, then supply a short-lived RDS authentication token as the password when connecting.

Teams working with Aurora PostgreSQL often use these engines too. Explore dedicated guides and JDBC setup for each.