Skip to content
WARSTRIKESby Tellurial
For teamsSign in
WARSTRIKES

WarStrikes for teams

Conflict events, traced to source.

Structured records of conflict events for risk, insurance, shipping and research teams. Each event links to its reports, states how precise it is, and is available in a workspace and through an API.

Request a pilotSee a sample record ↓

Sample records on this page are synthetic

How a record is builtIllustrative
  1. 01

    Observation

    What one source reported

  2. 02

    Event

    One occurrence, linked to all its reports

  3. 03

    Signal

    Our assessment — severity, confidence, materiality

Teams receive Events, Signals or both, depending on their access.

01 / The data model

One event.
Many reports.
One record.

News outlets and public channels often report the same event several times, with different details. WarStrikes keeps every report, links the ones that describe the same occurrence into one event, and adds a separate assessment when it matters.

01 / Provenance

Source-linked records

Every event lists the reports behind it, and what kind of source each one is.

02 / Transparency

Uncertainty is visible

If a place or time is uncertain, the record says so. Nothing is filled in by guessing.

03 / Integration

Built for data teams

The same records through a versioned API, with access granted per layer.

02 / Coverage

What the data covers.

Geography
73 countriesDedicated coverage of eight conflict regions, from Russia–Ukraine to the Red Sea and Sudan, plus reports placed anywhere else in the world.
Freshness
Every 5–10 minPublic channels every 5 minutes, news every 10. Events update as new reports arrive.
History
48,000+ reportsEvery report since collection began is kept. Each event has a dated, public revision history.
Sources
66 sources28 news outlets and wire services, plus 38 public Telegram, X and Reddit channels — each labelled by type.

Figures are read from the live archive and source list when this page loads.

03 / A closer look

A record,
not a feed.

Every Event carries its evidence, its stated precision and its revision history. The record below is synthetic, shown in the exact structure customers receive in the workspace and through the API.

Event · 0b6e…c41 · revision 3Synthetic record — not a live incident
DroneActive

Drone strike reported on port infrastructure, Odesa

When
26 Oct 2026 · 05:50–06:40 UTC · 50-min window
Where
Odesa, Ukraine · city-level
Entities
Port of Odesa (infrastructure)
Signal
Black Sea ports · severity high · confidence moderate

Evidence · 4 source reports

  1. Air defence active over the coast

    X · OSINT & social

  2. Video appears to show fire at a port facility

    Telegram · OSINT & social

  3. Explosions heard near the port, officials say

    Established media · Unmarked

  4. Regional administration confirms drone attack

    Established media · Marked verified

Same record via API

GET /api/v1/events/0b6e…c41

{
  "event_type": "drone",
  "status": "active",
  "granularity": "city",
  "event_start_at": "2026-10-26T05:50:00Z",
  "event_end_at": "2026-10-26T06:40:00Z",
  "active_evidence_…_ids": [ 4 ]
}

Requires events:read · Policy intelligence-publication-v1

04 / Who it is for

Built for teams
that must be right.

Insurance & risk

Screen insured assets near reported events and review exposure by region, asset type and impact.

region · asset_type · impact

Maritime & logistics

Track port, corridor and route disruption as structured events, each with its stated precision.

domain · region · precision

Data & research

Pull canonical Events and Signals into your own models through a versioned API.

GET /api/v1/events · /signals

05 / Pilot

How a pilot works.

  1. 01

    Scope

    We agree the regions, sectors and questions your team needs answered.

  2. 02

    Access

    Workspace seats and API keys for the layers you need — Events, Signals or both.

  3. 03

    Evaluate

    A time-boxed evaluation against your own workflows, with a weekly review.

  4. 04

    Decide

    Contract, data terms and service levels. Pricing on request.

Request a pilotRead the API referenceMethodology

06 / Trust

Built to be checked.

Hosted in the EU

The servers and databases behind the workspace and the API run in the European Union.

Public methodology

How sources are labelled and how Events are resolved is published.

Corrections

Every public report has a correction form. A person reviews each one and the decision is recorded.

Access by layer

Events and Signals are separate entitlements. Keys are shown once and stored hashed.

07 / Questions

Questions teams ask.

Is every event confirmed?
No — and no single label claims it is. Each Event shows its sources, their types and any editorial marks, so your team can weigh the evidence itself.
How do you decide two reports are the same event?
Our software proposes possible matches. A person reviews and approves each one, and every decision is recorded.
Do you predict attacks?
No. WarStrikes records and assesses what has been reported. It does not forecast targets.
How precise are locations and times?
As precise as the evidence allows — and always stated: city, district or region; a time window rather than a false minute.
Can we integrate it?
Yes. A versioned REST API with signed cursors, per-layer entitlements and an equivalent request behind every view in the workspace.
What does a pilot cost?
Pilots are scoped per team. Pricing on request.

WarStrikes / by Tellurial

Evaluate WarStrikes with your team.

Tell us the regions and questions that matter to your team. We’ll scope a pilot around them.

Request a pilot