Mistral Public Sector Singapore

DSO National Laboratories

Security and Compliance

DSO needed sovereign, multilingual large language models it could train and deploy fully on premise for defense workloads, but it lacked at-scale operational experience with the mixture-of-experts architecture it considered essential for next-generation systems.

Reported impact

Business outcome

The collaboration accelerated DSO's model-development timeline, delivered leading-in-class Southeast Asian language benchmark performance for operational use cases, and strengthened DSO's internal ability to build future edge reasoning models independently.

  • Productivity Improvement
  • Risk Reduction

Solution

DSO used Mistral's Forge to accelerate creation of a sovereign multilingual large language model for defense operations. The program started from DSO's existing pretraining work but focused on mastering mixture-of-experts architecture, which the lab viewed as critical for next-generation LLMs. Working in a shared development environment with Mistral, the team trained a specialized MoE model on language data that included content sourced through AI Singapore, then prepared it for entirely on-prem deployment so DSO could avoid external-vendor dependency and supply-chain risk. The engagement was not only about shipping a model: Forge gave DSO repeatable training workflows while close collaboration transferred practical know-how about what works at scale. That left DSO with both a benchmark-competitive multilingual model and stronger in-house capability for later edge reasoning systems.

Data flow

Language content sourced via AI Singapore feeds a shared development environment, Forge orchestrates training for the multilingual MoE model, and the resulting model is prepared for entirely on-prem deployment and later edge reasoning work on autonomous systems.

Solution architecture

1 components · 1 layer
  1. Orchestration
    • Forge Provides the end-to-end training system DSO used to co-develop and train its custom multilingual MoE model.

Architecture clues

  • A second phase is targeting small reasoning models that can run efficiently at the edge on autonomous systems.
  • DSO wanted models that could be deployed entirely on premise for sovereign defense use.
  • Knowledge transfer from Mistral was a core part of the project, not just model delivery.

Evidence from the source

"DSO needed to train its own multilingual large language models from scratch that could be deployed entirely on premise."
"Partnering with Mistral gave us direct access to expertise in MoE architecture, helping us accelerate our model development timeline."
"The custom MoE model delivered leading performance in its class on Southeast Asian language benchmarks"
"The two teams co-developed a MoE model using Mistral's model development stack, later integrated into Forge."
"Training data included language content sourced via AI Singapore (AISG)."
Transparency Evidence & methodology 71/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value71/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Mistral

    DSO National Laboratories customer story

    First-party
    https://mistral.ai/customers/dso/
    Source type
    Vendor-published customer story
    Published
    Apr 24, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Apr 24, 2026 · Mistral · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.