How to Configure Windows Sandbox Local Supabase Studio and Auth via XML in Windows 11

Modern full-stack web applications frequently build against Supabase as an open-source Firebase alternative, leveraging its PostgreSQL backend, GoTrue authentication service, PostgREST instant API layer, and Supabase Studio dashboard. However, bootstrapping a full local Supabase development environment on a primary development machine often leaves behind complex network configurations, container images, and database volumes. Windows Sandbox in Windows 11 Pro and Enterprise offers an ephemeral, hardware-isolated hypervisor instance that provides an ideal platform for running disposable Supabase test instances.

By defining automated Windows Sandbox configuration files (.wsb) and PowerShell scripts, developers can spin up a fully isolated Supabase testing stack with a single double-click, test migrations and authentication flows, and tear down the environment instantly upon completion.

Windows Sandbox Architecture and Isolation Benefits

Windows Sandbox operates as a lightweight, pristine virtual machine based on your host operating system’s image. All software installations, environment variables, and file modifications remain completely isolated from the host OS and are discarded when the sandbox closes. A .wsb XML file configures sandbox capabilities:

• <Networking>: Must be Enable to download the Supabase CLI, Node.js runtimes, and dependencies.
• <MappedFolders>: Maps a host directory into the sandbox to pass setup scripts and export database schema dumps.
• <LogonCommand>: Executes PowerShell bootstrap commands automatically upon desktop initialization.

Creating the Supabase Automated Bootstrap Script

Create a directory on your host machine (e.g., C:\Sandbox\Supabase) and save the following script as bootstrap-supabase.ps1:

# bootstrap-supabase.ps1 - Automated Supabase Setup for Windows Sandbox
$ErrorActionPreference = "Stop"

Write-Host "Initialising Supabase Sandbox Environment..." -ForegroundColor Cyan

# Install Supabase CLI via winget
Write-Host "Installing Supabase CLI..." -ForegroundColor Yellow
winget install Supabase.CLI --silent --accept-package-agreements --accept-source-agreements

# Refresh environment variables
$env:Path = [System.Environment]::GetEnvironmentVariable("Path","Machine") + ";" + [System.Environment]::GetEnvironmentVariable("Path","User")

# Set up project workspace
$projDir = "C:\SupabaseTest"
New-Item -ItemType Directory -Path $projDir -Force
Set-Location $projDir

# Initialise Supabase project configuration
Write-Host "Initialising Supabase project configuration..." -ForegroundColor Yellow
supabase init

Write-Host "Supabase CLI configured successfully." -ForegroundColor Green
Write-Host "Project ready at $projDir" -ForegroundColor Cyan

# Launch Microsoft Edge with Supabase local development documentation
Start-Sleep -Seconds 3
Start-Process "msedge.exe" -ArgumentList "https://supabase.com/docs/guides/cli/local-development"

Authoring the Windows Sandbox WSB Configuration File

In the same folder, create a configuration file named SupabaseSandbox.wsb:

<Configuration>
  <VGpu>Enable</VGpu>
  <Networking>Enable</Networking>
  <MappedFolders>
    <MappedFolder>
      <HostFolder>C:\Sandbox\Supabase</HostFolder>
      <SandboxFolder>C:\SupabaseSetup</SandboxFolder>
      <ReadOnly>true</ReadOnly>
    </MappedFolder>
  </MappedFolders>
  <LogonCommand>
    <Command>powershell.exe -ExecutionPolicy Bypass -NoExit -File C:\SupabaseSetup\bootstrap-supabase.ps1</Command>
  </LogonCommand>
</Configuration>

Running and Testing Supabase in Windows Sandbox

1. Double-click SupabaseSandbox.wsb on your Windows 11 host.
2. Windows Sandbox boots into a clean desktop environment and launches PowerShell automatically.
3. The script installs the official Supabase CLI silently and initializes a local project configuration structure.
4. Developers can test schema migrations, inspect config.toml settings, and experiment with database seeds safely.
5. When testing concludes, close the Windows Sandbox window; all temporary CLI binaries, configuration files, and downloaded data are erased immediately.

This automated approach provides an efficient, clean environment for testing Supabase database architectures on Windows 11 without polluting your primary workstation.