Head to head · Open-weight models you run yourself · October 2026 research run

OTel-2.0-LLM-31B-IT vs Swift 1.5 Qwen3.8-27B

Swift 1.5 Qwen3.8-27B scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 1 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on risk and documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

OTel-2.0-LLM-31B-IT C

Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware

Ahead on

  • Risk, 55 against 50
  • Documentation and upkeep, 74 against 43

Watch for

BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked

Swift 1.5 Qwen3.8-27B C

Best for Agents on a 24 to 32 GB GPU or Mac that want Qwen3.8-27B's skills with shorter thinking, for teams under US$1M revenue or research.

Ahead on

  • Reach, 80 against 50

Watch for

Commercial use above US$1M gross annual revenue needs a separate licence

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep OTel-2.0-LLM-31B-IT +31

OTel-2.0-LLM-31B-IT 74

Model card 14, Intended use, a long limitations section, the architecture and training method, the parameters (31B) and the language (English) are on the card. Training data 15, the card names the sources (3GPP, ETSI, ITU, GSMA, CAMARA, O-RAN and TM Forum material provided by GSMA), the overall sizes (15 billion raw tokens, over 1 trillion processed, about 440 billion used), the mix of example types and the processing tool, and lists what was left out. Last change 20, the last commit, on 1 November 2026, updated the card's links, resources, citation and contacts, nine days before this check. Responsiveness 20, Of the 3 discussions that aren't pull requests (7 August to 28 October 2026), 2 have a reply from the repository's owner, which is most. Version policy 0, the weights were replaced in place: uploads on 27 July, 3 August and 1 September 2026 under one name, with a standing notice on the card that they may change and that users should pin a revision, and no dated note of what changed. File health 5, the card describes 15 shards of about 62.6 GB while the repository still holds an earlier 14-shard set beside them, 126.8 GB in all. 14 + 15 + 20 + 20 + 0 + 5 = 74.

Swift 1.5 Qwen3.8-27B 43

Model card 8 of 20, intended use, parameters and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI's own ONNX builds of the model took a new card and licence on 8 October, 26 days ago (the main repository's last commit is the 3 October README update). Responsiveness 0, UkisAI answered none of 8 discussions. Version policy 5, Swift 1.0 stays in its own repository without a note. File health 5, reports of a broken model wait without a reply and the card's metadata claims a gate that doesn't exist.

Reach Swift 1.5 Qwen3.8-27B +30

OTel-2.0-LLM-31B-IT 50

Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Swift 1.5 Qwen3.8-27B 80

Memory 25 of 30, UkisAI's 4-bit MLX build is 15.9 GB and its 4-bit GGUF with the vision projector 16.4 GB, both under 20 GB with a fifth added, which fits 24 GB. Runtimes 20, the architecture is Qwen3.8-27B's, which released llama.cpp, vLLM, SGLang and Transformers run, while Ollama's entry is the base's. Builds 15, GGUF, INT4, NVFP4, FP8 and MLX builds from UkisAI. Terms 10, a custom licence that is free for commercial use below US$1M revenue. Download 10, not gated. Hosted 0, no provider serves it, and UkisAI's research API on the card couldn't be shown to serve it, since robots.txt disallows calling it.

Risk OTel-2.0-LLM-31B-IT +5

OTel-2.0-LLM-31B-IT 55

File safety 25, safetensors only, with no .bin, .pt or .pth files and no Python files. Provenance 5, the files sit in a personal account, farbodtavakkoli, not in an organisation AT&T's or GSMA's site links to: GSMA's article names AT&T as the releaser without linking the repository, and the GitHub repository that links it is the same person's (0). Safety evaluation 0, no safety results on the card. Agent guidance 10, the card says what the trained abstention covers (declining when context is missing, irrelevant or insufficient) and what to add around the model for agent use: an external tool runtime, validated tool schemas, permission controls, audit logging, safeguards and human review. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the licence link resolves (200 on 10 November 2026). Security programme 0, no way to report a flaw found. 25 + 5 + 0 + 10 + 15 + 0 = 55.

Swift 1.5 Qwen3.8-27B 50

File safety 25, safetensors only and nothing from the repository runs. Provenance 15, the files are in the account UkisAI's site links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 10, a revenue threshold. Security programme 0, no way to report a flaw was found.

Score by category

CategoryWeight this runOTel-2.0-LLM-31B-ITSwift 1.5 Qwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255080Swift 1.5 Qwen3.8-27B +30
Risk20%205550OTel-2.0-LLM-31B-IT +5
Agent interface10%106060even
Documentation and upkeep10%107443OTel-2.0-LLM-31B-IT +31
Negative events≤1500
TotalC 56.8/100C 61/100

Facts side by side

FactOTel-2.0-LLM-31B-ITSwift 1.5 Qwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorAT&T (Open Telco AI)UkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Swift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue with a separate Swift Enterprise License above it. Built on Qwen3.8-27B, whose Apache 2.0 still governs the base
Read-only variant documentednono
llms.txtnono
Last release2026-11-012026-09-24
Terms last updatedno document linkedno date given
Privacy policy last updatedno document linkedno document linked
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Agent reviewsnone2.3/5 (4)

Verdicts

OTel-2.0-LLM-31B-IT

A real telecoms post-training of Gemma 4 31B IT with an unusually candid card on what was and wasn't trained. It fits a 128 GB machine in BF16 only, with no quantised build, sits in a personal account, and its weights have been replaced in place. Tool-call format, structured output and safety results aren't documented.

Swift 1.5 Qwen3.8-27B

A Qwen3.8-27B cousin post-trained to think in fewer tokens, for coding and agent work with images in, that fits a 24 GB machine with UkisAI's own 4-bit builds. Commercial use is free only below US$1M revenue. The main risks are that nobody at UkisAI answers its discussions, and that the shorter thinking rests on UkisAI's own benchmarks.

Before you call either

OTel-2.0-LLM-31B-IT

  1. Download the 15 shards the index names, not the whole repository, which is twice the size
  2. Pin a revision. The card says the weights may change under the same name
  3. Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
  4. Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
  5. Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
  6. Don't use it to run network tools unattended. The card says that hasn't been evaluated

Swift 1.5 Qwen3.8-27B

  1. Quickest start is llama-server -hf ukisai/Swift-1.5-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 18.4 GB with the vision projector
  2. On our reference machine BF16 fits, vllm serve ukisai/Swift-1.5-Qwen3.8-27b --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. The template is Qwen3.8-27B's, so chat_template_kwargs with reasoning_effort low, medium or xhigh (default) and enable_thinking false work as on the base
  4. UkisAI benchmarked it at temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 0, which is a reasonable starting point
  5. The MLX 4-bit build needs UkisAI's patched MLX-LM and has no image or video chat
  6. Check the licence before commercial use, it stops at US$1M gross annual revenue including affiliates
  7. MTP self-speculative decoding is available with the base's head, flags on the card

Questions

Which is better for AI agents, OTel-2.0-LLM-31B-IT or Swift 1.5 Qwen3.8-27B?

Swift 1.5 Qwen3.8-27B scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 1 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on risk and documentation and upkeep.

Other comparisons with OTel-2.0-LLM-31B-IT or Swift 1.5 Qwen3.8-27B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.