How is Kanject different from Firebase, Supabase, Convex, or Amplify?
Firebase, Supabase, and Convex are excellent hosted platforms for fast-moving teams. Kanject is built for .NET teams that want the same product velocity while keeping their backend infrastructure and data plane in their own AWS account.
Are BaaS modules included in the Core tiers?
No. Core Launch, Starter, and Team license the 12 Core libraries only. BaaS modules — Identity, Wallet, FileServer, Insights, InstantMessaging, NotificationHub, EventHub — are purchased individually. Forms and Identity.Server are currently in private beta: join the waitlist from their product pages rather than buying them today. All Access Enterprise is the only tier that bundles every BaaS module.
How does the seat cap work?
Seats are named developer seats on the org license. Devs who never touch the Kanject NuGet feed don't count. If you outgrow a tier mid-year, you can upgrade; the new tier prorates against the time remaining on the current term.
None of the tiers fits my team — what are my options?
Two paths. If you've simply outgrown a tier, upgrade mid-term — the new tier prorates against the time remaining, so you pay the difference, not a second license. If your shape is genuinely different — more developers than Starter but no need for Team's support layer, say — reach us through the contact page and we'll scope a license that fits. The ladder is the default, not a wall.
What does “per environment” mean for BaaS?
One production deploy is one environment. Staging, regional pilots, and per-customer sandboxes each count separately. All Access Enterprise rolls every environment into the commercial model so the count stops mattering.
Do I pay AWS separately?
Yes. Kanject deploys into your AWS account, so AWS bills you directly for usage. We charge for the libraries, modules, release channel, and support — never for the infrastructure underneath.
Is there a free tier or free trial?
Yes — the Community tier. The Kanject.Core foundation (kernel, Web API, and messaging), the Kanject CLI, and the DynoStudio workspace are free for individuals, open source, education, and companies under $250K in revenue or funding raised over the trailing twelve months — free to build and ship the foundation, not just evaluate it. The AWS provider engines (NoSQL, SQL, cache, files, logs), BaaS modules, and commercial use above $250K move to a paid Core license.
How does Community-tier eligibility work?
Self-certification — tick a box, no sales call, no audit. Individuals, open source, education, and companies under $250K in trailing-twelve-month revenue or funding qualify. Cross $250K and you have 90 days to move to a paid Core license. The AWS provider engines and BaaS modules are always paid; commercial DynoStudio use moves to Professional, Business or Enterprise, with a one-year Professional subscription included with every annual Core and All Access license.
Is DynoStudio sold separately?
DynoStudio has its own licensing: Community is free for non-commercial use — individuals, open source, education, and companies under $250K. Professional is the per-developer commercial license; Business adds annual team packaging at the same per-seat rate; Enterprise adds governed rollout and procurement terms. Every annual Core and All Access license ships with a free one-year Professional subscription (BaaS modules are licensed separately and don't include it), so those customers never pay for it twice. The full breakdown lives on the DynoStudio page.
What about source code and IP risk?
All Access Enterprise includes source code escrow — the source is released to you if Kanject ceases operations — and IP indemnification on the libraries you license. Core tiers include a binary license. Source access can be scoped separately during procurement.
What happens if I don't renew?
What you've shipped keeps running, and what you built with stays usable. Deployed binaries are licensed indefinitely, and every annual Core license carries a perpetual fallback: the versions released during your paid term stay licensed to use after it ends. Those packages remain downloadable from the Kanject feed for up to six months after expiry — and you can mirror them into your own artifact repository, so availability never depends on us. Non-renewal ends new versions, updates, and support — renewals buy updates and support, not permission for what you already have.
Can I host the Kanject packages in my own artifact repository?
Yes. Licensed packages can be mirrored into your organisation's private artifact repository for internal builds. That pairs with the perpetual fallback license: even after a subscription ends, the versions from your term stay licensed and stay available from a feed you control.
Will my renewal price go up?
No. Your renewal never costs more than your current term while you stay continuously subscribed. List-price changes apply to new customers and lapsed subscriptions that return — not to a live one. The only way your number changes is an upgrade you choose: a bigger tier, more modules, more environments.
If I downgrade or cancel, what happens to my data?
It stays in your AWS account. Cancelling means you stop receiving updates and support, but deployed binaries and your AWS resources remain yours.
On-prem or air-gapped deployments?
Available on All Access Enterprise. We scope private NuGet mirroring, deployment templates, and outbound-network limits during discovery.