VediramSystem Requirements
The Windows edition, hardware, software, and permissions a computer needs to run Levee
Levee needs a 64-bit Windows 11 Pro, Enterprise, or Education computer, version 22H2 or later, with at least 8 GB of memory and 30 GB of free disk space. It does not run on Windows 11 Home, Windows 10, or Windows Server.
Most of the detail below is for the IT team that prepares the computer. As a user, you do not need administrator rights to use Levee day to day.
Which Windows versions are supported?
| Requirement | Details |
|---|---|
| Windows edition | Windows 11 Pro, Enterprise, or Education (including Pro for Workstations, Pro Education, and Enterprise LTSC). |
| Windows build | Windows 11 version 22H2 (build 22621) or later. |
| Architecture | 64-bit x64 (AMD64). ARM64 devices are not supported. |
| Not supported | Windows 11 Home and Windows 10 (any edition). Windows Server is not supported as a Levee host. |
Why not Windows 11 Home? Levee's sandbox is a Windows container. Windows containers are only available on the Pro, Enterprise, and Education editions of Windows 11.
The installer checks these requirements before it changes anything:
- A 32-bit system fails with:
Levee requires 64-bit Windows. - An unsupported edition fails with a message that starts:
Levee requires Windows 11 Pro, Enterprise, or Education. - A build older than 22621 fails during host preparation with
Windows build <n> is below the required 22621 (Windows 11 22H2).and the installation rolls back.
To check a computer, run this in PowerShell:
Get-ComputerInfo -Property OsName, OsBuildNumber, OsArchitecture, WindowsEditionId
$env:PROCESSOR_ARCHITECTURE # must be AMD64
Hardware
You need at least 8 GB of memory and 30 GB of free disk space. No special processor or graphics card is needed.
| Resource | Minimum | Recommended | Notes |
|---|---|---|---|
| Memory | 8 GB | 16 GB | A running sandbox uses roughly 300 to 600 MB, plus what the agent's work needs. Each sandbox is limited to 4096 MB by default (configurable, see Container settings). |
| Free disk on the system drive | 30 GB | More if users keep many large projects | The container runtime image takes several GB. Levee also keeps 20 GB of headroom free before it downloads a runtime image (configurable). |
| CPU virtualization (VT-x / AMD-V) | Not required | Levee's sandboxes do not use a hypervisor. | |
| GPU | Not used | Agents run on the CPU only. |
Only one project runs on a computer at a time, so memory is needed for one sandbox, not several.
For your IT team
Windows features and components
Levee runs its sandboxes as Windows containers with process isolation. That is why the Windows Containers feature is needed and Hyper-V is not.
| Feature or component | Required? | Notes |
|---|---|---|
| Containers | Yes | Must be enabled, followed by a restart. The installer does not enable it. See Installation. |
LeveeFS driver and LeveeFSHost service | Yes | The component that shows shared files inside the sandbox. The Levee installer installs both. |
Hyper-V (Microsoft-Hyper-V) | No | Levee never uses Hyper-V isolation. It is safe to leave it on if your baseline needs it for other reasons (WSL2, Windows Sandbox, Credential Guard). |
| Virtual Machine Platform / WSL2 | No | Coexists with Levee. |
Runtimes
Levee's service and its policy channels need the Microsoft .NET 8 runtimes on the computer:
| Runtime | Needed by | Checked by the installer? |
|---|---|---|
| ASP.NET Core Runtime 8.x (x64) | Levee service and its policy channels | Yes. The install fails without it: ASP.NET Core 8 runtime not found ... Install 'ASP.NET Core Runtime 8.x' from https://dotnet.microsoft.com/download/dotnet/8.0 |
| .NET Desktop Runtime 8.x (x64) | Levee desktop app | No. Install it before users open the app. |
| Microsoft Edge WebView2 Runtime | Levee desktop app | No. Included with Windows 11. |
Install both .NET runtimes with winget:
winget install --id Microsoft.DotNet.AspNetCore.8 --architecture x64 --silent --accept-package-agreements --accept-source-agreements
winget install --id Microsoft.DotNet.DesktopRuntime.8 --architecture x64 --silent --accept-package-agreements --accept-source-agreements
You do not need Docker, Docker Desktop, Git, Python, or Node.js on the computer. The sandbox image already includes PowerShell 7, Git, Python, and Node.js. Git on the computer is optional: if it is there, Levee uses it to start a history for new projects and to save a checkpoint when a project stops.
Virtual desktops (VDI)
Levee does not need nested virtualization, so it runs in Windows 11 virtual machines on any hypervisor, as long as the guest meets the edition and build requirements above:
| Platform | Supported |
|---|---|
| Physical Windows 11 Pro / Enterprise / Education | Yes |
| Windows 365 Cloud PC (single-user Windows 11 Enterprise) | Yes, any size |
| Azure Virtual Desktop, personal host pools on Windows 11 Enterprise | Yes |
| Azure Virtual Desktop, Windows 11 Enterprise multi-session | No |
| VMware Horizon, Citrix, Nutanix AHV, or other hypervisors (single-user Windows 11 guests) | Yes. No nested virtualization setting is needed. |
Network
The Levee service on the computer needs outbound HTTPS to:
downloads.vediram.com, to download the container runtime image. Air-gapped computers can use a local mirror or a pre-staged image instead. See Container runtime.- The model providers, websites, and search providers your policy allows. The agent's traffic leaves from the computer, not from inside the sandbox.
- Vediram Cloud, if you connect devices to Vediram Cloud.
Levee uses the computer's system proxy settings for outbound traffic. See Planning a deployment.
Permissions
| Task | Needs administrator rights? |
|---|---|
| Install, repair, upgrade, or uninstall Levee | Yes |
Enable the Windows Containers feature | Yes (plus a restart) |
Write policy.json or tenant-config.json, publish AI tools, or install plugins under %ProgramData%\Vediram\Levee | Yes |
Store package-registry credentials (levee upstream-auth set / clear) | Yes |
Read machine-wide logs (levee log tail --all) | Yes |
| Start or restart the Levee services | Yes |
| Use the Levee app: create projects, share files, run agents, answer approvals, fill in your plugin values | No. Everyday use works as a standard user. |
Read your own logs and the audit log (levee log tail, levee audit tail) | No |
Next steps
- Install Levee on one computer.
- Planning a rollout to many computers? Start with Planning a deployment.