Getting Started

View .md

These docs cover four products for building on AWS with .NET: Kanject CLI, Kanject Core, Kanject BaaS and DynoStudio, plus Kanject UI for BaaS frontends. Start with the product that matches the job in front of you; the requirements below explain which tools and services it uses.

Ship .NET services, packages and apps
Kanject CLI. Deploy a Lambda service, publish NuGet packages, or distribute a desktop app, each proven locally before an approved production step.
Write AWS services in typed C#
Kanject Core. Eighteen focused .NET libraries for DynamoDB, SQL, caching, S3, SQS, Lambda hosting and more. Use one, or several.
Add ready-made product features
Kanject BaaS. Identity, a wallet ledger, notifications, file storage, messaging and more, deployed into your own AWS account.
Explore and query DynamoDB
DynoStudio. A desktop studio to model tables, browse items and run PartiQL, with the native request and its cost shown before anything runs.

How they fit together

Choose the products your service needs. Kanject UI uses BaaS, and Kanject CLI handles BaaS package installation and service deployment:

  • Kanject CLI coordinates the tools you already use — dotnet, the AWS tools, CloudFormation and your CI provider — instead of replacing them. It works on new and existing .NET projects, with or without Core.
  • Kanject Core replaces AWS SDK boilerplate with typed C#. Write against the SDK yourself, or let Core do it.
  • Kanject BaaS modules are features you could build yourself on Core, already assembled. Install the private NuGet packages and deploy your service using Kanject CLI. CloudFormation templates are available separately to customers at [developer.kanject.cloud](https://developer.kanject.cloud).
  • Kanject UI is the frontend for BaaS: React widgets and admin templates that talk to the modules you deployed.
  • DynoStudio works on any DynamoDB table, however it was built. If your entities carry Core's NoSqlDatabase annotations, it can import them as the model, but it doesn't need them.

What you need

  • Kanject CLI — the .NET SDK, version 8 or later (the project templates need .NET 10). Each shipping path adds its own tools, such as the AWS CLI for Lambda. Installation checks them one at a time.
  • Kanject Core — a .NET project to add the libraries to. The Community libraries install from public NuGet; the others come from the private Kanject feed, so ask your administrator for access.
  • Kanject BaaS — an AWS account you control, Kanject CLI, and customer access to the private NuGet packages and CloudFormation templates at [developer.kanject.cloud](https://developer.kanject.cloud).
  • Kanject UI — a deployed BaaS module and a React 18+ app (Vite, Next.js or Astro).
  • DynoStudio — the app, on macOS, Windows or Linux. Connect with IAM SSO or access keys to work on live tables; without a connection, schema-only mode works offline.

Learn by doing

Bean & Bark, a fictional coffee roaster, runs through three tutorial series. Start with the product you picked. The Core chapter includes a standalone local API; each series lists its own tools and setup steps:

Was this page helpful?