Pricing & adoption
Research Agent is the featured workflow. Teaching Studio and Business Collaboration are browser-local previews. Product access, deployment, and fees require separate confirmation.
Adoption pathway
Each path begins with workflow scope, authority, evidence, deployment constraints, and a measurable advance or hold gate.
Illustrative profile · Individual users
A proposed scope for researchers, educators, graduate researchers, and professionals working independently across academic life.
Access and fees require separate confirmation.
View access notesIllustrative profile · Teams and institutions
A proposed scope for labs, faculties, graduate programs, research offices, universities, and university-industry teams.
Access and fees require separate confirmation.
View access notesIllustrative profile · Controlled environments
A proposed scope for organizations that require private infrastructure, local data boundaries, or offline operation.
Access and fees require separate confirmation.
View access notesOperating-scope comparison
| Capability | Individual | Organization | Private / Offline |
|---|---|---|---|
| Product access | Confirmed separately | Confirmed separately | Confirmed separately |
| Scale | One user | Teams and institutions | Controlled organizations |
| Workspace | Personal | Shared and administered | Private and administered |
| Review and governance | User controlled | Role-based | Role and policy based |
| Deployment | ScienzaOS cloud | Cloud or isolated | Private, on-premise, or offline |
| Fees | Not published | Not published | Not published |
These are illustrative scope profiles, not current service offers or entitlements. Product access, deployment, integrations, and fees require separate confirmation 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 workflow. After validation, confirm product access, deployment, and fees.
View access notes
