Buy the whole stack, or one component.
An enterprise can subscribe to the whole stack or to individual components. This page states what is charged, what is paid to someone else, and what is decided during scoping. Where a term is undefined, it says so.
01
The whole stack, or one component
An enterprise can subscribe to the whole stack or to individual components. A first purchase of one component is a supported way to buy.
Defined02
Platform pricing is per seat
The platform is charged per seat. Component-level packaging is set against the components in your scope.
Defined · figures agreed in the engagement03
Model usage is paid by you
Underlying model usage is paid separately by the customer to the model provider, under that provider’s terms.
Defined04
Managed execution credits
Managed-agent execution credits and consumption terms are still being defined. Commercial terms depend on the selected scope.
Undefined · stated as undefinedOne team. One repository. One workflow.
01
Choose a component
Start with the layer that addresses your immediate blocker.
02
Agree the boundaries
Deployment mode, permitted models and workload classes, written down before work starts.
03
Run against your own tasks
One team, one repository, one engineering workflow, with agreed acceptance criteria.
04
Add the next layer
Extend the scope when the first component has proved itself.
No price list is published. Commercial terms depend on the selected scope.