Migrating to Gate
Most teams come to Gate carrying an existing identity stack — a hosted Auth-as-a-Service vendor, an enterprise IdP, or a homegrown auth layer. Migration is bounded by three concerns: feature parity (does Gate cover what you rely on?), API-shape mapping (how does your existing code change?), and user-data continuity (do existing users keep their accounts and credentials?).
This page is the migration landing surface. The capability comparison table is the substance; per-vendor sub-pages cover the API-shape mapping and code walkthrough.
1. Capability comparison
The table below maps capabilities customers commonly use across third-party identity vendors against Gate.
| Capability | Auth0 | Clerk | Stytch | Okta | WorkOS | Gate Standalone | Gate Native |
|---|---|---|---|---|---|---|---|
| Email + password | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Magic link | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| OTP (email) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Social OAuth (Google, GitHub, etc.) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Passkeys (WebAuthn) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| MFA — TOTP | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| MFA — WebAuthn / FIDO2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| MFA — SMS | ✓ | ✓ | ✓ | ✓ | ✓ | — | — |
| Branded hosted UI | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Custom email templates | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Transactional email — BYO provider | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Transactional email — platform-hosted | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| OIDC federation | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| OAuth2 federation | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| SAML SSO | Enterprise | Enterprise | Enterprise | ✓ | ✓ | ✓ | ✓ |
| SCIM provisioning | Enterprise | Enterprise | Enterprise | ✓ | ✓ | ✓ | ✓ |
| AD / LDAP native bridging | Enterprise | — | — | ✓ | — | ✓ | ✓ |
| Audit log — query API | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Audit log — SIEM forward | Enterprise | Enterprise | Enterprise | ✓ | ✓ | ✓ | ✓ |
| Hardware-attested tokens — SKR mode (TDX / SEV-SNP) | — | — | — | — | — | ✓ | ✓ |
| Forensic attribution (PII-tight audit envelope) | — | — | — | — | — | ✓ | ✓ |
| Automatic data-layer scoping (Identity-Aware Kernel) | — | — | — | — | — | — | ✓ |
| MAU billing model | Per-MAU tier | Per-MAU tier | Per-MAU tier | Per-user tier | Per-connection | 50K free → Unlimited (paid) | 50K free → Unlimited (paid) |
| Customer-held key custody (BYOK / HYOK) | — | — | — | — | — | ✓ | ✓ |
Standalone is Gate consumed as a dedicated identity service (the @k9o/gate SDK package; no rest-of-platform adoption required). Native is Gate composed with the rest of the Kilimanjaro platform (the @k9o/core SDK package; unlocks automatic data-layer scoping where Gate identity becomes the binding identity for every data query).
The single capability Gate does not match is SMS MFA — NIST SP 800-63B-4 deprecates SMS as a restricted authenticator and SIM-swap risk is material to the threat model Gate is built against. Customers migrating from a vendor whose SMS-MFA usage is load-bearing should plan a parallel migration path to TOTP / WebAuthn before cutover.
2. Two consumption paths
| Path | When to choose | SDK | Effective when |
|---|---|---|---|
| Standalone | Replace your current identity vendor without adopting the rest of Kilimanjaro. Adopt Gate first and the rest later. | @k9o/gate | Auth-only swap; existing application data stays where it is |
| Native | Adopt Gate as part of the full Sovereign Stack. Identity-Aware Kernel composes with Data / Security / Control / Compute pillars; automatic data-layer scoping turns on. | @k9o/core (re-exports the Gate namespace) | Greenfield projects or progressive migration from multi-vendor stacks to a unified platform |
Existing customers can start Standalone and add the rest of the platform later — the Gate API surface is identical across both paths. The Native-only differentiator (automatic data-layer scoping) requires the rest of the platform to be present; everything else is the same shape.
For pricing, see pricing on kilimanjaro.dev. SAML, SCIM and IdP federation are available on every plan.
3. Migration phases
Every migration follows the same four phases regardless of which vendor you're leaving.
Phase 1 — Capability audit
Before any code changes, audit your existing identity surface:
- User-collection size + structure. Active users, dormant users, soft-deleted users, retention obligations.
- Authentication methods in use. Which methods does your live application actually exercise (versus what your vendor account supports)? Migration is sized by what you actually use, not your vendor's full menu.
- Identity-provider connections. Federated SSO providers (OIDC / SAML / OAuth2 / AD / LDAP). Per-provider attribute mapping and group sync.
- Roles, groups, permissions. Your authorisation model. Gate maps to platform roles bound in Security §1; custom-permission models translate to JSON-policy rules per Control.
- Custom UI flows. Hosted UI usage, custom login pages, programmatic flows (passwordless sign-up, embed-in-app flows, etc.).
- Audit and compliance posture. Audit-log retention, SIEM integration, regulatory framework requirements.
Phase 2 — Parallel-run setup
Provision Gate alongside your existing vendor without cutting over. Set up:
- A Gate project (Standalone or Native per §2 above).
- Identity providers matching your existing federated connections (OIDC / SAML / OAuth2 / AD-LDAP per Auth §5).
- Attribute mapping + group sync configured to match your current vendor's behaviour (Auth §5.6–5.7).
- Transactional email — either BYO matching your existing email provider, or Gate platform-hosted if you're consolidating (Auth §8).
- Audit and SIEM forwarding matching your current observability path (Security §2.6).
At this phase no live traffic flows through Gate yet — provision-and-test only.
Phase 3 — User-data migration
User-data migration shape depends on what your existing vendor exposes:
| Vendor export shape | Migration path |
|---|---|
| Bulk export with Argon2id / bcrypt hashes | Direct import via Gate user-import tooling; hash format preserved. Argon2id hashes work natively; bcrypt hashes are re-hashed on first sign-in (transparent to the user). |
| Bulk export with proprietary hash format | Federated migration — point Gate at your existing vendor as an OIDC / SAML / OAuth2 provider for a transition window; users transparently migrate as they sign in; the migration window closes after a configurable timeout. |
| Federated-only (no local passwords) | Re-configure your IdP connections under Gate; no user-data export needed. |
| External directory (AD / LDAP) | Configure ACTIVE_DIRECTORY / LDAP provider under Gate; users authenticate against your existing directory immediately. |
Account state (verified / pending / locked / deleted) and MFA enrollment state migrate alongside user rows. Recovery codes do not migrate — users re-enroll their MFA factors on first authenticated sign-in post-migration; the migration window keeps the existing vendor's MFA in force until each user completes Gate-side enrollment.
Phase 4 — Cutover
Cutover is a DNS / SDK-config flip:
- Standalone path — replace your existing vendor's SDK import with
@k9o/gate; replace the vendor-specific configuration values (issuer / tenant / app-id / etc.) with the Gate project's API URL and credentials. Per-method API call signatures change per the per-vendor mapping table on the sub-pages below. - Native path — additional configuration to adopt the
X-K9o-Projectrequest header convention and the per-project token-issuance pattern bound in Auth §3.1.
Roll out gradually: enable Gate for a fraction of traffic (a feature flag, an A/B percentage, a single application tier) and monitor sign-in success rates, MFA challenge completion, and audit-event throughput before widening exposure. Most migrations cut over within two to four weeks of Phase 2 commencement.
4. Per-vendor migration guides
Vendor-specific sub-pages cover the API-shape mapping, code walkthrough, and gotchas particular to each migration path.
| Source vendor | Guide |
|---|---|
| Auth0 | Migrating from Auth0 |
Auth0 is the published per-vendor guide. Clerk, Stytch, Okta, WorkOS, Entra ID, and Google Workspace use the same migration shape; request a specific guide via support if your migration path needs one.
5. See also
- API → Auth — the canonical Gate API surface.
- Gate Overview — Standalone vs Native consumption paths.
- Identity-Aware Kernel — the conceptual model.
- API → Security — RBAC, audit log, SIEM forwarding.
- Pricing — usage-based pricing and plan bundles.