Compare

Duck Creekvs Callvu

Duck Creek is a P&C core delivered as SaaS, with policy, rating, billing, claims, a policyholder portal, bureau content and an agentic AI platform. Callvu is the Completion and Compliance Layer around the core: it runs servicing and claims requests from policyholders, agents and third parties end to end to policy admin and claims, deterministically, with compliance enforced at every step. Callvu integrates with Duck Creek and goes live in weeks alongside it.

At a glance

Runtime compliance enforcement

Duck CreekPartial.
CallvuYes.

Front-to-back-office handoff

Duck CreekPolicyholder Portal (US homeowner and personal auto) for payments, claims and policy changes, connected to policy, billing and claims.
CallvuYes, end to end: prefill from the core, classify the work, chase and verify documents from policyholders, agents and third parties on a clock, route decisions to the Decision Desk and write back to policy admin and claims.

The fair version

What Duck Creek is built for.Sourced from their own pages.

Vista Equity Partners completed its acquisition of Duck Creek in 2023 [1]. Duck Creek provides P&C policy administration with business-led configuration [2], claims workflows from first notice of loss through settlement with rules-based assignment and vendor orchestration [3], a Policyholder Portal for payments, claims and policy changes, connected to policy, billing and claims [4], and bureau content from ISO, AAIS, NCCI and other bureaus with automated circular updates [5]. It is delivered as SaaS through Duck Creek OnDemand [6]. Its agentic AI platform combines large language models with insurance business rules and adds built-in guardrails on every model call, an immutable decision ledger and human oversight, with an Agentic Underwriting Workbench, an Agentic Policy Assistant and an Agentic Product Configurator [8], and Agentic FNOL captures, validates, triages and routes personal auto claims and sends the claim data into Duck Creek Claims [9]. HDFC ERGO's policy, rating and billing core was delivered in nine months [7].

When to choose which

Two different jobs.Pick the one you need.

When to choose Duck Creek

Choose Duck Creek when the need is the P&C system of record itself: policy, rating, billing and claims [2][3], with bureau content [5], a policyholder portal [4] and AI agents on its platform [8], delivered as SaaS [6].

When to choose Callvu

Choose Callvu when claims and policy servicing requests arrive from policyholders, agents and third parties and must reach the core complete. Callvu orchestrates that work, routes it by work type, skill and due date, applies rules and policies and manages every decision, with five moves: it prefills from the core, classifies each request the moment it lands, chases and verifies documents on a clock, routes decisions to the Decision Desk, and writes changes to policy admin and claims by API.

Guardrails are not runtime enforcement. Duck Creek's FNOL agents capture, validate and route claims with decision traceability and human checkpoints [9], under platform guardrails on every model call and alongside business rules [8]. Guardrails limit and record what an AI does while it does the work. Even with guardrails, an AI that runs a step can write wrong data to the system of record, take a path that is not in the workflow, or act compliantly most of the time rather than every time. Callvu does not let AI run the process. A deterministic orchestrator executes every step of a defined workflow and enforces every control before the step runs; AI only starts a process or evaluates it. Every run is recorded in a Decision Trace and an Audit Trace.

Choose Callvu, too, when time and services cost matter. HDFC ERGO's policy, rating and billing core took nine months [7]. Callvu's license includes white-glove design, implementation, maintenance and optimization for as long as it runs, with no separate services project, and Callvu goes live in a few weeks: Phoenix Insurance integrated all core systems in 4 weeks and had 100+ processes live in under 3 months.

Side by side

The verifiable facts.Nothing else.

Every cell about Duck Creek is sourced from its own public pages. Runtime enforcement and the handoff lead the table because they are where the two differ most.

