For product and platform teams
Use Clariva where your product or service would otherwise call an AI provider directly.
- One workflow.
- API or SDK integration path.
- Policy template fit.
- Approved and rejected examples.
PricingEvaluation-first scoping
Start with a standard path. Expand when the workflow requires it.
Start with one workflow and one starter profile. Pricing is scoped after the evaluation path is understood, not before.
Evaluation Framing
Pricing follows the request boundary.
Clariva does not currently publish fixed public tiers. Commercial scope depends on deployment model, workflow count, integration surfaces, policy depth, evidence requirements, customization needs, and support expectations.
A standard evaluation starts with one bounded workflow to confirm fit before broader pilot, production, or enterprise scope is discussed.
Evaluation Paths
Standard starting points, not fixed software tiers.
The right starting point depends on how the AI-bound request enters the system and how much review the workflow requires.
For CRM and support teams
Evaluate Clariva around tickets, customer conversations, CRM notes, summaries, or routing workflows.
- One supported source path.
- Data-class review.
- Provider route planning.
- Audit evidence sample.
For stricter review needs
Add deeper controls when the workflow requires security review, custom policy, SSO, deployment-model review, or expanded audit scope.
- Custom control review.
- Provider-route requirements.
- Security and procurement support.
- Production readiness planning.
Pricing Drivers
What affects commercial scope.
Clariva starts with a standard evaluation path. Additional scope is based on the actual workflow, not a generic implementation package.
| Driver | Why it matters |
|---|---|
| Integration path | Direct API and SDK paths are usually simpler than CRM, support, or custom enterprise integrations. |
| Policy depth | More data classes, departments, exception rules, or rejection requirements add review work. |
| Provider routing | Single-provider paths are simpler than multi-provider routing, fallbacks, or customer-specific provider rules. |
| Audit and security review | Procurement, compliance, certification, retention, export, and evidence needs can expand scope. |
Expectation Setting
What is standard and what may need review.
Standard evaluation
One workflow, one starter profile, a policy-template fit, sample request behavior, and reviewable evidence.
Enterprise expansion
Custom policy design, SSO, deployment review, provider credential handling, private environment requirements, or expanded audit/export requirements.
Pricing Review
Get the right scope by starting with the right profile.
The demo intake helps identify the standard path first, then separates any custom enterprise requirements.
Next: review the evaluation path →