Platform

From the world’s noise to a record you can act on.

Tellurial Core reads every source once, turns reports into events, and keeps every decision attributable. Products and customers draw on the same record.

Tellurial Core reads every source once, turns reports into events, and keeps every decision attributable.

  1. 01

    Collect

    90+ sources

    every 5–10 min

    90+ sources · every 5–10 min

  2. 02

    Read

    place, time, category

    precision stated

    place, time, category

  3. 03

    Resolve

    one record per event

    evidence linked

    one record per event

  4. 04

    Assess

    severity · confidence

    materiality

    severity · confidence · materiality

  5. 05

    Deliver

    workspace · API

    alerts · exports

    workspace · API · alerts

Tellurial Core

Four capabilities. Every product uses all of them.

Event resolution

Many reports, one event. A model proposes how reports group; each change passes the same checks as an editor’s decision.

Many reports, one event. Each change passes the same checks as an editor’s decision.

POST resolution plan → validated → applied · actor recorded

actor recorded

Place & precision

Every event is placed as precisely as the evidence allows — and says so. Coordinates are never invented.

Placed as precisely as the evidence allows — and says so.

granularity: point | city | district | region | unknown

granularity · coordinates

Signals

What events mean, as three separate answers: how severe, how sure, how relevant to your sector.

Severity, confidence and materiality: three separate answers.

severity · confidence · materiality · null = not assessed

null = not assessed

Audit trail

Every change keeps who made it, when and why. Withdrawn records stay visible.

Who changed what, when and why. Withdrawn records stay visible.

revision history · status: retracted | superseded

revision history

The data model

One model of the world, shared by every product.

Reports, events, places, assets and assessments are linked objects with stable IDs — so a port, a strike and the reports about it stay connected across products and over time.

  • Source reportevidence ofEvent
  • SignalassessesEvent
  • Eventlocated atPlace
  • Eventwithin 40 km ofAsset

Assets are linked to an event when it is located within 40 km of them. About location precision.

Delivery

Wherever your team works.

Workspace

Explore events and signals, save views, export, and manage your team — no code.

Explore, save views, export, manage your team.

Alerts & briefings

A daily briefing by region, and alerts when something changes in the places you follow.

Daily briefing by region; alerts on change.

$ curl "https://warstrikes.com/api/v1/events?since=2026-10-23T00:00:00Z&until=2026-10-30T00:00:00Z" \
    -H "Authorization: Bearer wsk_live_…"

{ "id": "…", "status": "active", "country_code": "UA",
    "granularity": "city", "primary_location": "Odesa",
  "active_evidence_observation_public_ids": ["…"], … }

API · REST · JSON

GET /api/v1/events
  ?since=2026-10-23T00:00:00Z&until=…
Authorization: Bearer wsk_live_…

See the platform on your own regions.