Cortex Enterprise

Your whole portfolio on one map.Before, during and after the event.

Cortex Enterprise brings together on one screen what is spread across spreadsheets, a GIS and the loss adjuster's visit today: where the portfolio accumulates, what falls inside each storm and which claim to look at first.

CortexAgro portfolio · hail of Feb 18, 2026

Before

Highest concentration

18/02/2026Event reconstruction

Version 1 · not corrected

Policies in portfolio

0

Hectares in portfolio

0

Sum exposed

USD 0.0M

Claims the day after

Consistent0
Inconclusive0
No consistent activity0

Signed report · SHA-256

  1. 01BeforeWhere the portfolio accumulates
  2. 02DuringWhat falls inside the storm
  3. 03AfterWhich claim to look at first
Real Sentinel-2 image from Mar 1, 2026, after the Feb 18, 2026 hailDemo portfolio

One module per team

Each team comes in through its own door.All of them look at the same map.

Claims, underwriting, reinsurance and parametric work on the same event footprint and the same history of each place. Every number comes with its source and date.

A 100.8-hectare field in Armstrong in true color: green on Jan 30, 2026 and straw-colored on Mar 1, with the greenness-drop grid marked in red.

Jan 30, 2026: before the hail

99.1 ha with a net drop in greenness

Nine Sentinel-2 crops of the same field in Pergamino, from 2017/18 to 2025/26, with the likely crop and the confidence for each season.

One image per season

Likely crop and confidence for each year

Hail signal hexagons for the Nov 11, 2018 storm between Villa María and Casilda, with the policies of a demo portfolio as dots.

Hail signal by hexagon

Policies in force that day

A field in General Belgrano: the 5 by 5 km surroundings with open water in blue and the 50 by 50 km basin in Sentinel-1 radar.

Open water in two or more passes

New water by radar, even through clouds

  1. Jan 30, 2026: before the hail
  2. 99.1 ha with a net drop in greenness
  1. One image per season
  2. Likely crop and confidence for each year
  1. Hail signal by hexagon
  2. Policies in force that day
  1. Open water in two or more passes
  2. New water by radar, even through clouds
Hail loss adjustment · Armstrong, Feb 18, 2026 · 100.8 ha field
Field risk · Pergamino · one image per season
Scenario: the Nov 11, 2018 storm over a demo portfolio
Excess water · General Belgrano · August to November 2025

Integration

It starts with the location.Without sharing the portfolio.

Your company decides each step, with its own agreements and rules. And each one returns more than it asks for.

  1. E0 One area You give usNothing from the portfolio You getEach event's footprint as a layer for your GIS
  2. E1 Locations You give usJust points or fields You getWhat fell inside each storm
  3. E2 Sums and terms You give usSum insured and start date You getHectares and exposed sum insured by band, and recent additions
  4. E3 Closed claims You give usPlace and date of already settled claims You getThe blind comparison against the loss adjuster
  5. E4 The whole company You give usSSO, roles and the API in your systems You getCortex Enterprise in every team

SSO and six roles

Each person signs in with the company account and sees what their role allows.

Two API keys

One production and one sandbox: test with recorded data and go live by switching the key.

Encryption

In transit and at rest, with a log of who saw and did what.

Isolated per organization

Every query takes the organization from the session, never from the browser.

Signed report · offline verification

SHA-256················

The report is the one that was signed

Anyone can recompute the PDF's fingerprint and compare it with the signed one, without connecting to Ucotron.

The pilot we recommend

Compare blind against your loss adjuster.On claims you've already closed.

It doesn't ask for the portfolio, doesn't touch operations and is measured in weeks. If Ucotron's assessment matches what the loss adjuster found, the adjuster can go to the field to validate instead of searching.

  1. 01You pick already-closed claimsOne hail season, from an area you know well.
  2. 02You send us only place and dateWithout the loss adjuster's result and without the rest of the portfolio.
  3. 03Ucotron assesses each oneConsistent, inconclusive, not consistent or not measurable, with the evidence.
  4. 04We open the envelopeWe measure where we agree, where we don't and how many days the first evidence took.
No.UcotronLoss adjusterResult
1 Consistent Damaged Match
2 Consistent Damaged Match
3 Not consistent No damage Match
4 Inconclusive Damaged Goes to a person
5 Not measurable Damaged Can't be seen isn't didn't happen
6 Consistent No damage Difference: reviewed

Illustrative: this is how the comparison reads. It is not a result.

How to sign up

On an annual contract.For the whole company.

  • The whole portfolio on one map, no limit on places
  • All four modules: claims, underwriting, reinsurance and parametric
  • Reports signed with SHA-256, verifiable offline
  • SSO, six roles and an audit log
  • Production and sandbox API, and MCP for your agents
  • The blind pilot, supported by the team

Traction

Linkups with leading agro insurers.

This page's pain points come from those conversations: hail eating into results, the reinsurance number that grows with claims, and the loss adjuster who goes out to search instead of validate.

Start with a pilot that doesn't ask for the portfolio.And measure it against your own loss adjuster.

Start for free

Leave your details and we'll open your account. We'll reach out to set up your first place.

No card, no commitment.