Deployment shapes

Six editions. One kernel.

The edition describes where the control plane and workloads run and who operates them. Solo uses the local binary; Cloud v0.2.0 uses the hosted Portal and API.

$soyaos start --edition solo     # local Solo entry point

Edition	Entry point	Persona	Typical cost	Status
Solo	`soyaos start --edition solo`	One dev, one laptop.	Free · your hardware	alpha now
Cluster	`soyaos start --edition cluster`	A team + a VPS + intranet devices.	~$0.10 / Comet·hr (est.)	planned
Cloud	`developer.soyaos.ai`	Register, get an API key, ship.	currently free · daily quotas	Stable v0.2.0
Hybrid	`soyaos start --edition hybrid`	SaaS Planet, your Moon.	per-token (control plane only)	planned
Enterprise Cloud	`soyaos start --edition ent-cloud`	Multi-tenant SaaS with SSO and SLA.	contact us	planned
Enterprise Private	`soyaos start --edition ent-private`	On-prem or air-gapped.	annual license	planned

Where things run

Control plane vs. data plane, per edition.

Solo and Cloud are available now; the remaining shapes are roadmap items. Cloud v0.2.0 is a controlled text-Agent service, not the full target Cloud architecture.

Solo

alpha now

soyaos start --edition solo

Planet, Moon and Comet collapse into a single process on your machine. No registry, no auth, no network surface — the fastest way to feel SoyaOS.

Control plane: in-process
Data plane: in-process

Cluster

planned

soyaos start --edition cluster

One Planet you run, Comets you scale. Auth via shared org token, manifest registry on your S3-compatible bucket. The default shape for a startup engineering team.

Control plane: self-hosted Planet on your VPS
Data plane: self-hosted Comets in your LAN / VPC

Cloud

Stable v0.2.0

developer.soyaos.ai

Stable v0.2.0: sign in with GitHub, create an API key, call soya:starter through the OpenAI-compatible API, and inspect 24-hour trace metadata. Currently free, single-region, best-effort, and without an SLA.

Control plane: SoyaOS-hosted personal tenant and API keys
Data plane: platform-reviewed hosted text Agent

Hybrid

planned

soyaos start --edition hybrid

The orchestration is hosted, the workload stays inside your perimeter. Useful when your data can't leave but you don't want to babysit a control plane.

Control plane: soyaos.ai-managed Planet
Data plane: your Comets in your VPC / on-prem

Enterprise Cloud

planned

soyaos start --edition ent-cloud

Dedicated regions, SSO/SAML, SOC 2 controls, signed audit log export. Same kernel as Solo — only the operations are different.

Control plane: dedicated Planet (region pinned)
Data plane: dedicated Comet pool

Enterprise Private

planned

soyaos start --edition ent-private

Ship the same binary into a sealed network. Update via signed offline bundles. Tested against banks and labs where outbound is denied by default.

Control plane: customer-operated Planet
Data plane: customer-operated Comets

Not sure which fits?

Choose Cloud for no installation or operations; choose Solo to run fully on your own computer. Other shapes remain planned.

Cloud quickstart