See Kanject running in your AWS
in 30 minutes.

A working .NET service generated from the CLI, deployed into a sandbox AWS account, with DynoStudio open beside it. No slideware — we drive the product live and you ask the questions that matter for your stack.

A 30-minute walkthrough of the real product.

Three steps. No slideware. A Kanject engineer drives, you ask the questions that matter for your stack.

Pick a sample app

You name the use case — internal admin, customer portal, event-driven pipeline. We generate it live with the Kanject CLI in your shape, not a canned demo.

Watch it deploy

Private NuGet pull, source generators emit the typed surface, CLI ships the lambdas and tables into a sandbox AWS account. Eight to ten minutes, end-to-end.

Inspect with DynoStudio

Browse the generated tables, run a typed query, hit the lambdas. We answer the architecture questions your team will ask on day one.

DynoStudio, open beside the running app.

The same product surface the call will walk you through — generated tables, typed queries, derived functions, a single visual sense of the data layer. Hover the preview to feel the pacing; we'll go deeper live.

See the standalone DynoStudio page
Kanject DynoStudio us-east-1
FileEditViewSchemaQueryToolsHelp
ItemsSchemaModelQueryIndexes
No connection yet
Pick an AWS profile, or paste an annotated C# schema to start exploring without a connection.
Connect to AWSPaste SchemaUse LocalStack

Who should attend

Whoever owns the .NET service layer and whoever owns AWS. 30 minutes for the demo, optionally 15 more for Q&A.

What you need

A sketch of the domain you want to see modelled. Nothing prepared — we spin the sample from scratch on the call.

No trial, on purpose

We don't ship a free tier because the libraries deploy into your AWS account — you'd be running real infrastructure on day one. A demo is the honest way in.

What happens next

You leave the call with the generated sample, a copy of the deployment template, and a written proposal sized to your tier within two business days.

Tell us what you're shipping.

A Kanject engineer will reach out within one business day with two or three time slots. If you picked a tier on the pricing page, we'll have the context already — you'll see it pre-filled below.

  • 30 minutes on the call, plus optional Q&A.
  • One business day response, sent by a person.
  • No mailing list — we don't sell to your inbox.

We'll reach out within one business day. No mailing list, no follow-up automation.

The questions every prospect asks first.

Is this a sales call or an engineering call?
Engineering call. A Kanject engineer drives the CLI and AWS console. Sales joins only if you ask for procurement or contracting context.
Can I bring my own AWS account?
Yes — preferred, actually. We can deploy the sample into a sandbox of yours instead of ours, which makes the day-two story obvious. We'll send the IAM scope ahead of the call.
How is this different from just reading the docs?
The docs cover one library at a time. The demo shows the whole loop — generate, deploy, browse, query — so you see how the pieces compose under your real constraints.
Will you record it?
Only if you ask us to. Default is no recording, no transcript, no follow-up automation. You'll get one email with the artefacts and a written proposal — that's it.