Migrate from Supabase to Neon

Neon Auth provides a Supabase-compatible API, and Neon Data API provides PostgreSQL database access. This guide shows how to migrate from Supabase to Neon.

Prerequisites

• A Neon project (create one here)
• Data API enabled (Neon Auth is enabled by default when you enable Data API):
  • Go to Data API in the Neon Console and enable it
  • In Data API → Configuration, verify it's configured with Neon Auth
  • Copy your Data API base URL and Auth URL from the Console - you'll need both

1. Install Neon SDK

   Replace the Supabase SDK with Neon's:

   Terminal

   npm uninstall @supabase/supabase-js
   npm install @neondatabase/neon-js

2. Update environment variables

   Replace your Supabase credentials with your Neon Auth and Data API URLs:

   .env

   # Remove these:
   # VITE_SUPABASE_URL=https://your-project.supabase.co
   # VITE_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
   
   # Add these:
   VITE_NEON_AUTH_URL=https://ep-xxx.neonauth.us-east-2.aws.neon.build/neondb/auth
   VITE_NEON_DATA_API_URL=https://ep-xxx.us-east-2.aws.neon.build/neondb/rest/v1

   Get your URLs:

   1. Auth URL: Go to Auth → Configuration in the Neon Console
   2. Data API URL: Go to Data API in the Neon Console

   note

   The VITE_ prefix is for Vite. Use NEXT_PUBLIC_ for Next.js, or no prefix for Node.js.

3. Update client initialization

   Find your Supabase client file, typically src/supabase.ts or src/lib/supabase.ts, and update it:

   Before (Supabase):

   src/supabase.ts

   import { createClient } from '@supabase/supabase-js';
   
   export const supabase = createClient(
     process.env.VITE_SUPABASE_URL!,
     process.env.VITE_SUPABASE_ANON_KEY!
   );

   After (Neon):

   src/auth.ts

   import { createClient, SupabaseAuthAdapter } from '@neondatabase/neon-js';
   
   export const client = createClient({
     auth: {
       url: import.meta.env.VITE_NEON_AUTH_URL,
       adapter: SupabaseAuthAdapter(),
     },
     dataApi: {
       url: import.meta.env.VITE_NEON_DATA_API_URL,
     },
   });

   This example renames the file to auth.ts and the variable to client for a provider-agnostic setup. You can use any naming, just stay consistent throughout your codebase.

   Find all files that import this client and update them:

   // Before
   import { supabase } from './supabase';
   
   // After
   import { client } from './auth';

4. Your auth code stays the same

   After updating imports, use find/replace to change all instances throughout your codebase:

   supabase. → client.

   Your authentication methods, parameters, and responses work identically. Your components, hooks, and auth flows don't change.

   Auth methods

   // Sign up
   await client.auth.signUp({ email, password });
   
   // Sign in with password
   await client.auth.signInWithPassword({ email, password });
   
   // OAuth sign in
   await client.auth.signInWithOAuth({ provider: 'google' });
   
   // Get current user
   const {
     data: { user },
   } = await client.auth.getUser();
   
   // Get session
   const {
     data: { session },
   } = await client.auth.getSession();
   
   // Sign out
   await client.auth.signOut();

5. Your database queries stay the same

   Your existing client.from() queries work without any code changes:

   // Same as Supabase - no changes needed
   const { data: posts } = await client.from('posts').select('*');
   const { data: user } = await client.from('users').select('*').eq('id', userId).single();

   note

   For production apps, use Row Level Security (RLS) to secure your data. See our RLS with Drizzle guide for the recommended setup.

6. Test the migration

   Run your app:

   Terminal

   npm run dev

   Test your app:

   1. Sign up a new user
   2. Sign in with that user
   3. Verify the session persists across page reloads
   4. If you enabled Data API: Test user actions that involve database queries (creating posts, loading lists, etc.)

   Your authentication and database queries should work the same as they did with Supabase.

   Verify users in Neon Console:

   Go to Auth → Users in the Neon Console to see your newly created users, or query directly:

   SQL Editor

   SELECT id, email, "createdAt"
   FROM neon_auth.user
   ORDER BY "createdAt" DESC;

What changed?

API compatibility

Neon Auth supports most Supabase Auth methods including sign up, sign in (password and OAuth), session management, user updates, and email verification. See the Neon Auth & Data API TypeScript SDKs for the complete API.

Not supported:

Different behavior:

If you're using any unsupported methods or verification flows, you'll need to adjust your implementation.