Status: Closed beta (launching soon)
Most startups reach for Auth0 or Cognito by default — not because they’re the best fit, but because they’re familiar. Then the per-seat bill arrives, the login flow needs customizing, and what felt like a solved problem turns into an expensive constraint.
Kanshin is the alternative you build on from day one — and don’t outgrow.
Pay for Identity When It’s Used. Not When It Isn’t.
Every major identity provider charges per seat, per month. That means you’re paying for every user in your database — whether they logged in yesterday or haven’t touched your product in six months.
Kanshin works differently. You pay per login and per registration — the actual moments of value. A user who isn’t active isn’t costing you anything.
Our introductory beta pricing starts free for development and grows with your usage, not your user count. When you’re ready to scale, the math stays in your favor.
Authentication You Can Actually Program
Most identity platforms give you a login page and a handful of configuration options. Kanshin gives you a programmable flow engine.
Using the same visual graph approach as the rest of the Nandeshou platform, you can build custom authentication logic without writing infrastructure code. Define what happens when a user registers. Trigger an event when a login comes from an unfamiliar location. Route different user types through different verification paths. Connect your identity events to downstream systems through Event Hooks.
This isn’t configuration. It’s programmable identity — and it means your auth layer can evolve with your product rather than constraining it.
Every Action, Auditable
Every login, registration, policy evaluation, and system event in Kanshin is logged, timestamped, and queryable. Not buried in a log file — surfaced in a clean audit interface you can filter by time range, level, and source.
This matters for compliance. It matters when something goes wrong and you need to know exactly what happened. And it matters as a signal of the kind of platform Kanshin is: one where nothing happens invisibly.
Auditability isn’t a feature we added. It’s a property of the entire Nandeshou platform, and Kanshin inherits it by design.
Built for Hybrid From Day One
As your startup grows, some enterprise customers will require on-premises or hybrid deployments. Most identity platforms make you solve that problem when you get there — which usually means a painful migration.
Kanshin’s outbound-only synchronization architecture means your identity layer works across cloud and on-premises environments without opening inbound firewall ports. Your local directory stays behind your perimeter. Changes sync in real time. If connectivity drops, local authentication keeps working.
You don’t have to need this on day one. But it’s there when you do.
The Developer Experience You Actually Want
Testing authentication flows is painful. Kanshin includes a built-in Developer Sandbox — a free, non-persistent realm with an integrated test mailer so you can register accounts and validate email verification flows without touching real addresses or setting up third-party services.
Every paid plan includes a Dev Realm alongside your production environment. Test freely without risk.
The Foundation for Everything Else
If you’re building on the Nandeshou platform — or think you might — Kanshin is already the identity layer for Omni, Omni Core, and AethOS. Adopting Kanshin independently means your identity infrastructure is already integrated if your stack grows. No migration, no adapter, no compatibility work.
Start here. Stay here.
Closed Beta
Kanshin is launching soon. We’re accepting beta partners now — startups building new products who want a better foundation than the default options, and are ready to take advantage of what a programmable identity platform can actually do.
