Pay for the work
running at the same time.
Bring every person and every Agent your Organization needs. S0 prices shared concurrent work and included storage—not human seats or Agent count.
One Organization.
One shared capacity pool.
Every plan includes the same operating model. Plans differ by how much concurrent work and included storage the Organization wants available.
Concurrency is a pool.
Only root Sessions occupy it.
A foreground root Session or a task root Session occupies a slot. Work nested inside that root does not consume another one. Idle roots release capacity; when the pool is occupied, new roots wait visibly.
A foreground root Session is working now.
A task root Session shares the pool.
An idle root releases its slot.
New root work waits visibly.
Start with the peak.
See the honest base capacity.
Choose how many root Sessions need to run at once. The planner shows the smallest plan and additional-slot combination that covers that peak. Runtime and model usage stay separate.
Free includes two root Sessions and cannot add slots. Pro adds capacity at $20 per slot per month. Business adds capacity at $10 per slot per month.
4 root Sessions · 20 GB included storage.
Choose where the work runs.
Cloud Runtime first. BYO when you need it.
Cloud Runtime is the hosted path for always-on execution. BYO machine is available when your organization wants to provide the runtime boundary itself.
Always-on hosted compute.
Use S0-hosted runtime when you want one click, always-on execution for foreground and task root Sessions in your Organization pool.
Your machine. Your boundary.
Keep the machine and keys you already trust. S0 connects the operating model without charging for hosted compute.
2 vCPU · 4 GB RAM
4 vCPU · 8 GB RAM
8 vCPU · 16 GB RAM
Fuel first.
BYOK when you need your key.
Purchase Fuel directly in S0 to access leading global models through the platform at published provider prices, or bring a key your Organization already manages. Model usage remains separate from software capacity.
Global model access.
Recharge in S0 and access leading global models through the platform at published provider prices.
Your key. Your provider bill.
Connect a key your Organization supplies when you want provider access to remain on your side.
When the boundary gets stricter,
the commercial shape changes.
Enterprise is a contract boundary for identity, audit, hosting, service terms, and capacity—not a feature dump on a larger card.
Talk to sales →SSO / SCIM
Identity boundary.
Audit export
Reviewable history.
Dedicated hosting
Runtime isolation.
SLA / volume terms
Contract boundary.
Price the capacity.
Keep the rules visible.
Is a slot an Agent? +
No. One slot is one root Session running at a time. A foreground Session or a task Session can occupy a slot; work nested inside that root Session does not consume another slot. You can create as many Agents as the work requires.
Do people consume slots? +
No. Human members are unlimited. The Organization owns one capacity pool for root Sessions, not a pool per person or per Agent.
What happens when the pool is full? +
Foreground root Sessions take priority over task Sessions. Idle root Sessions release their slots; new root work can wait visibly when the pool is occupied.
Can we run S0 on our own machine? +
Yes. Cloud Runtime is the default hosted path when you want S0 to run the compute. BYO machine is available when your organization wants to provide the runtime boundary itself.
Are model costs included? +
Model usage is separate from software capacity. Purchase Fuel for access to leading global models through S0, or use BYOK when your organization supplies the key.
Are interfaces or Agents billed separately? +
No. People, Agents, projections, and interfaces are not pricing atoms. Pricing follows the Organization’s root-Session capacity.