DynoTable vs TablePlus

TablePlus shipped a DynamoDB driver in September 2025 and has published almost nothing about it since. There is no PartiQL or SQL editor for DynamoDB in it, so reading a table means the grid and the visual filter builder. DynoTable is built for DynamoDB alone, around a SQL Workbench that plans joins and aggregates against your keys and GSIs. This page compares the two as DynamoDB clients, as of July 2026.

Feature	DynoTable	TablePlus
Purpose-built for DynamoDB	Yes	Relational-first
Browse & filter DynamoDB items	Yes	Yes
Edit DynamoDB items	Yes	Limited (in progress)
PartiQL/SQL query editor	Yes	No
SQL JOINs, GROUP BY & aggregates	Yes	No
Query plan preview (Scan/Query + RCU when available)	Yes	No
Smart Tables (visual joined views)	Yes	No
AI agent on your own AWS Bedrock keys	Yes	No
Connect external AI agents (MCP), staged review	Yes	No
Table management (create/delete, GSIs, TTL, capacity)	Yes	Not documented
Works offline (DynamoDB Local)	Yes	Not documented
Documented DynamoDB support	Yes	No
Pricing	Free read-only tier, from $9/mo billed annually	$99 one-time

When TablePlus wins vs DynoTable

Your workflow	Choose
One native client for Postgres, MySQL, Redis, and DynamoDB together	TablePlus
Browse a DynamoDB table with the grid and visual filter builder	TablePlus
`JOIN`, `GROUP BY`, or aggregates over live DynamoDB tables	DynoTable
See Scan vs Query and an RCU estimate before you run a filter	DynoTable
Staged edits, full exports, or MCP for a coding agent	DynoTable

Is DynoTable a TablePlus alternative for DynamoDB?

Yes, for the DynamoDB half of the job. TablePlus is a native client built around relational engines, with DynamoDB as a recent addition on the side. If DynamoDB is the database you live in every day, the question is whether a driver added to a relational client keeps up with it.

What the TablePlus DynamoDB driver actually is

The changelog is the only source, because nothing else documents it. Two entries, eight months apart:

macOS 6.7.0 (634), 5 September 2025: "[DynamoDB] Added DynamoDB - Beta."
macOS 6.9.1 (670), 2 May 2026: "[DynamoDB] Fixed a bug where TablePlus could not fetch the item list."

Windows got its own line in 6.7.0 build 324 on 30 September 2025: "[DynamoDB] Added DynamoDB driver." TablePlus's documentation site names fifteen database engines, and DynamoDB is not one of them, so nothing about the driver's feature set is written down where you can check it.

What you get in practice is the data grid plus the visual filter builder that TablePlus uses for its relational drivers. There is no query-language surface for DynamoDB at all, PartiQL included.

What a grid filter costs on a DynamoDB table

DynamoDB gives a client two read APIs for a table. Query needs an equality on the partition key. Scan reads everything. A filter on status, email or createdAt is not a key condition, so there is no Query to issue: it has to become a Scan with a FilterExpression. AWS is direct about what that means, in the Scan reference: the filter is applied after the scan finishes, so consumption is the same whether a filter is present or not.

Put a number on it. Eventually-consistent reads bill half a unit per 4 KB, so one pass over a 5 GB table is:

5 GB / 4 KB x 0.5 = 655,360 read units

On-demand in us-east-1 that is roughly $0.08, which is why it never shows up in development. On a table provisioned at 500 RCU the same filter is 4,000 KB/s of read capacity for about 22 minutes, with every other reader on that table queueing behind it. Your grid shows twelve rows; DynamoDB read every item in the table to find them, and the raw response admits it, with ScannedCount counting everything it evaluated and Count saying twelve.

The 1 MB page limit makes it worse in a way that is easy to misread. That limit applies before the filter runs, so a page can come back with zero matching items and a LastEvaluatedKey telling you there is more. A client that treats the first empty page as the end of the results will show you an empty table that isn't empty.

None of this is fixable inside a filter builder, because the fix is choosing the right key or index before the read. DynoTable's SQL Workbench compiles INNER/LEFT JOIN, GROUP BY and aggregates into native Query and Scan calls planned against your keys and GSIs. When a plan is available, the preview identifies Scan versus Query and the index; the RCU estimate appears only when table metadata supports it. An ordinary partition Query shows no RCU. A Scan of the table above announces itself as a Scan before you run it. See SQL for DynamoDB, and why Scans get slow and expensive for the cost side.

DynoTable's visual filter builder with the index picker and the derived Query badge.

The DynoTable SQL Workbench compiling a JOIN with GROUP BY into Query and Scan calls.

TablePlus added an LLM chat of its own in 6.6.2 (July 2025). The difference worth knowing about DynoTable's AI agent is where the inference runs: your own AWS Bedrock account, with the boundary and the per-action approvals set out in the AI chat docs.

How to switch from TablePlus

Download DynoTable for macOS, Windows or Linux and install it.
Add a connection with the same AWS profile or access keys you use in TablePlus — DynoTable reads your standard AWS credential chain, nothing DynoTable-specific.
Point it at the same region and tables; your data stays in DynamoDB, so there's nothing to migrate.
Open the SQL Workbench and write the filter you were clicking as a WHERE clause. If it lands on a key or a GSI, you get a Query instead of the full scan.

The trial is free for 30 days, no credit card required. Paid Individual seats start at $9/mo billed annually ($108/yr); see pricing for monthly and Team rates. DynoTable stays on the Free plan after the trial — browsing, PartiQL SELECT, exports and MCP schema/item reads, with no time limit.

FAQ

Does TablePlus support DynamoDB?

Yes, as a beta driver. TablePlus 6.7.0 added it on 5 September 2025 (macOS) and 30 September 2025 (Windows). Since then the macOS changelog carries one further DynamoDB entry, a May 2026 fix for fetching the item list, and DynamoDB is not listed among the fifteen engines on TablePlus's documentation site.

Can you write a query in TablePlus for DynamoDB?

No. The DynamoDB driver exposes the grid and the visual filter builder, with no PartiQL or SQL editor, so JOIN, GROUP BY and aggregates have nothing to compile against.

Why is filtering a DynamoDB table in a GUI slow?

Because a filter on a non-key attribute cannot be a Query. It becomes a Scan with a FilterExpression, and DynamoDB applies that filter after reading the data, so you pay for the whole table however few rows come back. One pass over a 5 GB table is 655,360 eventually-consistent read units, which is about 22 minutes of a 500 RCU table's entire read budget. That is true in every client. When a plan is available, DynoTable's preview identifies Scan versus Query and the index; the RCU estimate appears only when table metadata supports it. An ordinary partition Query shows no RCU.

Browse the full comparison hub for every DynoTable alternative.
Prefer a client with an official DynamoDB PartiQL editor? See the DataGrip comparison.
See also DynoTable as a DynamoDB GUI and the Dynobase comparison.
Build queries fast with the free DynamoDB Expression Builder.

Last verified 2026-08-28 against the TablePlus macOS and Windows changelogs, the TablePlus documentation site, and the AWS Scan reference. The capacity figures are computed from AWS's 4 KB read-rounding rule and the current us-east-1 on-demand read price. TablePlus is a trademark of its respective owner; referenced here for identification only.