CapabilityCallvuDuck Creek
Primary roleCompletion and Compliance Layer between every front door and the system of recordP&C core as SaaS: policy, rating, billing and claims [2]
Runtime compliance enforcementYes. A deterministic orchestrator runs every step; AI never runs the process. Every regulation and company policy is enforced on every step while the work runs, whether a person or an AI started it; a step that fails a control does not run. A Decision Trace and an Audit Trace for every runPartial. Duck Creek documents business rules working alongside AI models, compliance controls, guardrails on every model call and an immutable decision ledger, and claims workflows with embedded controls and full auditability. Not documented: a policy layer that enforces every regulation and company policy on every step of work that spans policyholders, agents and third parties outside the core. Where its agents act, such as Agentic FNOL, the AI performs the step [8]
Front-to-back-office handoffYes, end to end: prefill from the core, classify the work, chase and verify documents from policyholders, agents and third parties on a clock, route decisions to the Decision Desk and write back to policy admin and claimsPolicyholder Portal (US homeowner and personal auto) for payments, claims and policy changes, connected to policy, billing and claims; Agentic FNOL sends structured claim data into Duck Creek Claims [4]
Orchestration, routing, rules and decisioningYes: workflow orchestration across the core and outside parties, routing by work type, skill and due date, rules and policies, and human decisions in the Decision DeskYes: claims workflows from FNOL to settlement with rules-based assignment and vendor orchestration [3]
AI guardrails vs deterministic executionDeterministic execution, not guardrails: AI never runs the process. A deterministic orchestrator executes every step and enforces every control before it runs, so nothing unchecked reaches the system of record and no step outside the workflow can happenAgentic FNOL captures, validates, triages and routes personal auto claims, with confidence scoring, decision traceability, audit trails and human checkpoints for complex losses [9]
Regulatory contentMost regulations already loaded as policies and enforced on every step of servicing and claims processesBureau content from ISO, AAIS, NCCI and others, with automated circular updates [5]
Deployment and professional servicesWhite-glove design, implementation, maintenance and optimization included in the license, for as long as it runs; no separate services project. Live in a few weeks: Phoenix Insurance integrated all core systems in 4 weeks and had 100+ processes live in under 3 monthsSaaS through Duck Creek OnDemand; HDFC ERGO's policy, rating and billing core was delivered in nine months (2024) [7]

Using both together

Keep what works.Add the layer that finishes it.

Callvu integrates with Duck Creek. Duck Creek stays the policy, billing and claims system of record. Callvu runs servicing and claims requests from every channel, chases documents from policyholders, agents and third parties, routes decisions and writes changes back to the core by API, alongside the core and any migration plan. Callvu can also run the whole process on its own.

Proof

Live in production.At regulated enterprises.

FAQ

The questions buyers ask.Answered plainly.

Does Duck Creek enforce compliance at runtime?
Partly. Duck Creek configures claims workflows and rules-based assignment in its core, with embedded controls and full auditability, and its agentic AI platform combines business rules with AI and adds compliance controls, built-in guardrails on every model call, a decision ledger and human oversight. Those are rules inside the core and governance of AI that still performs the steps. Duck Creek does not document a policy layer that enforces every regulation and company policy on every step of servicing and claims work that spans policyholders and third parties. Callvu does, and AI never runs the process: a deterministic orchestrator does.
Does Callvu replace Duck Creek?
No. Duck Creek stays the policy, billing and claims system of record. Callvu integrates with Duck Creek, runs servicing and claims requests from every channel and writes changes to the core by API.
Are Duck Creek's agentic FNOL agents the same as runtime enforcement?
No. Duck Creek runs its AI alongside business rules and keeps human checkpoints for complex losses, but agents that capture, validate and route claims are AI performing the steps, with guardrails around them. Even with guardrails, an AI that runs a step can write wrong data to the system of record or take a path that is not in the workflow. Callvu keeps AI out of execution: a deterministic orchestrator runs every step and enforces every control first.
How can an insurer improve servicing without waiting for a core upgrade?
Callvu runs policy servicing, claims intake and document collection on top of the current core and goes live in a few weeks. During a core migration it keeps running on the current core.
How fast can Callvu go live alongside Duck Creek?
A few weeks, with white-glove implementation included in the license. Phoenix Insurance integrated all core systems in 4 weeks and had 100+ processes live in under 3 months.

See it on your process.

Bring one regulated process. We will show you the handoff and runtime enforcement on it.