Rekey

The question worth answering before you adopt anything is how much work is this. Here is the whole flow: signing in, creating an Application, minting a key, configuring auth, and proving it works with three lines of SDK code. Under a minute, start to finish.

It starts muted, so nothing makes noise at you. Unmute for the walkthrough, or turn on captions. The API key is blurred here; yours is shown once and then only ever stored as a hash.

What happens, in order

  1. Sign in to the operator panel

    One operator account, one workspace. On Rekey Cloud there is nothing to install first. Self-hosted, the panel comes up with the stack.

  2. Create an Application

    Name, slug, environment. An Application is a self-contained pool of end users with its own auth config, keys and billing.

  3. Mint a server API key

    Shown exactly once, then only a SHA-256 hash is stored. It is blurred here; your panel shows it in full.

  4. Configure auth and redirect URLs

    Turn on email + password and magic link, add the callback URL your app returns to. Changes apply to new sign-ins immediately.

  5. Prove it works

    Three calls through @rekey.dev/node with the key just minted: the Application resolves, an end user signs up, and getCurrentUser reads them back.

What you are looking at

Everything on screen is sample data, and the key is blurred because a secret key is shown exactly once and then only ever stored as a hash. Yours behaves the same way.

Nothing is sped up. The pauses are the API answering, so what you see is what the work actually takes.

This is the Rekey side of the job. The other side is what you type in your own project, and the framework walkthroughs cover it: an empty directory to a working sign-in in Next.js, and to a token-protected route in NestJS.

Prefer to read it? The operator-panel walkthrough covers the same ground in writing, with screenshots of every page.

Watch: configuring an Application | Rekey