Before you begin

Do not configure the hosted project until the application and migrations work locally. Starting from a known-good local baseline makes hosted configuration problems much easier to identify.

Required baseline

Confirm all of the following:

• Node.js 22 or later is active.
• Dependencies are installed with the package manager declared by the application.
• Docker and the local Supabase stack start successfully.
• The local database resets cleanly and its tests pass.
• Generated database types are current.
• The application builds and the authentication pages load locally.
• You can sign in to the Supabase CLI.
• You have Owner or Administrator access to the intended hosted Supabase project.
• The application repository is connected to the intended Vercel project.
• You know which branch Vercel treats as Production.

Run the application-provided checks rather than inventing substitute commands. A typical Supacharger project exposes commands for reset, database lint, type generation, application lint, type checking, and build.

npx supabase status
supacharger doctor
npm run build

supacharger doctor checks names and local configuration. It does not contact a linked project, print secret values, or prove that hosted Dashboard settings match the repository.

Tooling connections

If you use an AI coding agent, connect and authenticate the Supabase and Vercel MCP servers now. Confirm that each connection points at the intended account and project before allowing it to inspect or change hosted configuration.

MCP is optional. The production application communicates with Supabase and Vercel through its normal runtime configuration, not through MCP.

Record the deployment targets

Write down these values before continuing:

Value	Example
Supabase organization and project name	Acme / Acme Production
Supabase project reference	abcdefghijklmnopqrst
Vercel team and project name	Acme / acme-app
Production branch	main
Local application origin	http://localhost:3000
Intended production origin	https://app.example.com

Treat the intended production origin as provisional until the domain is attached and responds over HTTPS in step 4.

Choose application policy

Edit the developer-owned src/supacharger.config.ts before configuring Supabase Dashboard. Decide:

• whether users can sign in and sign up with email and password;
• whether magic-link sign-in is available and may create accounts;
• whether sign-up verification is disabled, link, or otp;
• whether usernames are disabled, optional, or required;
• whether post-sign-in onboarding is required and its real destination route;
• whether organizations are enabled and have a complete onboarding journey;
• which social providers are visible; and
• whether mobile deep linking is actually ready for the production host and signed native application identifiers.

The hosted settings must enforce the same policy as the application. Hiding a button in the UI does not disable a Supabase Auth method.

Completion check

Continue only when:

• the local build and database checks pass;
• the hosted project identities have been recorded; and
• src/supacharger.config.ts expresses the intended authentication policy.

Next: Connect hosted Supabase.