Risk objects and parties
Model what is insured and who is on the policy—vehicles, drivers, policyholders and additional roles—each with its own attributes and cardinality rules.
THE PLATFORMInsurance concepts,
Insurance concepts,
not database tables
Thirteen configuration areas cover everything a product needs—from what is insured to how it is priced, sold, changed and renewed. Product people work in the language of insurance; nobody writes code to ship a product.
THE PRODUCT MODEL
A structure deep enough for real insurance, readable enough for business users.
The complexity lives in the model, not in the interface. That is what keeps a product changeable a year after launch instead of frozen behind whoever built it.
Coverages, benefits and plans
Build coverages and benefits once, then compose them into plans. Cover limits, sums insured and deductibles sit where an underwriter expects them.
Product rules
Conditional logic over the product's own fields: default a value, lock it, make it mandatory, or hide it—without touching code.
RUNNING THE BUSINESS
The product is configuration. The policies are the business.
Everything below runs on the same platform and the same product definition—there is no second system to reconcile against.
Full policy lifecycle
Quote, issue, endorse, renew, cancel and reinstate. Mid-term changes settle pro-rata, with each coverage line rounded to the cent as the system of record.
Customers and parties
Policyholders, insured parties and distribution partners as first-class records, each carrying a change history of who edited what.
Commissions, taxes and fees
Partner commission rules, taxes and charges configured on the product, then calculated onto every policy transaction.
Versioned configuration
Product versions carry their own status history, so a change is a reviewable new version rather than an edit nobody can trace.
External quoting API
Key-authenticated endpoints for products, quote schemas, lookups and pricing—published as an OpenAPI spec your partners can build against.
Environment promotion
Export a configured product as one portable bundle and re-create it elsewhere, keyed by code rather than environment-specific ids.
GOVERNANCE
Changes you can trace, promote and reverse.
Configure in test. Promote to production.
A configured product exports as a single portable bundle and re-creates itself in another environment. The bundle is keyed by code, not by ids that differ between environments, and a round-trip test in CI proves export → import → re-export stays identical. Rehearse the launch where it is safe, then promote exactly what you signed off.
SEE IT HANDS ON
Book a demo