Deployment shapes

Six editions. One kernel.

The edition isn't a different product — it's where the Planet (control), Moons (UI / edge) and Comets (workers) run, and who runs them. The CLI flag is all that changes.

$soyaos start --edition solo     # or cluster | cloud | hybrid | ...

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

Where things run

Control plane vs. data plane, per edition.

Same binary, six split points. The boundary between "you operate it" and "we operate it" is the only knob.

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

planned

soyaos start --edition cloud

We run the Planet and the Comets. You hold an API key. Drop in your own BYOK model key at any time and stop paying us for inference — only for compute.

Control plane: soyaos.ai-managed Planet
Data plane: soyaos.ai-managed Comets

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?

Start with solo. Graduate to cluster when your laptop fan gets loud. Everything else is the same kernel.

Download v0.1