Who this is built for
RiskRouter prices whatever risk vertical you configure into it. The validation build ships with four worked examples — not products, not cover, and not for sale to anyone — so a reader can see exactly what the engine does before pointing it at rates of their own. Each one below is a real base layer and real optional components, priced by the same server that would price yours.
mobility
E-bike, scooter, car-share and on-demand fleet exposure.
base 2.00 / month5 components
digital_nomad
Cross-border remote work, client liability and device exposure.
base 1.50 / month5 components
urban_rental
Tenant liability, deposit liquidity and connected-home risk.
base 3.50 / month5 components
micro_travel
Short-haul multi-modal transit and seasonal sports exposure.
base 2.50 / month5 components
Or start from who you are, not what you price
The four verticals above are worked examples. These two are about your role instead.
Distributors, brokers and MGAs →
Replace a spreadsheet-based Article 20 evidence trail with server-side pricing and an append-only ledger.
Platforms embedding insurance →
Add compliant micro-insurance at checkout without building the audit layer yourself.
Security, compliance and audit review →
Don’t trust RiskRouter. Export the evidence and verify it yourself, offline.
The same engine underneath every one of them
Nothing below changes from vertical to vertical. The difference between the four pages is the rate card, not the architecture.
Priced on the server, always
A client sends a vertical and a set of toggles, never a price. The server looks up the mandatory base layer and every selected component from its own matrix and computes the total. A submitted price is not read.
Sealed if it is attributed
A quote with no key is priced and not recorded. A quote from a resolvable distributor is priced and appended to a chain where changing one entry breaks every entry after it.
Yours to configure
These four verticals and twenty components are worked examples. Your own base layers, your own components and your own prices replace them; the engine does not change shape.
Not sure which one fits
Every vertical here is the same shape: one mandatory foundation layer priced into every quote, and four optional modules a customer switches on individually. If what you are pricing does not look like any of the four, say what it is — the question is whether it decomposes into a base layer and optional modules, not whether it matches one of these four labels.