OPEN SWARM — WINDOWS HOME SETUP Reviewed 29 October 2026 Home setup / Windows Give that laptopa useful new job. One command in PowerShell installs what is missing and the product, creates your administrator, and ends at the sign-in page. Then add the applications your household needs. Install now ↗ (#install)Watch the walkthrough ↗ (https://oswarm.ai/watch/windows-home-setup/) Native kernel · 29 October 2026 Packaged. One command. No compiler, no source checkout. The installer is a readable PowerShell script served from this site. It installs Docker Desktop when it is missing, downloads the published kernel image and PostgreSQL, creates persistent storage, sets a real administrator password, stages the public application catalog, and prints the address and the password. Open Swarm is the product name; the local software keeps its OSHAL identifiers. 1 · What you need (#prepare)2 · Install (#install)3 · Sign in (#signin)4 · Connect intelligence (#ai)5 · Add home apps (#apps)6 · Add your household (#family)7 · Everyday operations (#maintain) 1. What you need. An updated Windows 10 or 11 PC with virtualization enabled in its firmware (most are), 8 GB of memory or more, about 4 GB of free disk for the images, and an internet connection. Nothing else: the installer brings WSL 2 and Docker Desktop when they are missing. You also want an AI provider key, or a local model endpoint, for step 4. 2. Install. Press the Windows key, type Terminal, open it, paste this line and press Enter: irm https://oswarm.ai/install.ps1 | iex What happens, in order: - WSL. If the Windows Subsystem for Linux is not enabled, the installer enables it (Windows asks for permission) and asks you to restart. After the restart, open Terminal and paste the same line again. - Docker Desktop. Installed with winget when it is missing (Windows asks for permission once), then started. Its first start shows a terms window; accept it. The installer waits for the engine. - The product. The kernel image (about 1.4 GB) and PostgreSQL are downloaded; the installation directory %USERPROFILE%\oswarm is created and restricted to your account; the database starts; your administrator password is set; the kernel starts. - The catalog. One reviewed commit of the public application catalog is downloaded and staged. Nothing is activated yet. - Done. The address, the administrator name and the generated password are printed, and the browser opens the sign-in page. To choose the administrator name, the directory, the port or your own password, set these before the command in the same PowerShell window: $env:OSWARM_ADMIN='parent', $env:OSWARM_DIR="$env:USERPROFILE\FamilySwarm", $env:OSWARM_PORT=38789, $env:OSWARM_ADMIN_PASSWORD='...' (12 characters or more). Running the command a second time on the same PC starts the existing installation; it never resets a password and never deletes data. 3. Sign in. The browser opens http://127.0.0.1:38788/login (http://127.0.0.1:38788/login). Sign in with the administrator name and the password the installer printed. The password is shown once and stored nowhere; save it in your password manager now. 4. Connect intelligence. The installed default provider answers nothing and costs nothing. Open Connections, add the provider you use (OpenAI, Anthropic, DeepSeek, OpenRouter, Ollama, vLLM, LiteLLM, or your own compatible endpoint), choose the model, and run a small request. Image generation, transcription, speech, and video have separate provider settings. The installation and its files stay on the PC. A cloud model still receives the context sent to it for each request. A suitable local model on a more capable computer is a separate choice. 5. Add the applications your household uses. The public catalog is already staged. Open the App Loader, preview the applications you want with their dependencies, install them, and assign people the relevant application roles. Life Start with household organization: shopping lists, plans, and calendar workflows. Little Monsters Create classes, record lectures, and build study materials. Configure transcription and other providers needed by the features you choose. Media and games Add these when useful. Storage, transcoding, and simultaneous sessions add their own resource needs. Business applications are in the same catalog but are not installed by default. Preview dependency requirements before selecting a package; a learning workspace can depend on shared tools such as presentations. 6. Give each person a place. Create or invite family members through Users. Keep everyday accounts separate from the administrator. Assign the selected application roles, then share supported resources intentionally. Test one private item and one shared item using two ordinary accounts before adding personal information. For a phone or another computer, connect to an authenticated address for this installation. 127.0.0.1 on a phone means the phone itself. The starter configuration binds the portal to the laptop’s loopback interface; remote access needs your supported authenticated gateway or private network setup. 7. Everyday operations. The installer leaves a copy of itself in the installation directory. From PowerShell: & "$env:USERPROFILE\oswarm\oswarm.ps1" status & "$env:USERPROFILE\oswarm\oswarm.ps1" stop & "$env:USERPROFILE\oswarm\oswarm.ps1" start & "$env:USERPROFILE\oswarm\oswarm.ps1" logs & "$env:USERPROFILE\oswarm\oswarm.ps1" upgrade Stopping and starting preserve the database and kernel data. Keep the installation directory private: it holds the database credentials and the vault key. Back up the two Docker volumes and the directory together as one recoverable installation. Do not delete volumes to fix a startup problem; read logs first. uninstall -Purge removes the containers, all data and the directory. What was exercised The same installer, run with PowerShell on Linux against Docker Engine: a fresh installation from an empty directory, sign-in with the generated password, wrong-password rejection, the staged catalog, stop and start, a second run that kept the password, and uninstall. The Windows-only steps (WSL, winget, Docker Desktop) follow the vendors’ documented commands and still need a Windows hardware run. Watch the walkthrough ↗ (https://oswarm.ai/watch/windows-home-setup/)Users and AI configuration ↗ (https://oswarm.ai/guides/users-and-ai/)