P&C rating engine: which vendor for your situation (April 2026)
A decision guide for US P&C carriers choosing a rating engine. Rating is the pricing math layer: it takes the risk attributes underwriting has structured and returns a premium. The decision turns on whether the carrier needs a standalone engine, a PAS-embedded module, or a programmable pricing platform operated by actuaries directly.
Tier-1 on Guidewire: Guidewire's native rating, unless specialty complexity demands more.
Tier-2 on Duck Creek: Duck Creek's rating.
Complex specialty actuaries: hyperexponential.
Mid-market carriers wanting a standalone programmable engine: Earnix.
Digital-native MGA: Akur8.
Which to pick
| Scenario | Recommended |
|---|---|
| Tier-1 carrier on Guidewire, personal lines | Guidewire native rating |
| Tier-2 carrier on Duck Creek | Duck Creek native rating |
| Complex specialty / commercial with actuary-driven pricing | hyperexponential (hx Renew) |
| Mid-market personal lines needing ML-pricing | Akur8 |
| Global carrier needing standalone programmable engine | Earnix |
| Insurity shop | Insurity rating (stay in-family) |
Ranking criteria
- Programmability by actuaries (code-native vs GUI-configured)
- LOB complexity (personal lines vs commercial vs specialty)
- Existing PAS stack (Guidewire, Duck Creek, Insurity, etc.)
- Real-time rating throughput (API latency)
- ML-pricing support (GLM + gradient-boosted models)
Default for complex specialty or commercial actuaries who want to write pricing logic in code.
Situation fit. London-market specialty lines. US specialty / E&S carriers where pricing sophistication is the primary constraint. Actuaries who want to write models in code rather than configure a GUI.
Why hx Renew. Programmable pricing surface; actuaries write models in Python-adjacent syntax and deploy them to production with regression tests. hx has deep Lloyd's and UK commercial references with US expansion since 2023.
When hx is the wrong pick. Pure personal lines where PAS-native rating is simpler. Carriers without actuaries who can write code.
Default for mid-market personal lines carriers adopting ML-pricing without rebuilding the actuarial function.
Situation fit. Mid-market personal lines (auto, home). Carriers exploring GBM / interpretable-ML rating. Regional carriers that need sophisticated pricing without a London-market actuarial team.
Why Akur8. GUI-driven ML-rating; transparency layer designed for state DOI defensibility. Strong mid-market personal lines adoption across US and Europe.
When Akur8 is the wrong pick. Specialty / commercial where hx's programmability wins. Personal lines carriers already deep in PAS-native rating.
Default for global mid-to-tier-1 carriers needing a standalone programmable engine that sits above the PAS.
Situation fit. Multi-region carriers that need one rating platform across countries. Carriers where the PAS-native engine is inadequate for pricing sophistication but hx is overkill. Companies that also use Earnix for dynamic pricing in life / banking lines.
Why Earnix. Broadest cross-industry footprint. Strong analyst coverage (Gartner, Celent).
Buyer reality
What a carrier procurement team should expect on scope, budget, and integration cost.
Situation-scoped diligence.
- Specialty actuary buyer: ask hyperexponential for deploy-time metrics on complex pricing models (days from idea to production). Ask for regression-test coverage requirements pre-production.
- Mid-market personal lines buyer: ask Akur8 for named state DOI acceptances of Akur8-produced rate filings. Transparency claims must be state-provable.
- Global buyer: ask Earnix for named multi-region deployments within the last 3 years. Cross-border rating consolidation is claimed often and measured rarely.
- PAS-native buyer: before replacing the native rating engine, verify that the native engine actually cannot meet the requirement. Many "native is inadequate" complaints resolve with partner-integration rather than vendor replacement.
Deployment-window risk.
- Rating engine replacement typically crosses one CEO-of-actuarial tenure cycle.
- Migration from PAS-native to standalone is harder than migration between standalone vendors.
- State DOI rate filings take 30-90 days per filing; experiment plans need to account for regulatory latency.
Also considered
- Guidewire PolicyCenter
Native Guidewire rating. Right answer for most Guidewire shops on personal lines.
- duck-creek-policy
Native Duck Creek rating. Right answer for Duck Creek shops.
- Insurity
Insurity rating for specialty / programme business.
Sources
- hyperexponential — hyperexponential
- Akur8 — Akur8
- Earnix — Earnix
- Guidewire PolicyCenter — Guidewire
- Duck Creek Policy — Duck Creek