Open LLMs/anrilombard

Open-Weight LLM · Private & Custom AI

mzansilm-125m

A lightweight, multilingual decoder-only LM trained on South African languages—designed for private deployment and fine-tuning in low-resource, localized NLP workflows.

MzansiLM is a 125M-parameter Llama-architecture model trained on MzansiText, covering all eleven official South African languages (Afrikaans, English, Ndebele, Sotho, Swati, Tswana, Tsonga, Venda, Xhosa, Zulu, Nothern Sotho). For ops teams building AI in geographically or linguistically specific markets, it's a permissively licensed, audit-friendly foundation that avoids vendor lock-in and keeps inference data in your infrastructure.

125M
Parameters
apache-2.0
License (OSI/permissive)
Unknown
Context
176.5k
Downloads

Model facts

Developeranrilombard
Parameters125M
Context windowUnknown
Licenseapache-2.0 — OSI/permissive
Tasktext-generation
GatedNo
Downloads176.5k
Likes25
Updated2026-05-19
Sourceanrilombard/mzansilm-125m

Private deployment

Run mzansilm-125m in your own environment

At 125M parameters and 2048-token context, the model runs on modest CPU or single-GPU setups (estimated 250–500 MB BFLOAT16, ~1 GB FP32). Deploy it on-premise or in a private cloud—no external API calls, no model telemetry, full data residency. Requires Transformers 4.x (validation issue noted in Transformers 5); standard PyTorch inference with safetensors format. Ops value: regulatory compliance, data sovereignty, and cost predictability at inference time.

Operational AI use cases

01

Multilingual customer support automation

Route and draft responses to support tickets written in any of the eleven South African languages. Fine-tune on historical ticket resolutions and knowledge bases; deploy the tuned model as a Retrieval-Augmented Generation (RAG) backbone to reduce ticket resolution time and scale support in underserved linguistic markets without external language APIs.

02

Internal documentation and knowledge mining

Index company wikis, policy docs, and procedure manuals in South African languages; use the model to power semantic search and auto-categorization of internal requests (HR, compliance, ops questions). Keeps sensitive internal knowledge private and avoids throughput bottlenecks of cloud APIs.

03

Operational workflow routing and summarization

Automatically classify and summarize operational logs, emails, and task descriptions in local languages. Route them to the right team (finance, logistics, legal) and extract action items. Useful for organizations with multilingual staff where language barriers slow down task assignment and escalation.

Custom AI

As a base for custom AI

Ideal as a fine-tuning base for domain-specific language tasks in South African languages—sentiment analysis on local social data, named entity recognition for regulatory compliance, or custom chatbot personalities. Its modest size makes it trainable on a single GPU with moderate datasets, lowering the barrier to building IP-protected, language-specific applications without relying on large closed models.

In the operating system

Where it fits

Sits at the **foundation layer** of an AI operating system: replace generic English-only LLMs with this when building knowledge retrieval, agent reasoning, or workflow automation for multilingual, geographically specific operations. Can feed into RAG pipelines, agent orchestrators, and fine-tuning workflows that drive internal task automation.

Data control & security

Self-hosting eliminates data transmission to third-party inference endpoints—conversation transcripts, customer interactions, and operational logs remain in your network. No model-serving SLA agreements or vendor dependencies. Architecture choice (private deployment) is the control lever; the model itself carries no built-in encryption, access controls, or compliance certifications—those are your responsibility via infrastructure (VPC, TLS, RBAC, audit logging).

Hardware footprint

**Estimate (unverified).** 125M parameters: ~250 MB (BFLOAT16), ~500 MB (FP32), ~125 MB (INT8 quantized). Inference on CPU (latency ~100–500 ms per 50-token generation) or single NVIDIA/AMD GPU (V100, RTX 4090, MI210) for <50 ms latency. No multi-GPU sharding required.

Integration

Load via Hugging Face `transformers` library (4.52.4+) and `safetensors`. Tokenizer is included; custom BPE with 65K vocab, NFD normalization. Use standard PyTorch or ONNX export for inference servers (vLLM, TensorRT, or custom wrappers). Integrate via REST/gRPC endpoints or embedded in Python microservices. Typical stack: async job queue (Celery, AWS Lambda) → inference → downstream task (CRM, ticketing, search index).

When it's not the right fit

  • English-only or non-South-African-language workflows—model is optimized and trained exclusively on eleven SA languages; use general-purpose open models (Llama 2/3, Mistral) for English or other regions.
  • Real-time, ultra-low-latency inference at scale (>100 req/s)—125M is efficient but requires batching or GPU clusters; consider quantized distillation or smaller alternatives for edge/mobile.
  • Instruction-following or chat applications out-of-the-box—this is a base (causal language model), not instruction-tuned; requires fine-tuning on your own instruction data to achieve chat behavior.
  • Shallow language coverage—if you need languages outside the eleven SA languages, this model will hallucinate or degrade; train a custom adapter or use a larger multilingual model.

Alternatives to consider

Llama 2 7B / Llama 3.2 1B

Larger, broader language coverage, instruction-tuned out-of-the-box, but no SA language specialization; requires more compute and introduces vendor/Meta ecosystem dependencies. Better for English-dominant ops.

Mistral 7B / Mixtral 8x7B

Permissive license (Apache 2.0), strong multilingual grounding, efficient, but not trained on SA languages; assumes English/European-language workflows. Smaller context (4K–32K vs. 2048).

African-NLP custom models (e.g., AfriVEC, Afro-XLMR)

Purpose-built for African languages and smaller in scale, but sparse ecosystem support, older training data, and less active maintenance. MzansiLM is more current and SA-specific.

FAQ

Can I run MzansiLM entirely on-premises without cloud dependencies?

Yes. Load the model from HuggingFace, store it locally, and run inference via PyTorch or ONNX on your hardware (CPU, GPU, or edge device). No API calls or external telemetry. All data stays in your environment—ideal for regulated industries (financial services, healthcare, government).

Is MzansiLM free for commercial use?

Yes. Licensed under Apache 2.0 (OSI-approved, permissive). You can use it commercially—in products, services, or internal ops—without payment or license fees. Cite the paper and retain the license notice in redistributed code. Review the paper (arXiv:2603.20732) for any research-use expectations from the authors.

How do I fine-tune MzansiLM for my company's internal tasks?

Standard Hugging Face fine-tuning: prepare labeled data (tickets, docs, logs) in SA languages, use the `transformers` Trainer API or PyTorch with the model as a base, and save weights as safetensors. Low-rank adapters (LoRA) work well for modest hardware. Store tuned weights in your infrastructure. No special licensing constraints.

Will MzansiLM work for languages outside South African languages?

No. The model is trained exclusively on Afrikaans, English, Ndebele, Sotho, Swati, Tswana, Tsonga, Venda, Xhosa, Zulu, and Northern Sotho. It will perform poorly on other languages. For multilingual ops in non-SA regions, use larger models (Llama 3.2, mT5) or retrain with your target languages.

Build Private, Multilingual AI Systems

MzansiLM is a foundation. LLM.co helps ops teams integrate it into private knowledge systems, RAG pipelines, and workflow automation—keeping your data, your model, your competitive edge. Let's design a deployment for your South African operations.