Skip to content
Migrating from NextAuth.js v4? Read our migration guide.
Getting Started

EdgeDB Adapter




npm install edgedb @auth/edgedb-adapter
npm install @edgedb/generate --save-dev

Ensure you have the EdgeDB CLI installed. Follow the instructions below, or read the EdgeDB quickstart to install the EdgeDB CLI and initialize a project

Environment Variables



import NextAuth from "next-auth"
import { EdgeDBAdapter } from "@auth/edgedb-adapter"
import { createClient } from "edgedb"
const client = createClient({ dsn: process.env.AUTH_EDGEDB_DSN })
export const { handlers, auth, signIn, signOut } = NextAuth({
  adapter: EdgeDBAdapter(client),
  providers: [],


Linux or macOS

curl --proto '=https' --tlsv1.2 -sSf | sh


iwr -useb | iex

Check that the CLI is available with the edgedb --version command. If you get a Command not found error, you may need to open a new terminal window before the edgedb command is available.

Once the CLI is installed, initialize a project from the application’s root directory. You’ll be presented with a series of prompts.

edgedb project init

This process will spin up an EdgeDB instance and “link” it with your current directory. As long as you’re inside that directory, CLI commands and client libraries will be able to connect to the linked instance automatically, without additional configuration.


Replace the contents of the auto-generated file in dbschema/default.esdl with the following:

module default {
    type User {
        property name -> str;
        required property email -> str {
            constraint exclusive;
        property emailVerified -> datetime;
        property image -> str;
        multi link accounts := .<user[is Account];
        multi link sessions := .<user[is Session];
        property createdAt -> datetime {
            default := datetime_current();
    type Account {
       required property userId :=;
       required property type -> str;
       required property provider -> str;
       required property providerAccountId -> str {
        constraint exclusive;
       property refresh_token -> str;
       property access_token -> str;
       property expires_at -> int64;
       property token_type -> str;
       property scope -> str;
       property id_token -> str;
       property session_state -> str;
       required link user -> User {
            on target delete delete source;
       property createdAt -> datetime {
            default := datetime_current();
       constraint exclusive on ((.provider, .providerAccountId))
    type Session {
        required property sessionToken -> str {
            constraint exclusive;
        required property userId :=;
        required property expires -> datetime;
        required link user -> User {
            on target delete delete source;
        property createdAt -> datetime {
            default := datetime_current();
    type VerificationToken {
        required property identifier -> str;
        required property token -> str {
            constraint exclusive;
        required property expires -> datetime;
        property createdAt -> datetime {
            default := datetime_current();
        constraint exclusive on ((.identifier, .token))
# Disable the application of access policies within access policies
# themselves. This behavior will become the default in EdgeDB 3.0.
# See:
using future nonrecursive_access_policies;


  1. Create a migration
edgedb migration create
  1. Apply the migration
edgedb migrate

To learn more about EdgeDB migrations check out the Migrations docs.


npx @edgedb/generate edgeql-js

This will generate the query builder so that you can write fully typed EdgeQL queries with TypeScript in a code-first way.

const query =, () => ({
  id: true,
  email: true,
  emailVerified: true,
  name: true,
  image: true,
  filter_single: { email: "" },
return await


Deploy EdgeDB

First deploy an EdgeDB instance on your preferred cloud provider:

Find your instance’s DSN

The DSN is also known as a connection string. It will have the format edgedb://username:password@hostname:port. The exact instructions for this depend on which cloud provider you’re deploying to.

Set an environment variable


Apply migrations

Use the DSN to apply migrations against your remote instance.

edgedb migrate --dsn <your-instance-dsn>

Set up a prebuild script

Add the following prebuild script to your package.json. When your hosting provider initializes the build, it will trigger this script which will generate the query builder. The npx @edgedb/generate edgeql-js command will read the value of the EDGEDB_DSN environment variable, connect to the database, and generate the query builder before your hosting provider starts building the project.

"scripts": {
  "dev": "next dev",
  "build": "next build",
  "start": "next start",
  "lint": "next lint",
+  "prebuild": "npx @edgedb/generate edgeql-js"
Auth.js © Balázs Orbán and Team - 2024