You own the weights, every stage checkpoint, the training and evaluation code and a 23.8B-token data sample, all under Apache-2.0, so you can run and change the whole pipeline from any stage. You do not own a deployable safety case: safety results are the publisher's own, no guard model exists and agent actions are untested. Ownership moves to substantial if an independent evaluation lifts safety to 3 or more.
1
Use and modify freelyCan you run, modify and adapt it with no gate and no field-of-use trap?
StrongApache-2.0 by card declaration, ungated, with every stage checkpoint, training and RL code and a data sample, so you can run, fine-tune and commercialise it. The licence text is absent from the weights repositories (ev-license, ev-branches, ev-code).
How this scores (AOI sub-dimensions)
Openness4/5how much is released - weights, data, code, licence - and how freelyWeights, checkpoints from the CPT, Cooldown, FTPO and SFT stages for every size, training and RL code, evaluation code and a 23.8B-token data sample are public under Apache-2.0 (ev-report-release, ev-branches, ev-code, ev-data-sample).
Legal3/5how permissive and clean the licence is for real commercial useApache-2.0 allows commercial use without a field-of-use clause, but the grant for the weights is declared in card metadata and the report only, with no LICENSE file in the weights repositories (ev-license).
2
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
StrongWeights, stage checkpoints, code, evaluation suite, a data sample and a detailed report with named sources are public. The full corpus, partner-supplied books and generator-model outputs are not shared (ev-report-release, ev-report-data, ev-data-sample).
How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelThe weights sit in the verified inception42 organisation as safetensors with LFS sha256 values, a completed hub scan with no flagged files, and a documented lineage from K2 Horizon (ev-hub, ev-report-lineage).
Governance3/5how accountable and well-documented the publisher isMBZUAI, Inception42 and Cerebras are accountable institutions, and the report names its authors and contributors (ev-report-release).
3
ReliabilityIs it reliable and good enough for the job?
WeakSafety scores 2: every result is the publisher's own, there is no guard model, and no test covers agent actions. Operational scores 3 (ev-report-safety, ev-card-32b, ev-hub).
How this scores (AOI sub-dimensions)
Operational3/5how practical it is to run, serve and maintain in productionThe cards give validated vLLM, SGLang and Transformers recipes, parsers for reasoning and tool calls, tested GPU layouts and a 512K context for five of the six sizes (ev-card-32b, ev-hub).
Safety2/5whether misuse risks are evaluated and guardrails are providedThe models are safety tuned and the report publishes results on four benchmarks in two languages (ev-report-safety).
4
Doesn't extract your dataDoes running it keep your knowledge and data yours?
StrongSelf-hosted Apache-2.0 weights with no telemetry or claw-back in the licence. Read the two custom Python files that run under trust_remote_code (ev-license, ev-hub).
How this scores
Not a scored AOI dimension. For a self-hosted model, data-control is a structural property of running the weights yourself, strong by default unless the model phones home or the licence claws back rights. For a hosted API this factor is the retention + train-on-inputs + residency read, scored from the binding terms.
Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.
DocumentWhat it grounds
Model cardread2026-11-19
The 32B card declares license apache-2.0 in its front matter and has no License section.
Model cardread2026-11-19
The 0.9B, 3.7B, 7B, MoVA-36B-A4B and 375B-A23B cards repeat the 32B licence declaration, intended-use text and limitations.
Licenceread2026-11-19
Apache-2.0 is declared in the front matter of all six weights cards and in section 7.1 of the technical report.
Technical_reportread2026-11-19
The report says each Jais 3 model starts from the final post-trained K2 Horizon checkpoint of the same size, keeps its architecture and tokenizer, and is adapted by continual pretraining, SFT, FTPO and RLVR.
Technical_reportread2026-11-19
The report lists released weights, stage checkpoints, training and RL code, a training-data sample, run configurations, W&B logs, audited benchmarks and evaluation code (Table 41).
Technical_reportread2026-11-19
The report names each source with token counts: ArabicTxT360 web text (28.4B), literature collections (9.65B), translated reasoning (30.9B), parallel dialects (26.9B), Arabizi (25.1B) and 11.9B tokens of partner-supplied Arabic books with no named source.
Technical_reportread2026-11-19
The report says GLM-5, Jais 2, Qwen3.8-27B, Qwen3.6-27B, gemma-4-31B-it and MiniMax-M3 generated or judged parts of the training data.
Technical_reportread2026-11-19
Section 6.5 reports publisher-run results on AraSafe (1,254 harmful prompts, above 92% refusal for every size), Arabic Regional Safety, HarmBench and XSTest, scored with gemma-4-26B-A4B-it.
Technical_reportread2026-11-19
The report says Jais 3 leads or matches open models of its size on Arabic benchmarks.
Technical_reportread2026-11-19
Training covers Gulf, Egyptian, Levantine and Darija Arabizi, country knowledge for 22 states, and translation for seven dialects.
Documentationread2026-11-19
All six weights repositories are ungated, hold safetensors only with LFS sha256 values, and report a completed hub scan with no flagged files.
Documentationread2026-11-19
Each weights repository has branches CPT, Cooldown, FTPO and SFT besides main.
Documentationread2026-11-19
The IFM organisation hosts FP8, MLX and GGUF builds of the Jais-3 models, each tagged Apache-2.0.
Documentationread2026-11-19
IFM/Jais-3-Data is an ungated 23.8B-token sample, about 10% of CPT and SFT tokens, in four Arabic subsets licensed ODC-BY or CC BY 4.0.
Documentationread2026-11-19
The xllm, RL360 and gen-eval-arabic repositories are public with Apache-2.0 LICENSE files.
Documentationread2026-11-19
The JaisVoice README dates the Jais 3 release to 2026-10-15.
Model cardread2026-11-19
The K2-Horizon-32B card declares Apache-2.0, says "Fully open" and links code and data.
Technical_reportread2026-11-19
The K2-Horizon abstract describes six fully open models, about 10T synthetic pre-training tokens and a release that follows the LLM360 definition of open source (publisher claims).
Licenceread2026-11-19
The MiniMax Community License grants use for non-commercial purposes and sets conditions on commercial use of the software and its derivative works.
Model cardread2026-11-19
The four Jais-3 Uno adapter repositories carry no licence tag and no licence statement.
Documentationunverified2026-11-19
The ifm.ai blog and tech-report pages return HTTP 403 (Cloudflare challenge), so their text is unavailable.