Navigated to Humanity Centered Data | UN Refugee & IDP Tracker
    All AI articles
    Infrastructure

    Open-Source AI Models for Humanitarian Work: A 2026 Buyer's Guide

    By the Humanity Centered Data Editorial Team
    June 19, 202611 min read

    Why open weights matter for humanitarian deployments

    For a humanitarian team, the decision between a closed API and an open-weight model is rarely about performance and usually about three other things: data residency, sanctions compliance, and offline operation. Closed APIs send data to a vendor's infrastructure and depend on the vendor's terms remaining stable. Open-weight models can be run inside a country office, on a field laptop, or behind a firewall. For organisations working in sanctioned jurisdictions or with protection-sensitive data, this is not a preference, it is a requirement.

    The 2026 landscape at a glance

    Open weights now span every major capability class. Text generation: Llama 3 and 3.1 from Meta, Mistral and Mixtral, Qwen 2.5 from Alibaba, Gemma from Google. Translation: NLLB-200, SeamlessM4T. Speech recognition: Whisper from OpenAI (open-weight). Vision: SAM and SAM 2, DINOv2. Embeddings: BGE, E5. All are downloadable from Hugging Face under licences that permit operational use, though licences vary and should be read.

    Recommendations by task

    • Document summarisation and Q&A: Llama 3.1 8B or Mistral Small for laptop-class deployment; Llama 3.1 70B or Mixtral 8x22B when a server is available. Pair with a retrieval layer using BGE embeddings.
    • Translation: NLLB-200 for breadth (200 languages), SeamlessM4T when speech is involved. Always check FLORES-200 scores for your target language.
    • Transcription of interviews and radio: Whisper large-v3 for accuracy, distil-whisper for speed.
    • Satellite and image analysis: SAM 2 for segmentation, DINOv2 features for downstream classifiers, YOLO variants for object detection.
    • On-device chat for field staff: Llama 3.2 1B or 3B; Phi-3 mini; Gemma 2B. All run on a recent laptop CPU.

    The hardware reality check

    An 8B parameter model in 4-bit quantisation runs on a laptop with 8 GB of RAM. A 70B model needs a server with a 48 GB GPU or two 24 GB GPUs. For most country offices, the practical envelope is 7-13B parameters on a workstation or small server, which is sufficient for translation, summarisation, and RAG over a curated knowledge base. Cloud-based open-weight hosting via Together or Fireworks is an option when local hardware is not, with the same data-residency caveats as any cloud service.

    Licensing and compliance

    Read the licence. Llama community licence has acceptable-use restrictions; Mistral models vary by version; Gemma has its own terms. For humanitarian deployments the practical questions are: can we use it for our purpose, can we fine-tune on our data, can we operate it in sanctioned jurisdictions, and what are the attribution requirements? The Open Source Initiative AI definition work is the operative reference on what counts as genuinely open source.

    A short procurement checklist

    • Does the licence permit operational humanitarian use, including in sanctioned contexts where you operate?
    • Does the model meet quality thresholds on your actual tasks and languages, not generic benchmarks?
    • Can you run it on hardware you can deploy and maintain in the field?
    • Do you have a fine-tuning and evaluation pipeline, or a partner who does?
    • Have you documented the data governance for any data the model touches?

    Further reading and primary sources

    • Hugging Face: https://huggingface.co/
    • Meta Llama: https://llama.meta.com/
    • Mistral: https://mistral.ai/
    • NLLB: https://ai.meta.com/research/no-language-left-behind/
    • Whisper: https://github.com/openai/whisper
    • Segment Anything: https://segment-anything.com/
    • OSI AI definition: https://opensource.org/ai
    Infrastructure

    How We Use AI to Synthesize UNHCR, OCHA, and ACLED Data — Without Losing the Human Layer

    A transparent walkthrough of how we use retrieval-augmented AI to synthesize UNHCR, OCHA, and ACLED data while keeping a human in every loop that matters.

    8 min read
    Infrastructure

    Biometric AI in Refugee Registration: UNHCR BIMS, IrisGuard, and the Privacy Debate

    How biometric AI is used in refugee registration in 2026, the systems involved, and the unresolved governance debates.

    11 min read
    Infrastructure

    AI's Carbon Footprint and Humanitarian Computing: The Sustainability Trade-Off

    What the latest evidence says about AI's energy, water, and carbon footprint, and what it means for humanitarian organisations.

    11 min read
    Infrastructure

    Federated Learning for Refugee Data: A Privacy-Preserving Path Forward

    How federated learning offers a privacy-preserving path for humanitarian AI, and what is actually deployed in 2026.

    11 min read
    Impact

    How AI Is Being Used to Predict Refugee Crises Before They Happen (2026)

    Machine learning models are now feeding into UNHCR, IOM, and World Bank early warning systems. A clear look at what AI can and cannot predict about forced displacement in 2026.

    9 min read
    Impact

    AI vs Traditional Methods: How Humanitarian Organizations Are Counting Displaced People in 2026

    Registration desks, household surveys, and satellite based machine learning estimates are now being combined to count displaced populations. A practical comparison of what each method gets right and wrong in 2026.

    8 min read
    Advertisement
    Advertisement