Arete 27B is Nous Research's free, Apache 2.0 fine-tune of Qwen3.8-27B, built to stop the model giving Chinese state-framed answers on political topics. On Nous's own 803-prompt test, party-line answers fell from 22% to 0.9%, while coding and agent scores held. The bigger lesson is how cheap that was: about 52.8M tokens of supervised training, no RL. A model's values sit in a thin layer you can change.
For a support team, that layer is better set in instructions and tested on past tickets, which is the job eesel's AI helpdesk teammate does on top of whichever model runs underneath.
What is Arete 27B?
Arete 27B (Nous writes it Arete-27B) is a 27-billion-parameter open-weight large language model that Nous Research released on November 6, 2026. It is built on Alibaba's Qwen family. In its own words, Nous "post-trained over Alibaba's Qwen3.8-27B to reinforce Western values on a Chinese-trained model." The weights, the evaluation and the training data all went public the same day, announced in a launch post on X that passed 13,000 likes.
I work on SEO at eesel as well as writing code, and the search intent behind "Arete 27B" is unusually mixed. Some people want to run it, some want to know if it's propaganda in the other direction, and some are deciding whether an open model from China is safe to build on at all. I'll take those in that order, and I'll keep Nous's own numbers separate from anything independent, because right now almost every figure comes from Nous.
Here is the spec sheet, from the model card and the base model's card:
| Arete 27B | |
|---|---|
| Developer | Nous Research |
| Released | November 6, 2026 |
| Base model | Qwen3.8-27B (Alibaba) |
| Parameters | 27.36B, dense |
| Weights | Open, BF16 safetensors, 18 shards |
| License | Apache 2.0 |
| Post-training | Supervised fine-tuning only |
| Teacher model | Inkling (Thinking Machines Lab) |
| Context (base model) | 262,144 tokens native, extensible to 1M |
| Training context | 64K |
| Hosted API | None at launch |
The name is Greek: arete means excellence or virtue, and an arête is also a knife-edge ridge between two glacial valleys, which is what the cover art shows. Nous says the double meaning is on purpose.
Nous is better known for its Hermes Agent and the Hermes model line, so this is a research release more than a product launch. That matters for how you read it, and it's why I think the useful question isn't "is this the best 27B model" but "what does this experiment show about open models".
If you're building agents on open models, the same idea applies at the application layer. With the eesel CLI, an AI coding agent like Claude Code can upload your approved help articles and policies to an eesel support agent, adjust its instructions, and ask it test questions to check the answers before it goes live. Connecting your helpdesk still needs someone with admin access to approve it.
What did Nous Research change in Qwen3.8-27B?
Only the post-training. Nous wrote 20,000 prompts across seven value categories, collected answers from a teacher model it trusted on those topics, and fine-tuned Qwen3.8-27B on them. The blog post is unusually specific about every step, which is the main reason I'd trust the shape of the result even before anyone reproduces it.
The seven categories were freedom of expression, state ideology, state versus free market, education, data privacy and surveillance, democracy, and the environment. Before training, Nous removed every training prompt that overlapped the held-out evaluation set, so the model wasn't graded on questions it had studied.
The teacher choice is the interesting part. Nous wanted an open model to learn from, partly to avoid terms-of-use fights over "illicit distillation". It says it strongly considered NVIDIA's Nemotron 3 Ultra but found "it too had a checkered record on China-related topics", and theorizes the bias came from Nemotron itself being trained with help from Chinese open models. Nous adds that "the vast majority of high quality open models are Chinese", which anyone comparing Qwen alternatives like Kimi K3 will recognize. It settled on Inkling, Thinking Machines Lab's open model, which scored best on its eval.
The training run itself, per the model card:
| Setting | Value |
|---|---|
| Training examples | 28,886 (26.4M tokens per epoch) |
| Total tokens | About 52.8M over 2 epochs |
| Steps | 1,202 (601 per epoch), batch size 48 |
| Learning rate | Warmup to 1e-5 over 120 steps, cosine decay to 1e-6 |
| Optimizer | AdamW, weight decay 0.1 |
| Precision | bf16 compute, fp32 master weights |
| Trained | All language-model weights |
| Frozen | Vision encoder (training data was text-only) |
| Disabled | Multi-token-prediction head |
| Not used | RL, preference optimization, architecture changes |
One point worth clearing up early: this is full fine-tuning of every language-model weight, not a LoRA adapter. A reply on X with over 1,300 likes called it "just a LoRA", which is a fair mood but the wrong mechanism.
Nous's own summary of what it learned is the line I'd remember: "the bias layer in a Chinese-aligned model is shallow. It is applied late, it is applied thin." Against Qwen's pretraining, 52.8M tokens is a rounding error.
How much did Arete 27B's answers actually change?
A lot, on the axis Nous measured. On its Propaganda_Eval set of 803 prompts, the share of answers that adopted the Chinese state's account fell from 22% to 0.9%, and the fact score rose from 2.32 to 2.98 out of 5. (The model card says 0.9%; the blog prose rounds it to 1%.)
The eval works like this. Each prompt comes with 2 to 4 required facts from a dated source article, plus the official-frame language the Chinese government uses on that topic. An LLM judge, Grok 4.7, grades each answer without knowing which model wrote it. "Propaganda" has a strict definition: the answer has to replace a fact with the official line, or endorse it, and the judge must quote the exact phrase. Quoting the official line to identify it doesn't count.
Here is the full comparison table from the blog post, five runs per model:
| Model | Fact mean (0-5) | Any propaganda |
|---|---|---|
| Inkling (teacher) | 3.96 | 0.3% |
| Mistral Large 4 | 3.65 | 0.3% |
| Muse Glimmer 30B | 3.02 | 0.5% |
| Gemma 4 31B | 2.58 | 0.5% |
| Nemotron 3 Ultra | 3.22 | 0.6% |
| Arete-27B (thinking on, provisional) | 3.07 | 0.6% |
| Arete-27B (thinking off) | 2.98 | 0.9% |
| GLM 5.3 | 3.10 | 15% |
| DeepSeek V4.1 Flash | 2.39 | 16% |
| Qwen3.8-27B (base) | 2.32 | 22% |
Three details in that table are easy to miss.
First, the propaganda drop is much bigger than the fact gain. Arete went from the Chinese cluster to the Western cluster on framing, but its fact score of 2.98 still sits below Nemotron, GLM 5.3 and Mistral Large 4. It stopped repeating the official line faster than it learned the missing facts.
Second, the biggest change was in freedom of expression: the fact score went from 0.89 to 2.44 and the propaganda rate from 60% to 1%. The number of answers scoring zero across the whole set fell from 359 to 216.
Third, the decoding settings aren't identical. Arete and the base Qwen ran at temperature 0, everything else at 0.6. At 0.6, Arete scores 2.88 and the base model 2.24, so the gap holds, but the cleaner comparison is between those two rows.
Did Arete 27B lose any coding or agent skill?
Not on Nous's tests. That's the result that makes this release more than a political statement, because a values fine-tune that wrecked the model's coding would be a curiosity. Many people run Qwen3.8-27B as a local coding and agentic AI model, so this is the table most builders actually care about.
| Benchmark | Qwen3.8-27B | Arete 27B |
|---|---|---|
| Hermes Bench (Nous internal) | 65.77% | 65.60% |
| Terminal-Bench-2.1 (Nous's own run) | 67% | 70% |
Nous calls the 0.17-point Hermes Bench drop noise, and says it does "not take credit" for the Terminal-Bench gain because its harness differs from the official one. I'd read both rows as "no regression found", which is a weaker claim than "no regression". There's no Artificial Analysis listing or other independent result yet, and the card doesn't report any vision or long-context tests, even though the base model is a native vision-language model and the training only used text at 64K context.
If you're choosing between this and the stock model for coding, my read is that it's a wash on the evidence so far. Pick the one whose behavior on non-code prompts you prefer.
How do I run Arete 27B, and what does it cost?
It costs nothing to download, and there's no API to pay for yet. The weights are on Hugging Face under Apache 2.0, and the card says the model "isn't deployed by any Inference Provider". It also wasn't on OpenRouter when I checked its public model list on November 8, 2026. So the real cost is your hardware.
The full BF16 weights come to roughly 55 GB across 18 files, which is a multi-GPU or large unified-memory setup. Most people will use a quantized version. Hugging Face already lists 34 quantizations; the widely used bartowski GGUF set has these file sizes:
| Quantization | File size | Rough fit |
|---|---|---|
| IQ4_XS | 15.2 GB | 24 GB GPU with room for context |
| Q4_K_M | 17.2 GB | 24 GB GPU, the usual default |
| Q5_K_M | 20.7 GB | 24 GB GPU, short context |
| Q6_K | 23.6 GB | 32 GB GPU or Mac |
| Q8_0 | 28.7 GB | 32 GB+ GPU or Mac |
| BF16 (original) | ~55 GB | 2 GPUs or 64 GB+ Mac |
The "rough fit" column is my own arithmetic: file size plus headroom for the KV cache, which grows with the context window you actually use. Because Arete keeps the Qwen3.8 architecture, the same runtimes work: Qwen lists Transformers, vLLM, SGLang and TokenSpeed, and the GGUF builds run in llama.cpp and the apps built on it.
Two setup notes from the base model's card carry over. Thinking mode is on by default and can be turned off per request, and Nous's headline numbers were measured with thinking off. The only thinking-on row is provisional, from 2 of 5 runs.
If you don't want to manage hardware at all, the closest hosted options are the Qwen family's own Qwen3.8 Max (see how to access it) or Thinking Machines' Inkling 2 Small on its Tinker platform.
What are people saying about Arete 27B?
It split people. The r/LocalLLaMA thread passed 270 upvotes and 280 comments within two days, at only 73% upvoted. One of the top comments, with 229 points, asked whether Nous had simply "replaced eastern propaganda with western propaganda". The best reply to that, I think, made the open-weights argument:
"Models have inherited behavior based on how people decide to train them. That's true for Qwen models and that's true for Anthropic. The good thing about open weights is that you can remove that and make it yours."
Others agreed the base model had a real problem but questioned the label:
"I mean Qwen does tend to refuse to answer directly when asked about certain historical events in China, if nothing else. But this project seems to have an extremely specific idea of what constitutes western thought."
On Hacker News, the main thread went after the method rather than the politics. The judge model got the sharpest criticism:
"Grok is definitely the last model I would choose to be a 'judge' as to whether or not your model is now impartial for "western values"."
The most practical question came from a llama.cpp user: "Interesting, but is it better than just abliterating a model." Nobody in the thread had a measured answer. It's a fair question, since abliteration removes refusals but doesn't add missing facts, and Arete's fact score is the half of the result that abliteration wouldn't touch.
What's the catch with Arete 27B?
The catch is that it's graded by its own maker. Nous built the eval, chose the teacher, chose the judge, and ran the capability tests on its own hardware. It published all of it, which is more than most labs do, but nobody has reproduced the numbers yet.
Four specific limits I'd keep in mind:
- The judge is another model. Grok 4.7 decides what counts as a stated fact or as propaganda. Nous hand-graded a 25-prompt pilot and revised the rubric three times, which helps, but 25 prompts is a small calibration set for 803.
- "Western values" is a label, not a measurement. The eval measures one thing well: whether answers repeat the Chinese state's framing on 803 China-related prompts. It doesn't test US or European political bias, so a low score here doesn't mean the model is neutral.
- Vision and long context are untested. The vision encoder was frozen and training ran at 64K, so image tasks and very long prompts should behave like the base model, but the card doesn't confirm it.
- The cited security risk is contested. Nous's motivation includes outside reports that Chinese models write less secure code for American users. Commenters in the Reddit thread disputed how those tests were set up, and Arete's release doesn't include a code-security evaluation of its own.
None of that makes the result wrong. It makes it a well-documented first experiment, and Nous says as much in its own write-up.
Does Arete 27B matter for customer support?
Less than the headlines suggest, but the lesson does. Very few support tickets touch Tiananmen or press freedom. What Arete really shows is that a model's default point of view is a thin, adjustable layer, and that's true for the things support teams care about too: tone, refund policy, what to promise, when to hand off. In support, those are AI guardrails, and a model that drifts outside them is a bigger day-to-day risk than its politics, mostly through AI hallucination.
The difference is where you make the change. Nous changed the weights because it wanted to publish a model. A support team almost never needs to, because the layer it controls sits above the weights.
A version of this worry comes up on eesel sales calls all the time. One technical evaluator at a hardware company asked whether the AI quietly falls back on "some kind of other ChatGPT" when it doesn't know an answer, and whether that could be switched off. That is the same question Arete raises, from the business side: whose knowledge and whose rules is this model really using?
The answer eesel has landed on, after a few years of running AI on live support queues, is that you write the rules down and make the agent follow them. Cactus Club Cafe, a Vancouver restaurant group, runs its internal tech support in Zendesk with an eesel AI agent called Tixie. Tixie reads the team's emergency policy and routing matrix before every ticket, then drafts the fix from the matching runbook as written, with nothing improvised. In one month it handled about 750 tickets, wrote about 790 drafts for the team, and read runbooks and policies about 1,650 times, roughly two documents per ticket.
Nobody fine-tuned a model for that. The behavior comes from documents the team wrote and can change in an afternoon, which is the practical version of Nous's point that values are "one fine-tune away".
Arete is infrastructure; eesel is the employee. The model is the engine, and an AI helpdesk teammate is the hire who learns your help center, follows your policies, and hands off what it shouldn't answer. If you're still picking an engine, the best AI model for support tickets guide compares the options, and preventing AI hallucinations in support covers the testing side. For self-hosted agent frameworks, see best open source AI agents and Nous's own Hermes Agent for customer support.
Try eesel
If Arete has you thinking about how much a model's defaults shape what your customers hear, the fastest fix isn't a training run. eesel is an AI helpdesk teammate that joins your existing helpdesk, learns from your help center, macros and past tickets, and follows the policies you write, the way Cactus Club's Tixie follows its runbooks. You can run it against your historical tickets first to see exactly what it would have said before it replies to anyone. Try eesel free, or check pricing first.
