Skip to main navigation Skip to search Skip to main content

Structural dilemmas of PeaceTech: AI, power, and peacebuilding in the digital age

Research output: Contribution to journalArticlepeer-review

4 Downloads (Pure)

Abstract

PeaceTech, the use of AI and other digital technologies in peacebuilding, is often praised as a transformative approach to conflict prevention and dialogue. Yet the field remains conceptually vague and ethically fraught. Tools meant to empower communities can also enable surveillance when crowdsourced data exposes vulnerable groups. Innovation is often constrained by legacy institutions that collect data but lack the capacity to interpret or act on it. AI powered platforms may increase visibility, but early warning alerts frequently fail to produce effective responses. At the same time, corporate control over infrastructures such as cloud services and satellite internet raises concerns about the public good, while globally designed systems often clash with local realities and reinforce digital colonialism. Drawing on scholarship and practitioner insights, this article argues that these are structural rather than accidental problems. It calls for guardrails including service continuity, community data ownership, algorithmic accountability, and response protocols tied to funding, solidarity, and justice.
Original languageEnglish
JournalPeacebuilding
Early online date23 Mar 2026
DOIs
Publication statusE-pub ahead of print - 23 Mar 2026

UN SDGs

This output contributes to the following UN Sustainable Development Goals (SDGs)

  1. SDG 16 - Peace, Justice and Strong Institutions
    SDG 16 Peace, Justice and Strong Institutions

Keywords

  • PeaceTech
  • digital peacebuilding
  • techno-solutionism
  • algorithmic governance
  • ethical dilemmas

ASJC Scopus subject areas

  • Social Sciences(all)
  • Computer Science(all)

Fingerprint

Dive into the research topics of 'Structural dilemmas of PeaceTech: AI, power, and peacebuilding in the digital age'. Together they form a unique fingerprint.

Cite this