Supabase Local Manager

Windows

Node, Docker Desktop and the cross-platform launcher. The Windows-specific helpers, ports and data folders.

On this page
  1. What is supported
  2. Open and sign in
  3. Windows helpers
  4. If it goes wrong

What is supported

The manager runs on Windows as a Node application. The repository includes a cross-platform launcher and a set of PowerShell helpers: an interactive start-all.ps1 at the root, plus scripts for starting dev detached, restarting the backend or frontend, killing dev processes and listing the ports in use. Docker Desktop provides the Docker daemon that managed projects need.

Node.js 18 or later must be installed and available on PATH. The setup script checks it strictly. npm ships with Node. The Supabase CLI is resolved through npx and downloaded on first use.

Install on Windows

  1. Check Node and npm

    Open PowerShell and confirm both are available.

    node --version
npm --version

  2. Start Docker Desktop

    Wait until Docker reports that the engine is running. A project cannot start without it.

  3. Check the Supabase CLI

    Confirm that npx can resolve the CLI. The first call may download it.

    npx supabase --version

  4. Install the workspaces

    From the repository root, change into the product folder and install.

    cd my-supabase-app
npm install

  5. Generate the environment file

    Setup writes .env and prints the administrator credential once.

    npm run setup

  6. Start the dev stack

    The cross-platform launcher avoids the nested-concurrently problem on Windows.

    node scripts/start.mjs

Open and sign in

Open http://localhost:5173 and use the administrator account printed by setup. The manager API and WebSocket listen on PORT, bound to 127.0.0.1; the example environment file uses 24084 and the code fallback is 24085. If Vite cannot reach the API, the development proxy is pointing at the wrong port; start through the root launcher so both processes share the right environment.

Windows helpers

start-all.ps1 offers a menu for a full dev run, backend only, frontend only, production, a prerequisites check and a build-then-production run. scripts/ports.ps1 lists the listeners on the manager, Vite, proxy, front-door and pooler ports with their owning process. scripts/kill-dev.ps1 stops the development processes. scripts/restart-backend.ps1 and scripts/restart-frontend.ps1 restart one half without the other.

If it goes wrong

  • No backend logs and no ports bound. The nested concurrently chain can wedge on Windows. Run node scripts/start.mjs instead.
  • A port is already in use. The launcher frees PORT and PROXY_PORT. It does not free the front-door port or the pooler port; stop the process holding them.
  • Docker is not running. The interface still opens, but a project start fails at preflight.
  • The signing key is missing. Run npm run setup; the backend refuses to boot without a valid JWT_SECRET and VAULT_MASTER_KEY.

Where data lives on Windows

Manager database
%APPDATA%\supabase-local-manager\Config\supabase-manager.db
Manager logs
%LOCALAPPDATA%\supabase-local-manager\Log
Project data
Inside each project's Docker volumes.
Backups
supabase\backups inside the project folder.