Use this boundary for decisions that need explicit human review.
One company · one operating context
Build the OS your AI will operate inside.
Choose the people and modules first. Then verify the owner account and continue through the launch path the current configuration supports.
Configure your companyYou configure the autonomy boundary
Use this boundary for approved, repeatable work with evidence and audit history.
The mode can differ by workflow. Registration does not make launch-target or planned capabilities generally available.
AvailableRegister, verify, review the server estimate, then checkout.
ManagedSave the same company and configuration, then complete launch qualification.
Launch target / plannedVisible for planning only until its maintained availability changes.
Registration
Configure once. Continue through the right launch path.
Self-service and managed launch share this configuration. Prices shown here are a planning preview; the signup service validates the current catalog and estimate before checkout or launch planning.
- 01Company and modules
- 02Email and owner
- 03Checkout or managed launch