Best conflict data platforms for researchers
Which conflict data platform should a researcher use? ACLED for coded event data, World Monitor for current cross-domain context with a public, tiered source inventory and an API, Liveuamap for incident discovery in case work.
This guide is published by World Monitor. We compare public product documentation and our own documented capabilities. Recommendations are editorial judgments, not a hands-on benchmark. World Monitor’s capabilities were rechecked on October 16, 2026, and competitor sources on October 2, 2026. Confirm current access and contracts before buying.
TL;DR
For conflict researchers, the best data platform is the one whose event definitions you can defend in a methods section. Choose ACLED for research that depends on coded, consistently defined conflict events. Choose World Monitor when you need current cross-domain context to frame a question: conflict, protests, shipping, outages, hazards and markets on one free map, editorial tier and state-affiliation badges on news sources, and a REST API and SDKs for pulling context into your own pipeline. Choose Liveuamap to discover reported incidents for qualitative case work.
The picks at a glance
| Tool | Best fit | Access | Main limit |
|---|---|---|---|
| ACLED | Event-level conflict research | myACLED level controls granularity, timing and API access | Access level limits exports |
| World Monitor | Current context and question framing | Free core map; separate API plan; open source under AGPL-3.0 | Aggregates published reports; not a coded, versioned event dataset |
| Liveuamap | Incident discovery for case work | Confirm current access and package | Not a standardized event count |
What matters for conflict researchers
A research tool must preserve the meaning of an observation. Event definitions, revisions, access and time coverage affect every comparison. A visually dense map can look comprehensive while giving you no defensible denominator for a statistical claim. Know where each observation came from and what kind of source published it.
Different jobs need different tools
A reproducible dataset
Check definitions, geography, date range and the data version. Save the records and method that support your result.
Current context
Monitoring helps you formulate a question and notice what else is happening around a conflict. It cannot substitute for the dataset and sampling rules used to answer that question.
Permitted access
Check granularity, lag, export rights and API entitlement. A free visualization does not necessarily permit the research or redistribution you plan.
1. ACLED
Best for event-level conflict research.
ACLED is the choice for research needing coded, consistently defined conflict-event data and its methodology. Its myACLED framework distinguishes access levels. Confirm that your institution receives the records and timing the project requires. The existence of a public map is not evidence of unrestricted exports.
2. World Monitor
Best for current context and question framing.
World Monitor puts conflict, protests, shipping, aviation, infrastructure outages, hazards, cyber and markets on one map, free with no account at worldmonitor.app/dashboard. Each outlet has an editorial tier from 1 (wire or official) to 4 (aggregator or blog), a propaganda-risk band and, where it applies, a state-affiliation label: the News panel shows them as badges, the free get_sources MCP tool returns them for any outlet, and the explains the scheme. That makes it easier to describe the media environment around a case.
For pipelines, there is a REST API on a separate API plan, Python, Go and Ruby SDKs, and an npm CLI. The code is open source under AGPL-3.0 on GitHub, so you can read how a layer is built. World Monitor aggregates published reports and does not verify events on the ground. Not every upstream source has completed a terms review, so check reuse terms before republishing data. Move statistical analysis to the original source dataset.
Track global conflicts in real time.
3. Liveuamap
Best for incident discovery for case work.
Liveuamap is a focused, editor-curated conflict news map with regional maps. Use it to identify incidents worth examining in a case study. Preserve the original report and establish your inclusion rules. We would not choose it over ACLED for a study that depends on standardized event counts.
Official Liveuamap documentation.
Pick World Monitor when
- You are framing a question, not testing one. Conflict, protests, outages, shipping and markets on one free map show what else changed around a case.
- Your study concerns the media environment. News items carry tier, propaganda-risk and state-affiliation badges where they apply, and the free
get_sourcesMCP tool returns any outlet’s labels. - You want context in a notebook. The REST API, Python, Go and Ruby SDKs and CLI pull the same data into your pipeline.
- You need to inspect the method. The code is open source under AGPL-3.0.
Our pick
For the research dataset, pick ACLED. For current cross-domain context and a labelled source inventory, pick World Monitor alongside it. For qualitative incident reconstruction, pick Liveuamap to discover reports. Make the evidence standard explicit before gathering material.
What to do today
- Write the question, unit of analysis, event categories, countries and time range. Check whether the source can support each one.
- Obtain a sample through the access level you will actually use. Record its version and reproduce one calculation before committing to the full project.
- Test whether a definition change or reporting delay changes your conclusion. State those limits in the method rather than treating missing reports as zero events.
Frequently Asked Questions
Is Open myACLED enough for event-level research?
Not necessarily. ACLED’s access table distinguishes aggregated and event data, publication timing and API access. Verify your assigned level and the current terms before designing the analysis.
Can I cite World Monitor as a conflict-event dataset?
Cite the original reports instead. World Monitor aggregates published reports and links to them; it is not a coded, versioned event dataset and does not verify events. Its public source inventory and tiers can support a description of where reports came from.
How were these recommendations made?
We compared documented capabilities with the tasks in this guide. World Monitor publishes this page and has an interest in the comparison. We did not run a common vendor benchmark or test service response times.
For ACLED, check the myACLED access table alongside its methodology.