Request Access

See the ClimRisk Engine in Action.

Schedule a tailored walkthrough to see how we translate IPCC AR6 physical climate data into audit-ready financial intelligence for your portfolio.

Built for the frameworks you already answer to

IFRS S2TCFDCSRDSFDREU TaxonomyPCAFTNFDBasel III

LocationAmsterdam, Netherlands

For direct media or academic inquiries, please contact our research desk at shri@climrisk.io.

Before You Book a Call

What procurement usually asks first.

Where does the data live, and who hosts it?

The engine and your portfolio data run in a cloud environment we control; nothing is handed to a third-party AI vendor for inference — the resident agent needs no API key by default, and an optional language model runs entirely on your own machine via Ollama if you want more fluent written answers. For regulated deployments (banking, insurance) we scope hosting and data residency per engagement — raise it on the call and we'll work it into the proposal rather than force a one-size-fits-all answer here.

How long does implementation actually take?

A single-portfolio screening run (asset coordinates in, Capital-at-Risk out) is typically same-day — the live widget on the homepage is that exact pipeline, running on real data, not a sample file. A full embedded-due-diligence or white-label engagement, where the output feeds your own disclosure cycle, is usually 2–6 weeks depending on how much of your asset register needs geocoding first.

Is there an API, or is this only a web app?

Both. The web app ("Launch Platform") is the same engine every capability on the Platform page is built on, and it's also reachable as a direct API for teams integrating Capital-at-Risk output into their own risk systems at portfolio scale — see the Enterprise API engagement model on the Platform page.

How is this priced?

There's no published price list, because the three engagement models (Advisory Retainer, Embedded Due Diligence, White Label) scale very differently with portfolio size and how deeply the output needs to integrate with your existing workflow. Book a call and we'll scope it against your actual asset count rather than quote a number that doesn't fit your portfolio.

What happens if the model is wrong about one of my assets?

We'd rather you catch that than we hide it. Every methodology decision traces to a named, public data source (see /methodology), every validation test is published with its script so you can re-run it yourself (see /validation), and the engine reports its own confidence rather than a single number dressed up as certainty. If something still looks off on your own assets, that's exactly what the technical demo is for — we'll run it live, together, on your own coordinates.