Core and SoAI OS use separate first-party licenses. The controlling license and accepted purchase or commercial terms remain authoritative.
Product licenses
LICENSE.md at the root of the SoAI repository contains the
SoAI Source-Available License 1.0. It governs first-party Core source, launchers, assets, documentation, and the
Plugin SDK. A natural person may inspect, copy,
run, and privately modify Core for Personal Use without a paid key or deployment limit. The license defines Personal
Use and does not authorize ordinary organization use.
The Core license allows an identified organization one internal 30-day evaluation under its evaluation terms and allows independent review, press, benchmarking, research, and teaching within the stated limits. Current commercial licenses and organization evaluations are temporarily unavailable and are not being issued. Contact info@soai.to for licensing information or the waitlist; that contact does not grant a license or promise an availability date.
Bundled plugins and your own plugin
Bundled first-party plugin packages (.soaiplugin) and
SoAI Connect are MIT Components. Their MIT terms are
separate from the Core license. Each bundled plugin package includes
LICENSES/LICENSE_SOAIPLUGIN.txt; its managed backend and other dependencies can have additional
terms. The Plugin SDK itself remains part of Core.
The Core license separately permits anyone, including an organization, to develop, publish, sell, and distribute an independently written plugin against the documented Plugin SDK. Do not package the SDK or other Core files with that plugin.
SoAI OS
SoAI OS is not yet available and is not currently distributed. Purchases, licenses, appliance media, and credentials are not being issued. Contact info@soai.to to join the waitlist; joining does not grant a license or promise an availability date.
The SoAI OS appliance edition is governed by the SoAI OS Source-Available License 1.0, not the Core license. The personal licensing framework describes a named natural person's perpetual Personal Use grant on up to three active deployments. That grant requires acceptance of the identified documents and delivery of a matching credential; it is not a current offer while distribution is unavailable.
A deployment is one independently managed SoAI OS control plane with one licensing identity. High-availability replicas count as one only when they share configuration and entitlement and cannot operate independently. A separately usable control plane is another deployment. Powered-off backup images do not consume a personal slot, and a replacement can take a slot after the prior deployment stops.
A successfully activated personal deployment validates its entitlement locally and needs no recurring online check. Organization evaluation and commercial use have separate terms and entitlement requirements. SoAI OS has no automatic MIT conversion or Core Change Date. See Licensing administration for the WebUI activation, recovery, and conversion controls.
Source licensing and operative documents
Each official Core release becomes available under the MIT License exactly four years after its first official public distribution. This date cannot be postponed, does not apply to SoAI OS, and does not convert a later Core release early.
Read the operative documents
The license documents also cover redistribution, trademarks, third-party materials, warranties, liability, export controls, notices, and governing law. Read the applicable full text before relying on a right or making a licensing decision.
Third-party trademark attribution
Third-party names and marks mentioned by SoAI include, in alphabetical order: aider, AI Horde, Amazon Web Services (AWS), AMD, Android, Anthropic, Antigravity, AnythingLLM, Apache, Apple, APT, Arch Linux, Argon2, AUTOMATIC1111, Backblaze, BotFather, Brave Search, Certbot, Chroma, Chromium, Claude, Cline, Cloudflare, Codex, ComfyUI, CrowdSec, Crush, CTranslate2, CUDA, Cursor, Debian, DeepSeek, Devin, Discord, Docker, DuckDuckGo, EasyList, Facebook, Facebook Messenger, FastAPI, Fedora, Fernet, FFmpeg, Firefox, GDELT, Gemini, Git, GitHub, GNU, Google, goose, GPT, Groq, HAProxy, Helsinki-NLP, Hermes Agent, Hugging Face, Instagram, Intel, KDE, Kilo Code, Let's Encrypt, LibreChat, Linux, LiteLLM, llama.cpp, LM Studio, macOS, MeloTTS, Mermaid, Meta, Metal, micromamba, Microsoft, Mozilla, MSN Messenger, MyShell, Namecheap, NetworkManager, Nginx, Node.js, npm, NumPy, NVIDIA, NVML, Ollama, OpenAI, OpenCL, OpenClaw, opencode, OpenHands, Open-Meteo, OpenNMT, OpenRouter, OpenSSL, OpenVINO, Open WebUI, Paddle, Pi, Playwright, Purelymail, Python, PyTorch, Qwen Code, ROCm, Roo Code, SearXNG, Serper.dev, SheetJS, Signal, SillyTavern, Slack, SQLite, Stable Diffusion, SYCL, systemd, Tavily, Telegram, Tesseract, Together AI, TypeScript, Ubuntu, Uvicorn, Visual Studio Code, vLLM, Vulkan, WhatsApp, Whisper, Windows, Windsurf, WireGuard, YouTube, and Zed. These and other third-party product, project, service, hardware, operating-system, model, API, search-provider, messaging-provider, and company names mentioned by SoAI are trademarks or other protected identifiers of their respective owners and are used for identification, compatibility description, interoperability, parser support, or nominative reference only. SoAI is not affiliated with, sponsored by, endorsed by, or approved by those third parties.
AMD, Intel, and NVIDIA hardware logos are used only to identify detected GPU hardware vendors inside SoAI hardware views.