For one bounded workflow to assess fit, evidence shape, and deployment assumptions.
- One workflow.
- One integration path.
- One deployment target.
- One or two provider routes.
- Defined evaluation period and usage cap.
PricingStructured enterprise model
Start with one request boundary. Expand when the workflow requires it.
Clariva pricing follows a structured enterprise model: a fixed-scope evaluation package, an annual platform subscription for approved workflows, included protected usage, metered overage, and enterprise deployment or support add-ons when needed.
Evaluation Framing
Pricing follows the request boundary.
Clariva does not publish public dollar amounts at this stage, but the pricing structure is defined. Final scope depends on protected workflows, request volume, integration paths, provider-route complexity, policy depth, evidence and export requirements, deployment obligations, and support expectations.
A standard evaluation starts with one bounded workflow to confirm fit before broader pilot, recurring platform, or enterprise scope is discussed.
Commercial starting points
Evaluation package, platform subscription, and enterprise scope.
The right starting point depends on how the AI-bound request enters the system, how much control the workflow requires, and how the approved deployment is scoped.
For approved workflows moving from evaluation into recurring use.
- Annual platform subscription.
- Included protected usage.
- Policy and provider-route configuration.
- Reviewable evidence receipts.
- Usage bands for additional protected requests.
For stricter deployment, security, procurement, or multi-workflow requirements.
- Customer-controlled data-plane gateway review.
- Optional managed control-plane scope.
- SSO/SCIM and security review.
- SIEM/GRC export and retention needs.
- Expanded support and deployment obligations.
Usage Model
How usage is measured.
Clariva should be evaluated around protected workflow activity rather than only raw text volume. Usage can be scoped by protected requests, provider routes, connector or tool actions, and evidence receipts.
| Meter | What it means |
|---|---|
| Protected request | A request evaluated by Clariva before AI provider, model, tool, or connector execution. |
| Protected text volume | Text inspected, transformed, routed, or recorded for policy and evidence purposes. |
| Provider route | An approved model, provider, or internal AI destination controlled by policy. |
| Connector or tool action | A governed external action or enterprise connector path. |
| Evidence receipt | A reviewable record of the policy, routing, transformation, rejection, or execution decision. |
Pricing Drivers
What affects commercial scope.
Clariva starts with a standard evaluation path. Additional scope is based on the actual workflow, deployment obligations, and review requirements.
| Driver | Why it matters |
|---|---|
| Workflow count | More protected workflows add policy, evidence, and review scope. |
| Request volume | Recurring use is scoped around protected request activity and usage bands. |
| Integration path | Direct API paths differ from CRM, support, knowledge, messaging, or custom enterprise systems. |
| Provider-route complexity | Multiple approved routes, fallbacks, or provider-specific rules add review work. |
| Policy depth | More data classes, exception rules, and rejection requirements expand configuration. |
| Evidence and export requirements | Review receipts, audit exports, and SIEM/GRC needs affect implementation scope. |
| Deployment model | Data-plane placement, managed-control-plane scope, networking, and retention are confirmed during evaluation. |
| Security/procurement support | Security review, legal review, and procurement requirements can add commercial and implementation scope. |
| Support/SLA expectations | Support coverage and service-level terms are documented in written agreements. |
Pricing Review
Get the right scope by starting with the right workflow.
The evaluation request helps identify the first bounded path, then separates recurring platform and enterprise requirements.
Next: review the evaluation path →