Follow a portfolio
Filter events by country, region, sector and asset type in the workspace, and save the views your team returns to.
Political violence data for insurers, with the sources attached.
See which insured assets sit near a reported event, how severe it looks and how sure anyone is. Every record links to the reports behind it.
The problem
A headline is not an exposure.
Underwriters and claims teams read about the same incident in many places, and still have to work out what happened, where, and whether it touches their book.
Tellurial turns news, official feeds and public channels into one structured record per event. Reports about the same incident are grouped, placed as precisely as the evidence allows, and assessed once.
That gives political risk, political violence and specialty teams a shared starting point: a dated record they can search, check against its sources and return to when a file is reviewed months later.
What you get
Built for files that get reviewed.
Exposure
Events are linked to the ports, oil terminals, airports, power stations, chokepoints and canals within 40 km of them, so you can start from the asset rather than from the news.
asset_type: port | oil_terminal | airport | power_station | chokepoint | canal
Three separate answers
Severity, confidence and materiality are separate fields. A severe event backed by weak evidence stays visibly uncertain, and anything not assessed is left empty rather than guessed.
severity · confidence · materiality · null = not assessed
Evidence
Every event lists the source reports behind it and the kind of source each one is, so a reader can go back to what was actually published.
Location precision
Each event says how precisely it is placed, from an exact point to a whole region. Coordinates are never invented to make a map look better.
Revision history
Every change keeps who made it, when and why. Withdrawn and merged records stay visible, with date and reason, which helps when a claims file is reviewed later.
An example
One event, read by an underwriter.
The record gives the asset and the distance, then keeps severity and confidence apart. This example is illustrative.
How teams use it
Where the record fits in your day.
Get told when it changes
A daily briefing by region, and alerts when something changes in the places you follow.
Feed your own tools
Pull events and signals into exposure or reporting tools through the API, or export them from the workspace.
What it does not do
We say it before you ask.
No forecasts
We record and assess what was reported. We do not predict attacks, losses or claims.
No premium or pricing advice
The record supports your judgement. It is not an underwriting model or a risk score for a policy.
Distance is not damage
A link to an asset means the event was located within 40 km of it, not that the asset was hit.
Reports are not confirmed facts
A record describes what sources said. Confidence tells you how far to rely on it.
Public assets only
Asset links cover the six asset types above, not your own schedule of locations.