Use case

Replace Clerk, keep your own database

AscendKit gives you Clerk-grade drop-in auth components and a hosted dashboard while user records stay in your own database, not a hosted store. Auth executes in your app and AscendKit acts as the control plane, so you get the developer experience without the lock-in. AscendKit also ships a user import path, so an existing Clerk user base can be migrated.

How it works

  1. 1. Install and configure
    Add @ascendkit/nextjs, set your public key, and drop in the auth-card, login, and user-button components in place of Clerk's.
  2. 2. Point auth at your database
    User records are created as usr_ profiles in your own data store through the SDK adapter rather than a hosted user store.
  3. 3. Import existing users
    Migrate your current Clerk user base through the import path so accounts carry over without forcing a reset.

FAQ

Where do my users live after moving off Clerk?

In your own database. AscendKit keeps auth in your app and uses the backend as a control plane, so there is no hosted user store to lock you in.

Can I migrate my existing Clerk users?

Yes. AscendKit has been used to migrate a live customer off Clerk via its user import path, so existing accounts move over rather than starting fresh.

Start with one API key

Auth, email, surveys, and journeys share one user record, so you ship this without stitching vendors together.

Start free