Start with the Kanject Core foundation on an annual license. Add the BaaS modules you need, individually. Or take All Access Enterprise — every library, every module, with the SLA, IP indemnification, and source code escrow your procurement team will ask about.
Every tier deploys into your own AWS account. You pay AWS for usage. We don't host your data plane, we don't mark up your infrastructure — and if you ever stop renewing, what you've shipped keeps running. Renewals buy updates and support, not permission.
Building early? The CLI and the DynoStudio workspace are free for teams under $250K. Paid Kanject licenses include DynoStudio during launch.
Free developer tooling while you build. During launch, DynoStudio is bundled with paid Kanject licenses. Then choose the Core foundation, BaaS modules, or All Access Enterprise for production.
Start at $0 with the Kanject CLI and the DynoStudio workspace — free for individuals, open-source projects, and companies under $250K in trailing-twelve-month revenue or funding.
Start with a Core tier when your team wants clean .NET APIs over AWS infrastructure. During launch, paid Core licenses include DynoStudio.
Pick BaaS modules à la carte when the problem is specific: identity, files, forms, notifications, wallet, analytics, or messaging. During launch, paid BaaS licenses include DynoStudio.
Move to All Access Enterprise when you want every Core library and every BaaS module, plus SLA, IP indemnification, and source code escrow.
Kanject runs inside your AWS account, so pricing stays honest about who charges for what.
Libraries, modules, source generators, docs output, release channel, and support.
DynamoDB, Lambda, S3, Cognito, EventBridge, bandwidth, and any other AWS services your deployment consumes.
There is no Kanject-hosted infrastructure between your app and AWS. No proxy, no markup, no migration risk if you ever leave.
The Kanject CLI and the DynoStudio workspace, free for individuals, open-source projects, and companies under $250K in revenue or funding raised over the trailing twelve months.
Crossed the threshold? You have 90 days to move to a paid Kanject license.
Production deploys, runtime libraries, BaaS modules, and DynoStudio's modelling layer require a paid Kanject license. During launch, paid Core, BaaS, and All Access licenses include DynoStudio instead of pricing it as a separate SKU.
The starter license. Ship a pilot, an internal service, or your first production app on the full Core library set.
Book a demoFor small teams running a real product. Two environments to separate dev from production, with DynoStudio included during the launch bundle period.
Book a demoFor growing engineering organisations. Unlimited environments and business-hours email support with a next-business-day response target.
Book a demoBaaS modules are sold separately at every Core tier. All Access Enterprise is the only tier that bundles every BaaS module by default. The CLI and the DynoStudio workspace are free for eligible early-stage teams, and paid Kanject licenses include DynoStudio during launch.
| Core Launch $4,999 / yr | Core Starter $9,990 / yr | Core Team $24,990 / yr | All Access Enterprise From $75,000 / yr | |
|---|---|---|---|---|
| Shape | ||||
| Developer seats | 3 | 5 | 25 | Unlimited |
| Environments | 1 | 2 | Unlimited | Unlimited |
| Libraries | ||||
| All 12 Core libraries | ||||
| BaaS modules | Purchased individually | Purchased individually | Purchased individually | All included |
| Tooling | ||||
| Kanject CLI Also free for eligible teams under $250K | ||||
| DynoStudio workspace (beta) Browse, query, ⌘K — free for eligible teams; bundled with paid licenses during launch | ||||
| DynoStudio modelling (beta) POCO-derived schemas, model builder, diff & lint — launch bundle | ||||
| Support | ||||
| Software updates Shipped binaries stay licensed even if you don't renew | ||||
| Support level | Annual review | Annual review | Business-hours email | SLA-backed, named contact |
| Onboarding session | — | — | 1 × 90-min | Yes |
| Enterprise | ||||
| IP indemnification | — | — | — | |
| Source code escrow | — | — | — | |
| AOT-cert pipeline support | — | — | — | |
| Custom modules | — | — | — | Scoped |
| Procurement (MSA, DPA, sec) | — | — | — | |
Every Kanject library applies the six pillars of the AWS Well-Architected Framework to the service it wraps. The result: serverless-by-default architectures, scale-to-zero idle bills, and battle-tested patterns that don't quietly burn money — the libraries pay for themselves in what you stop paying AWS.
Every wrapper enforces the AWS Well-Architected pattern for the service it touches. You can't use Kanject and accidentally ship a hot-partition DynamoDB table, an S3 bucket without lifecycle rules, or an SQS consumer that DLQ-storms on a single bad message.
DynamoDB on-demand, Lambda compute, S3 + CloudFront delivery. No EC2 fleets to right-size, no RDS clusters to babysit, no idle dev environments quietly billing $1,200/month to do nothing on weekends. Scale-to-zero is the default, not an opt-in.
Single-table DynamoDB design, partial-batch acknowledgement on SQS, parallel workloads with retry budgets, idempotency keys, golden-path source generators. The patterns that take a senior engineer two years to learn — already encoded in the libraries on day one.
Teams shipping on Kanject typically see materially lower AWS spend versus equivalent always-on architectures, plus weeks of engineering time saved per quarter on infrastructure tuning. For most teams the Kanject license is recovered inside the first quarter — and stays cheaper every quarter after.
Kanject wraps the same AWS services that run in production at the world's largest engineering teams. Your pricing pays for the clean .NET API, the source generators, the auto-generated docs, and the support — not the infrastructure underneath, which already exists, runs in your account, and is paid directly to AWS.
Join forward-thinking developers and businesses who trust Kanject to eliminate cloud complexity and accelerate innovation.