NoSQL Workbench vs DynoTable
AWS NoSQL Workbench is AWS's free desktop tool for DynamoDB, built around data modeling. DynoTable is a desktop client for querying and editing a table once it is live.
Two different jobs
NoSQL Workbench centers on data modeling. You design a single-table schema, visualize access patterns, validate them against sample data, and commit the model to a table. Use it when you are deciding how your keys and GSIs should be shaped.
Its operation builder also edits items and manages tables (create, update and delete tables and GSIs, capacity and auto scaling), one operation at a time.
DynoTable is built for the day-to-day work after the model exists: browsing and editing items, building key and filter conditions, and querying live data. A common split is to design in NoSQL Workbench and operate in DynoTable, task by task:
| Your task | Use |
|---|---|
| Design a table, keys, GSIs from access patterns | NoSQL Workbench |
| Deploy the model as CloudFormation | NoSQL Workbench export |
| Turn a live table into CloudFormation / Terraform / CDK | DynoTable (free) |
| Quick schema sketch in the browser, no install | our free Single-Table Design tool |
| Browse, filter, edit live items daily | DynoTable |
JOIN / GROUP BY / aggregates over live tables | DynoTable (SQL Workbench) |
| One-off sample-code snippet for an operation | Either; both generate code |
Download NoSQL Workbench: free on Windows, macOS and Linux
AWS lists no price for NoSQL Workbench anywhere on its product page. The download page offers builds for macOS (Intel and Apple silicon), Windows and Linux.
Modeling needs no AWS account. The installer also sets up DynamoDB Local (an option since version 3.4.0), which needs Java 17 or newer and gives you local tables to run operations against.
The current build is 3.20.3, from late July 2026; the release history page still stops at 3.20.2 (April 6, 2026). The 3.20.0 release redesigned the Data Modeler and added access patterns.
What survives the commit button
A NoSQL Workbench model is three different kinds of thing at once, and they cross into production very differently.
The keys and indexes cross as code. Export offers "NoSQL Workbench model format" or "AWS CloudFormation JSON template format", and the second one deploys or drops into an existing infrastructure-as-code stack.
Commit skips the template. AWS's page says "This action creates server-side resources in AWS for the tables and global secondary indexes represented in the data model", and "NoSQL Workbench creates tables and indexes with on-demand capacity by default" (committing a data model). Check that capacity default before you commit to a production account.
The explanations cross as pictures. The aggregate view renders every table and index side by side, and exporting it produces "an archive with PNG images of all tables and indexes" (aggregate view). A teammate without the app receives screenshots.
Facets do not cross at all. AWS's facets page calls them "non-functional visualizations" and recommends validating access patterns instead.
If you learned single-table design by drawing facets, note that the entity views you reasoned with exist only inside the modeler.
After the commit: 50 saved operations, no joins
NoSQL Workbench does query live data. The operation builder "supports projection expression, condition expression, and generates sample code in multiple languages", and "you can save as many as 50 DynamoDB data operations in the operation builder" (operation builder). Results export to CSV one page at a time.
Each saved item is one DynamoDB operation. "Worst and average rating per
product category, English reviews only" over a reviews table and a products
table is not an operation. It is a Scan of the reviews (or a Query, if
locale were a key), a lookup per product, and a rollup you write somewhere
else.
DynamoDB has no join and PartiQL adds none. Its SELECT takes a single FROM
with no JOIN, no GROUP BY and no aggregate functions
(AWS PartiQL SELECT reference).
DynoTable's SQL Workbench takes it as one statement:
SELECT p.category, MIN(r.rating) AS worst, AVG(r.rating) AS avgRating
FROM reviews r
JOIN products p ON r.productId = p.productId
WHERE r.locale = 'en'
GROUP BY p.categoryThe join and the two aggregates run on the client, because DynamoDB exposes no
server-side join to call. The MIN and AVG aggregate columns show
(partial) until every page is read.
The read still costs what DynamoDB charges. locale is not a key, so the
reviews side is a full Scan, billed for every item in the table. Each
products row then comes through key lookups (BatchGetItem, de-duplicated).
The pre-run estimate prices the reviews read only. It flags the joined-table
reads inline without pricing them.
The joined table must be keyed by the join attribute: here, products needs
productId as the partition key of a table with no sort key, or as the
partition key of exactly one GSI. A self-join follows the same rule, so two entity
types inside one single-table design (which has a sort key) join only through a GSI.
Subqueries, CTEs, UNION and window functions are out too.
SQL for DynamoDB covers how the compilation works.

