Rating engine
A rating engine on a local server is a single point of failure that nobody can patch on a Sunday.
See ratingCarrier API availability
Rate change versioning
Forms management
Audit trail
The operational difference is larger than the technical one.
A locally hosted rating engine goes down when the server does, and the people who can fix it are usually not the people who need it working.
Rate and form changes become a deployment project rather than a configuration change, which means agencies delay them and run on outdated rates longer than they should.
In the cloud, rate changes are versioned and reversible, the audit trail is automatic, and a bad change can be rolled back without restoring a backup.
Yes, where the carrier exposes an API. Where they do not, we support structured submission and manual rate entry.
As versioned configuration changes with an audit trail, reversible without a rollback of the whole system.
No. It handles rating and forms. The AMS keeps the accounting and the customer record.
Personal and commercial lines rating in one engine.
Direct connections to carrier APIs and rating services.
Hosted, patched and backed up without your involvement.
Every rate and form change tracked with a full audit trail.
Tell us which carriers and lines you rate and we will show you the integration.
