A Visual Way to Browse and Query Amazon DynamoDB

Amazon DynamoDB defines each table by a partition key, an optional sort key, and the indexes around them. DbSchema's bundled JDBC driver introspects tables, GSIs, and LSIs into a diagram, and turns plain SQL into the PartiQL calls DynamoDB understands.

Read key design and index projections from a diagram, not from Terraform
Query items in SQL — the driver speaks PartiQL to the DynamoDB API
Inspect item shapes across a schemaless table before shipping a feature
Develop against DynamoDB Local with the very same tooling

available for

ISO-27001 certified

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

Free Download

DbSchema showing DynamoDB tables, keys, and indexes as a diagram

Trusted by teams at

Single-Table Design
Shouldn't Live Only in One Head

DynamoDB rewards packing many entity types into one table — and punishes anyone who has to reconstruct that design later from CloudFormation templates and item samples. Key schemas, GSI projections, and access patterns end up documented nowhere.

DbSchema puts tables, keys, and every index on a single diagram: the design becomes an artifact the team can point at, question, and onboard from.

Visualize, Query & Reason About
Your DynamoDB Tables

The parts of DynamoDB work the console keeps making harder than it should be.

Introspect DynamoDB tables, GSIs, and LSIs into a diagram

Indexes You Can Point At

Partition keys, sort keys, GSI projections, and LSI configurations arrive on the canvas straight from the live table definitions — no IaC archaeology required.

Write SQL against DynamoDB translated to PartiQL

SQL In, PartiQL Out

SELECT, INSERT, UPDATE, and DELETE are translated into DynamoDB API calls, with completion for table and attribute names — no SDK code for an ad-hoc question.

Lay out DynamoDB entities and access patterns visually

Access Patterns, Drawn Out

Lay out the entities sharing a table, annotate the diagram, and export it — the picture that turns a single-table review from argument into discussion.

AWS Owns the Tables
You Own the Model

Key schemas are expensive to change once items pile up. Working on an offline model first gives the design a review stage before anything is provisioned.

Design Off the Meter

Draft tables and indexes on the canvas — no AWS account involved yet.

Keep the DynamoDB model versioned in Git

A History for the Key Schema

Commit the model next to your IaC, so index decisions leave a reviewable trail.

Rehearse on DynamoDB Local

Point the same connection at localhost:8000 and validate the design without AWS costs.

Share Without Console Access

Hand reviewers the model or its documentation instead of IAM credentials.

DynamoDB Connection Facts

The custom driver (com.wisecoders.jdbc.dynamodb.JdbcDriver) is bundled with DbSchema — nothing to download or register — and its source is open on GitHub. Use jdbc:dynamodb://amazonaws.com for production AWS or jdbc:dynamodb://localhost:8000 for DynamoDB Local, plus your AWS Access Key ID, Secret Access Key, and region (for example us-east-1); traffic runs over HTTPS on port 443. For production, prefer IAM roles carrying the minimum DynamoDB permissions over long-lived access keys. Details on the DynamoDB JDBC driver page.

Put Your Key Design on a Diagram

Community Edition is free forever; the same download carries a 15-day Architect trial.

Download Free

Tutorials and guides

Amazon DynamoDB with DbSchema

Frequently asked questions

Yes, through a custom JDBC driver bundled with DbSchema that translates SQL statements into DynamoDB's PartiQL dialect, so you can view partition keys, sort keys, GSIs, and LSIs as a schema diagram and query items with familiar SQL.

DbSchema connects over HTTPS on port 443, using the JDBC URL jdbc:dynamodb://amazonaws.com for production AWS DynamoDB or jdbc:dynamodb://localhost:8000 for DynamoDB Local.

Yes — point DbSchema at jdbc:dynamodb://localhost:8000 to inspect item shapes and validate schema changes locally without incurring AWS costs.

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