Dynomate 1.11.0
Released February 5, 2026 (
Query your DynamoDB tables with actual SQL, dock the Inspector and Logs wherever you want them, and never wonder why your SSO session died again. Oh, and we squashed that empty sort key bug.
SQL Console for DynamoDB
You can now query any DynamoDB table with SQL. From any table, click SQL → Export & Open SQL. Dynomate runs a background full-table scan, creates a local timestamped snapshot, and drops you straight into a SQL editor with a table and JSON editor to view your results.
One click to go from DynamoDB to SQL.
You can keep multiple snapshots per table, each saved with its own timestamp ID. That means you can compare query results across different points in time. Super handy when you're debugging something and need to see what changed between deployments.
When you've got what you need, export your results to CSV or JSON, or copy rows straight from the table UI.
Dockable Inspector & Logs
The Inspector (that JSON sidebar you're always reaching for) and the Logs console are now fully dockable. Dock to the right, dock to the bottom, drag to resize. Whatever works for your setup.
Wide monitor? Dock the Inspector to the right. Laptop screen? Bottom probably makes more sense. The point is: your layout, your call.
Clearer AWS SSO Sign-In Status
We've all been there. You run a query, it fails, and you spend a minute wondering what went wrong before realizing your SSO session expired. Not anymore.
When your AWS SSO session is signed out or expired, Dynomate now shows a clear Sign In indicator right in the title bar. Click it and you're straight into the refresh flow. No guessing, no failed queries, no wasted time.
Empty Sort Key No Longer Blocks Queries
If you had an empty sort key value, your query would just silently refuse to submit. No error, no feedback. It just wouldn't go. That's fixed. Empty sort keys are handled properly now, so your queries go through like they should.
Table Refresh After SSO Login
If a schema download failed before you signed in via SSO, the table wouldn't refresh after login, so you'd sign in successfully but still be staring at stale data. That's fixed. Once you're signed in, the table refreshes like you'd expect.
