What we're building next.

An open view of Kanject's direction. Dates slip, priorities shift — but this is the honest plan. Ship is more important than ship-on-time.

In development
Up next
Later this year
Exploring
Q3 2026
Up next

Kanject UI for Blazor — WebAssembly + Server

Bring the Kanject UI widget suite to Blazor. Same props, same BaaS wiring — <KanjectLogin>, <KanjectAnalytics>, <KanjectForm> and the full admin dashboard template, native to the .NET stack.

  • Full parity with React widgets on launch: Login, Analytics, Form, Wallet, Notifications, Chat.
  • Blazor WebAssembly + Blazor Server both supported from the same package.
  • Shared design tokens with the React build — one theme, two runtimes.
#ui#blazor#dotnet
Q3 2026
Up next

Kanject.Insights v3 — real-time streams

WebSocket-delivered event subscriptions, server-sent funnels, and per-user cohort inclusion checks — all from the same [EventTopic] schemas you already have.

  • New [RealtimeProjection] attribute compiles to a live materialised view.
  • Drop-in React + TypeScript hooks: useCohort("power-users").
  • SLO-backed delivery: sub-200ms p95, 99.99% at-least-once.
#insights#analytics
Q3 2026
Up next

Kanject.Identity.Server v2

Full OIDC provider you own, built on AWS primitives. Replace Auth0 / Okta inside your AWS account with the same DX your team already knows.

  • OpenID Connect, OAuth 2.1, PKCE, DPoP — all attribute-driven.
  • Multi-tenant client registration with zero custom middleware.
  • Ships with a hosted UI you can theme via design tokens.
#identity#baas
Q4 2026
Later this year

Azure + GCP provider parity

The same attributes, a different provider. Kanject.Core.NoSqlDatabase targets CosmosDB and Firestore behind the exact same interfaces.

  • AddCosmosNoSqlDatabase() as a drop-in for AddDynamoNoSqlDatabase().
  • Multi-cloud source generators — one code-base, two deploy targets.
  • Provider-agnostic CloudFormation / Bicep / Terraform output.
#multi-cloud#core
Q4 2026
Later this year

Kanject.Agents — LLM-assisted service orchestration

A typed, auditable way to let agents call your Kanject endpoints. OpenAPI + [EmitsEvent] + permission attributes become tool definitions automatically.

  • Every [HttpPost] with XML docs becomes a callable tool.
  • Permission checks and rate limits enforced at the agent boundary.
  • Built-in traces in Kanject.Insights so every agent action is reviewable.
#ai#integrations
2027 · Research
Exploring

Kanject.EdgeFns — global, annotation-driven edge compute

Write the same C# endpoint; we decide whether to run it at Lambda@Edge, CloudFront Functions, or a regional Lambda based on [Edge]-annotated contracts.

  • Declarative latency budgets: [Edge(MaxLatencyMs = 50)].
  • Automatic cache + revalidation rules from [Cache] attributes.
#infrastructure#experimental

Have a use-case we haven't heard about yet?

Roadmap priorities follow paying customer demand. Tell us what's blocking you, and we'll tell you where it lands.

Get in touch →
Ready to ship?

Simplify your cloud
journey today.

Join forward-thinking developers and businesses who trust Kanject to eliminate cloud complexity and accelerate innovation.