SELF-SERVE PATH
Operator
Best when you want to start alone on one primary machine.
- 1 operator
- 1 primary machine
- Guided desktop entry
- Support through first governed work
COMMERCIAL SURFACE
Choose how you want to operate agents with control.
Operator for individual use. Team for coordinated operation. Enterprise for controlled deployment. The commercial path changes account behavior, machine scope, desktop release and support.
PLAN DIFFERENCES
Plan differences are operational, not decorative.
Every plan changes what can be purchased, how account access is released and how desktop continuation is governed.
TEAM PATH
Team
Best when operators, machines and account access need to be coordinated.
- Up to 5 operators
- Coordinated account access
- Initial setup support
- Distribution by contracted scope
CONTROLLED PATH
Enterprise
Best when adoption depends on policy, support and controlled distribution.
- Planned deployment
- Controlled distribution
- Organization account rules
- Security and operations coordination
WHAT HAPPENS NEXT
Each plan prepares a different kind of entry into Foundry.
Operator
Self-serve purchase, automatic account release where allowed, guided desktop entry and bounded support through first governed work.
Team
Organization-aware continuation. Account access and desktop release may depend on reviewed access and deployment policy.
Enterprise
Controlled path. Commercial agreement, account semantics and deployment remain policy-driven rather than anonymous self-serve.
BEFORE YOU BUY
Common questions before purchase.
Does payment mean the desktop is ready?
No. Payment confirms the purchase. The account path still has to resolve authorized download and desktop-local validation.
Is Foundry Account the main place to start?
No. Self-serve discovery begins in pricing. Foundry Account is reserved for recovery, reissue and reviewed access.
Can every plan see every release lane?
No. Desktop release depends on plan semantics, deployment policy, access truth and machine or organization constraints.
Does Operator include unlimited machine resets?
No. Operator is intentionally bounded to one primary machine and one controlled recovery path before review is required.