Workbench has no AI agent and can't model vector indexes
DynoTable's AI agent runs on Amazon Bedrock in your own AWS account, so no DynoTable server sees your prompts or rows. It can only stage writes, which you review and commit, as the AI chat docs describe.
Vector indexes became DynamoDB's third index kind in August 2026. Workbench's data modeler still models only tables and global secondary indexes, and its last build, 3.20.3, shipped two weeks before vector search went GA, so there is nothing yet to model or commit.
DynoTable creates and deletes a vector index from the Table dialog's Table indexes pane. The table must use on-demand capacity, DynamoDB Local is not supported, creating an index is a paid action, and a new index takes minutes to build.
It binds a Bedrock embedding model and its source attributes to the index, and re-embeds an item when an item-editor save changes its source text. Bulk edits, PartiQL writes and writes made outside DynoTable don't re-embed, so your app still needs its own embedding step.
Re-embedding on save and searching by a typed sentence both need AI set up and spend Bedrock tokens on your account. Searching by a pasted vector and Find similar on a row need no AI setup, spend no Bedrock tokens and work on the Free plan. Vector search covers it.
What DynoTable does not do
- No data modeling: there is no design canvas, no facets and no sample-data generation. DynoTable can export a table that already exists as CloudFormation, Terraform or CDK, but not a model you haven't deployed. Model in Workbench (or the free Single-Table Design tool).
- No model-driven commit: Workbench's commit button deploys a whole data model, every table and index in it, in one action. DynoTable creates one table at a time (name, partition key, optional sort key, capacity mode), then adds each GSI from the Table dialog's Table indexes pane.
- No restores, no streams configuration, and no CloudWatch monitoring; those stay in the AWS console. DynoTable creates and deletes on-demand backups and manages point-in-time recovery, but restores neither.
- Writes, SQL and table changes are paid: NoSQL Workbench is wholly free.
DynoTable's Free plan needs a free DynoTable account and covers browsing,
PartiQL
SELECT, data, code and schema exports, and read-only MCP. The SQL Workbench, Smart Tables, writes, AI and table or index changes need a paid seat or the 30-day trial.
Adding DynoTable next to NoSQL Workbench
Keep modeling in NoSQL Workbench if it fits your workflow, and add DynoTable for the live tables. The two connect differently.
The Workbench commit dialog asks for an account alias, a region, an access key ID and a secret access key, with a session token or IAM role ARN as options.
DynoTable reads the profiles already in your ~/.aws directory instead. It
detects six credential kinds, including IAM Identity Center and aws login
sessions, so there are no keys to paste.
Each profile pins its region, and ⌘P (Ctrl+P on Windows and Linux) switches profiles. DynoTable also connects to DynamoDB Local through a local profile.
Download DynoTable for macOS (Apple Silicon or Intel), Windows or Linux,
pick a profile, and run a GROUP BY (or a JOIN across two tables) against
the tables you just committed.
The 30-day trial of the plan you pick needs no credit card. When it ends, DynoTable falls back to the Free plan unless you upgrade. Paid seats start at $9/month billed annually ($108/year), or $12 month-to-month. See pricing for the current plans.
FAQ
Is DynoTable a NoSQL Workbench alternative?
Yes. NoSQL Workbench focuses on data modeling; DynoTable focuses on day-to-day querying and editing, with a SQL Workbench for JOINs, GROUP BY and aggregates.
Can DynoTable run SQL against DynamoDB?
Yes. DynoTable's SQL Workbench compiles SQL, including INNER/LEFT JOIN, GROUP BY and aggregates, down to DynamoDB's Query and Scan operations, so it stays within DynamoDB's access-pattern rules.
Are NoSQL Workbench facets a real DynamoDB feature?
No. AWS's documentation says facets "don't exist as a usable construct in DynamoDB, as they are purely an aid to modeling of access patterns" (facets). The table you commit has keys, indexes and items; it has no facets.
Related
- Browse the full comparison hub for every DynoTable alternative.
- See also the Dynobase comparison and the hands-on best DynamoDB GUI clients roundup.
- Plan a schema from access patterns with the free Single-Table Design tool.
- Size items and plan capacity with the free DynamoDB Item Size Calculator.
Last verified 2026-10-09. NoSQL Workbench is a tool from Amazon Web Services; referenced here for identification only.


