For
Platforms embedding insurance
You already know how to run a mobility fleet, a booking flow, a rental platform or a freelance marketplace. What you do not want to build is a compliance-grade audit ledger just to switch on a cover toggle at checkout. RiskRouter is the part you would otherwise have to build yourself: server-side pricing and a tamper-evident record, behind one HTTP call.
Where you sit relative to us
Your checkout → RiskRouter API → price + cryptographic record → your customer
We never touch your customer, never handle a claim, never hold the carrier relationship, and never see a name, an email or an account id. You keep all of that. We price a configuration and, if you hold a key, seal the record.
The questions an engineer actually asks
Answered directly, not deferred to a call.
What data do we send?
A vertical key and a set of component toggles — { "active_vertical":
"mobility", "selected_components": { "commuter_roadside": true } }. Nothing
identifying your user.
What does RiskRouter calculate?
The total premium, server-side, from the published rating matrix. A price your frontend computed is never trusted as the answer.
What gets permanently recorded?
Nothing, unless you send an API key. A quote with no key is priced and returned; nothing is written. Recording is a separate, attributed decision.
Where is it hosted?
Frankfurt, Germany, inside the EU. Nothing about your checkout traffic leaves that region.
Can we verify it ourselves?
Export your entries any time and run two offline scripts against them — no call back to us. See the tamper-detection demo.
What if RiskRouter disappears?
An export you already hold still verifies with us gone. Nothing about your evidence depends on our uptime a year from now.
How much engineering work is required?
No SDK, no session, no account to provision before you can price. A working integration is usually one afternoon — see two languages worked in the integration guide.
How do we test it?
Price against the live demo with no signup at all, or take a free sandbox key that writes to a row separate from production.
Pick the vertical closest to what you are building
Each is a real, worked rate card — a mandatory base layer plus optional components, not a category label.
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
Building something else? The question is whether it decomposes into a mandatory base layer and optional modules, not whether it matches one of these four labels — tell us what it is.
Why not build it yourself
You would still need the ledger
Compliant micro-insurance is not the pricing math — it is proving the pricing math was not changed afterwards. That is the harder half, and it is what we actually built.
You would own an audit posture, not a feature
Append-only triggers, a signed attestation, an offline verifier — each is small alone and easy to get subtly wrong together. We carry that so your team does not have to.
Leaving stays trivial, on purpose
No SDK, nothing to license. If we are wrong for you in six months, you keep every record and the means to verify it, and you leave without asking anyone's permission.