Service · pipelines · onboarding from EUR 10,000
Your trigger pipeline, built inside your team or run by your calculation agent.
The machinery behind every calculation on this site, built for your perils and your countries. You choose where it runs and who owns it.
Option A · handed over
I build it in your stack, your team owns it.
Code in your repository, tests, documentation and a runbook. Pipeline support and independent verification can follow, from EUR 8,000 a year: I maintain it and check its results against the contract.
Option B · calculation agent
I run it on my server and issue the event report.
Scheduled pulls, checks, index and the event report the payout follows. From EUR 12,000 a year, available about six weeks after signature and set up per contract.
What gets built
Single-job modules with checks between every step.
Each module does one job and checks its inputs before it runs. Known dataset defects are caught where they enter, not after a payout.
- 01
Data in
Sources named in the contract (NOAA, ERA5, IMERG, Sentinel). Pulled on schedule, with the fallback source agreed in advance.
- 02
Checks
Every input checked for coverage, units, gaps and known dataset defects. Every file hashed.
- 03
Index
The index exactly as the policy wording defines it. The same code runs the backtest and the live calculation.
- 04
Trigger
Tested against the payout ladder, cell by cell or district by district.
- 05
Payout
A payout report for each cell: value, tier, amount and the data used.
- 06
Audit trail
Every figure traced to input hashes and code version. A rerun gives the same answer.
Where this comes from
Two years of production pipelines at a parametric insurtech.
At Raincoat I owned the satellite and reanalysis acquisition layer (CHIRPS, ERA5-Land, IMERG, Copernicus CDS, WEkEO), shipped the Water Balance peril to production on Kubernetes, and built the Heat Stress pipeline.
CHIRPS v2 production ends after December 2026; new rainfall pipelines use CHIRPS v3.