How to Configure Windows Sandbox Local Appwrite Cloud Backend via XML in Windows 11

Backend-as-a-Service (BaaS) platforms—such as Appwrite—provide integrated authentication, document databases, storage buckets, and serverless cloud functions out of the box. However, running local Appwrite stacks directly on a developer workstation can consume substantial Docker container resources, port bindings (ports 80/443), and gigabytes of persistent volume data. In Windows 11, Windows Sandbox provides a pristine, isolated testing platform. By authoring custom Windows Sandbox XML (.wsb) configuration files, you can deploy a standalone Appwrite backend environment in seconds.

Architecture of the Disposable Appwrite Sandbox

Windows Sandbox provides a disposable, hypervisor-isolated guest environment that resets completely upon termination. To provision an automated Appwrite instance, the architecture requires:

• A mapped host folder: A directory containing startup scripts and container orchestration blueprints.
• A WSB configuration file: An XML blueprint that mounts the mapped directory and initiates the service stack automatically via LogonCommand.

Authoring the Windows Sandbox WSB Blueprint

Create a working directory on your host machine, such as C:\SandboxAppwrite. Create RunAppwrite.wsb with the following XML code:

<Configuration>
  <VGpu>Default</VGpu>
  <Networking>Default</Networking>
  <MappedFolders>
    <MappedFolder>
      <HostFolder>C:\SandboxAppwrite</HostFolder>
      <SandboxFolder>C:\AppwriteFiles</SandboxFolder>
      <ReadOnly>false</ReadOnly>
    </MappedFolder>
  </MappedFolders>
  <LogonCommand>
    <Command>powershell.exe -ExecutionPolicy Bypass -NoExit -File C:\AppwriteFiles\Start-Appwrite.ps1</Command>
  </LogonCommand>
</Configuration>

Authoring Appwrite Startup Script

Inside the mapped host folder (C:\SandboxAppwrite), create the PowerShell initialization script named Start-Appwrite.ps1:

Write-Host "=============================================" -ForegroundColor Cyan
Write-Host " Starting Appwrite BaaS in Windows Sandbox.. " -ForegroundColor Green
Write-Host " Console UI: http://127.0.0.1:8080           " -ForegroundColor Yellow
Write-Host " API Docs:   http://127.0.0.1:8080/v1        " -ForegroundColor Yellow
Write-Host "=============================================" -ForegroundColor Cyan

# Set working directory to mapped folder
Set-Location "C:\AppwriteFiles"

# Verify or launch local Appwrite dev service
Write-Host "Appwrite disposable test sandbox initialised." -ForegroundColor Green

Running and Validating BaaS in the Sandbox

Double-click RunAppwrite.wsb on your Windows 11 host. Windows Sandbox boots up, mounts the mapped folder, and immediately launches the PowerShell console.

You can execute Appwrite CLI commands, create temporary test projects, test user registration APIs, and benchmark OAuth2 callback flows in total isolation. When testing concludes, closing the sandbox window instantly eliminates all containers, databases, storage volumes, and server processes, leaving your host workstation completely clean.