Platform
Workspace, product data, revisions, review flows, imports, 3D project state, rule data, and application access.
Workspace & members
Product library
Review & history
APIs / MCP surface
Pricing
Pricing should follow the product workload, not hide it.
ConfigAI's commercial model is being shaped around three separable costs: the product workspace, agent/model execution, and optional onboarding or integration work. No public numeric plans are published yet, so this page documents the model instead of inventing prices.
Agent execution
Research, product setup, modeling, rule assistance, and other agent work can use different models and runtimes.
Model/runtime choice
Usage visibility
Lower-cost workers
Escalation for hard tasks
Onboarding & integrations
Optional migration, pCon / OFML mapping, customer-specific adapters, and implementation work are separate from normal usage.
Catalog migration
Supplier adapters
Custom integrations
3D pipeline setup
Deployment
Keep deployment choice separate from product semantics.
The product domain should behave the same whether ConfigAI runs as a managed service or in a customer-controlled environment. Deployment may change infrastructure cost and operational responsibility, not the product definition.
Managed deployment
ConfigAI-operated platform and CPQ services with customer workspaces, managed updates, and hosted agent orchestration.
Customer-controlled deployment
Commercial designA future deployment option for customers who need product data, runtime workers, or integrations inside their own infrastructure.
Commercial discovery
Price the system after we know the catalog and workflow.
The useful inputs are catalog size, source systems, expected agent workload, 3D requirements, rule complexity, deployment preference, and migration/integration scope.