Pricing & adoption
ScienzaOS is scoped around workflow complexity, portfolio context, deployment and security profile, integration boundary, validation requirements, and operating model, not rigid researcher-seat pricing.
Adoption pathway
Each path begins with workflow scope, authority, evidence, deployment constraints, and a measurable advance or hold gate.
Focused validation
Validate one high-value decision workflow with real institutional context, baseline measures, authority mapping, and explicit acceptance criteria.
Scoped to institutional workflow and deployment context
Scope a pilotMost common path
Operationalize governed workflow packs and the Decision Room across a research portfolio or institutional business unit.
Scoped to institutional workflow and deployment context
Discuss adoptionMulti-portfolio
Coordinate several portfolios with advanced governance, integration boundaries, deployment requirements, and dedicated operating controls.
Scoped to institutional workflow and deployment context
Discuss enterpriseControlled boundary
Evaluate a private, regional, VPC, or on-premises boundary when sovereignty and outbound restrictions require additional validation.
Scoped to institutional workflow and deployment context
Review requirementsOperating-scope comparison
| Capability | Design Partner Pilot | Institutional Platform | Enterprise | Sovereign / Private |
|---|---|---|---|---|
| Workflow scope | One focused workflow | Multiple packs | Multi-portfolio | Institution-defined |
| Decision Room | Pilot slice | Included | Included | Included |
| Integration scope | Required sources | Standard catalog | Expanded within scope | Customer environment |
| Policy configuration | Core | Expanded | Comprehensive | Institution-aligned |
| Deployment profile | Shared evaluation | Institutional profile | Dedicated options | Private boundary |
| Operating support | Pilot support | Priority | Dedicated planning | Dedicated boundary |
| Controlled intelligence | Standard | Advanced | Advanced | Approved boundary |
| Exports | Standard | Configurable | Configurable | Configurable / restricted |
Commercial terms, deployment commitments, connector availability, and service objectives are confirmed only after requirements and validation scope are agreed.
Trusted and procured by design
Least privilege, isolation, secrets, observability, backup, and recovery shape the operating model.
External effects pass through policy, approval, deterministic execution, and receipts.
Canonical domain contracts and exports remain portable across validated deployment profiles.
Core workflow state and manual progression remain outside model-provider availability.
FAQ
Begin with a real, high-value decision moment that has identifiable authority, evidence inputs, baseline measures, and a clear validation boundary.
The architecture supports evaluating pooled, isolated, regional, and private profiles. The exact profile depends on requirements and validation.
Business workflow state remains outside the model runtime. Intelligence failure may reduce recommendation speed but should not erase state or prevent manual progression.
Integration scope is selected from institutional source systems and validated as part of the implementation boundary. No connector is implied before that review.
Significant decisions retain human authority. Approval binds to the exact decision or intended action payload; material changes require renewed approval.
The adoption path begins with a focused workflow, baseline, evaluation method, authority map, and explicit advance, hold, or pivot decision.
Start with one governed workflow, validate the operating and economic case, then expand deliberately.
Start a conversation
