Future Cloud paid plans
We plan transparent per-token and per-sandbox-second metering and are evaluating BYOK. These are not current v0.2.0 capabilities or pricing commitments.
Pricing
Solo and Cloud v0.2.0 are currently free.
Solo is MIT-licensed open source. Cloud is live as Stable v0.2.0 with API keys and daily quotas, but no paid plans, metered bill, or SLA.
Alpha
Free. Forever-MIT core. No phone-home.
Run as many Solo instances as you want, on as many machines as you want. No telemetry, no usage caps, no signup. The only limit is your hardware.
- MIT-licensed — fork, embed, resell.
- No telemetry, no analytics, no remote config.
- Bring your own LLM keys — Claude / GPT / Qwen / Ollama.
- Signed SoyaPacks, capability tokens, audit trail.
When we monetize
The plan after GA.
Cloud v0.2.0 is live and free. The paid, BYOK, sandbox, and enterprise capabilities below are not live and are not being billed.
Enterprise
Annual seats + dedicated regions + SSO/SAML + SOC 2. Signed audit log export, offline upgrade bundles, support contracts with response-time SLAs.
Core kernel + SoyaPack + CLI
Always MIT. The format never gets a paid tier — if it did, the “portable agent” promise would die the moment we tried to monetize it.
Forge & Studio
Forge (the Agent Factory) and Studio (the local UI) are MIT-licensed and embedded in the same binary as the kernel. They ship together, they version together.
Will the MIT core ever get a paid tier?
No. The kernel, SoyaPack manifest format, CLI, Forge and Studio will always be MIT. Paid tiers attach to operations we run on your behalf — never to the format or the binary itself.
Can I commercially deploy SoyaOS today?
Yes — MIT means yes. The alpha label is about API stability, not legal restriction. Ship it; just pin a release and read CHANGELOG before upgrading.