Schema in. Queries out.
A modern DynamoDB studio — browse tables, run typed queries, and design single-table models visually. Got annotated .NET POCOs? Paste them in and DynoStudio derives the access patterns for free.
Paste a POCO. Skip the modeling.
Your annotated POCO doubles as the schema DSL — one file, two jobs.
It's the runtime data model your app already uses and the
single source of truth DynoStudio reads. [KeyTemplate],
[GsiAlias], [GsiIndex],
[ShardedKeyTemplate], [Composite],
[Unique] — DynoStudio reads them and derives the entire
access-pattern surface, so you don't have to redraw it in the model
builder. Edit the POCO, save, the studio re-parses. No JSON, no
YAML, no second source of truth.
using Kanject.Dyno;
public class User
{
[KeyTemplate("USER#{Id}")]
public string Id { get; set; }
[KeyTemplate("PROFILE#{Id}")]
public string Sk { get; set; }
[GsiAlias("ByEmail")]
[GsiIndex("GSI1", IsPk = true)]
[Unique]
public string Email { get; set; }
[GsiAlias("ByOrg")]
[GsiIndex("GSI2", IsPk = true)]
public string OrgId { get; set; }
[Composite("FullName")]
public string FirstName { get; set; }
[Composite("FullName")]
public string LastName { get; set; }
public DateTime CreatedAt { get; set; }
public string Role { get; set; }
}(USER#{Id})(PROFILE#{Id})(ORG#{OrgId})(ORDER#…) sharded ×4Six things that make it different.
Studio meets schema. Nothing here is a wrapper around the AWS console.
Schema-aware everything
POCO annotations drive tables, indexes, GSI aliases, sharded keys and access patterns. One source of truth — the C# class.
Functions auto-derived
Every GsiAlias becomes a typed query function. ByEmail → GetUserByEmail. ByOrg → ListUsersByOrg. No glue to write.
Browse data, run queries
Scan a table, page through results, click a row to inspect, hop to related items via foreign-key annotations.
⌘K command bar
Type a function, table or org id. Hit return. Result panel stacks below — schema-aware autocomplete on every step.
Visual model builder
Drag, drop, connect. The single-table model renders as entity boxes joined by GSI relationship curves — diff a v3 against v4 before you apply, lint warns before you ship.
Light + dark, all surfaces
Toolbar chrome, table borders, code highlighting and chip palette all swap. Accents and annotation pins stay constant.
Built for both sides of the desk.
Engineers and analysts work from the same DynamoDB tables. They shouldn't have to use the same tool — or wait for someone else to translate.
Your access patterns, typed.
Paste your annotated POCOs. DynoStudio surfaces every query function the schema implies, runs them against the table you connect to, and copies the equivalent code back out. Single-table designs stop being a separate file you maintain alongside the model.
- IAM SSO connection or paste a schema offline
- Sharded keys, composite keys, uniqueness — all annotation-driven
- Equivalent DynamoDB SDK call shown beside every run
Read the data without reading the model.
Switch to Explorer mode and the same schema becomes a data dictionary. Field names humanise, types simplify, every column gets a meaning. Ask a question in plain language, get a paginated read with cost preview attached — read-only by default, ship-safe.
- Plain-English questions compile into typed queries
- Data dictionary with allowed values, owners, downstream reports
- Read-only PROD by default; analyst role enforced at the toolbar
Questions, before you sign up.
When does it ship?
Private beta is rolling out by audience now. General availability is targeted for late 2026 once the schema parser handles every Kanject.Dyno annotation in production use today.
What will it cost?
DynoStudio is bundled with Kanject Core for teams already on the platform. Standalone pricing for non-Kanject users will be announced before GA.
Do I need an AWS connection?
No. Schema-only mode lets you design and validate access patterns offline. Connecting to AWS (IAM SSO or access keys) unlocks live browse, query and write.
Do I need .NET to use DynoStudio?
No. The studio works on any DynamoDB account — connect, browse tables, run queries, design models visually. The .NET shortcut (paste annotated POCOs and have DynoStudio derive the access patterns for you) is the one feature that requires a Kanject.Dyno-annotated schema; everything else is language-agnostic.
Self-hosted or SaaS?
Desktop app. macOS first (Apple Silicon + Intel), Windows next. Your AWS credentials and schema files never leave your machine — connections are direct from the desktop client to your AWS account.
Get an invite when your slot opens.
We're inviting in waves by use case. Tell us how you'd use it — developer, analyst, or both — and we'll prioritise the queue so you land in the right cohort.