174 Downloads Updated 4 days ago
ollama run orcarouter/DeepSeek-V4.1-Flash-1017-abliterated:mix-256g
Updated 4 days ago
4 days ago
d304f93d7430 · 347GB
DeepSeek-V4.1-Flash-1017-abliterated
The 763B abliterated (refusal-removed) DeepSeek-V4.1-Flash-1017 for Ollama — Engram streamed from SSD · vision · 1M context
MIT · 2 tags · 225 / 347 GB download · 114 / 236 GB in memory · vision bundled · thinking
Website · Model Catalog · Hugging Face · GitHub · Discord · X
🛡️ New from Orca — OrcaCyber Zero 1.5
Post-trained for cybersecurity: vulnerability analysis, vulnerability reproduction, red teaming & offensive-security research. 98.01% pass@1 on CyberGym Level 1 · 1M context · function calling · OpenAI-compatible API.
🛡️ New from Orca — OrcaCyber Flash 1.0
No 236 GB box? Run DeepSeek V4.1 Flash Abliterated as a hosted, OpenAI-compatible API on OrcaRouter: no download, no GPUs, one API key.
🔌 New from Orca — Orca Connect
Running this in Ollama on your own machine? Orca Connect puts the rig under your desk behind your usual OrcaRouter API key, next to 200+ hosted models, reachable from a laptop, a phone or a cloud agent. Outbound only: no port forwarding, no tunnel, no firewall rule. Requests your own hardware serves cost $0, and
orca-connect claudepoints Claude Code at your rig for one session.
These are Ollama builds of the abliterated (refusal-removed)
DeepSeek-V4.1-Flash-1017.
The model is a 763B-parameter MoE with 384 routed experts (top-6), a 197B-parameter Engram n-gram
memory, compressed sparse attention and a 1M-token context. The routed experts are the only part
the bits were spent on: every layer’s experts got their own precision from measured KL
divergence, not a hand-set rule.
The Engram table is a lookup that reads 48 rows per token. llama.cpp, and so Ollama, maps it from disk and reads it on demand, so it lives on your SSD, not in RAM. What has to fit in memory is everything else.
This model is built on an abliterated base whose safety alignment has been substantially reduced:
the refusal direction is orthogonalized out of every matrix that writes the residual stream. It will
comply with many harmful, unethical, offensive, or illegal requests that the original
DeepSeek-V4.1-Flash-1017 would refuse.
| Tag | In memory | Download (Ollama) | Experts | KLD ↓ | Top-1 ↑ | PPL vs. original |
|---|---|---|---|---|---|---|
mix-256g · latest |
235.8 GB | 347.4 GB | 3.36 bpw | 0.051 | 93.7% | +2.4% |
mix-128g |
114.0 GB | 225.5 GB | 1.59 bpw | 0.520 | 78.5% | +54.7% |
Mix-256G is the build to use. It needs a box with 256 GB of RAM, unified memory, or VRAM. At 3.36 bits per expert weight, the model’s next-token choice matches the unquantized model on 93.7% of held-out tokens.
Mix-128G fits 128 GB, but it is not a substitute. All experts at llama.cpp’s smallest type (IQ1_S) already take 111 GB, so a 128 GB box is at the floor: perplexity is 55% higher and one token in five differs from the original. Use it to try the model, not to rely on it.
In memory is everything except the Engram table. Download is the Ollama tag: it adds the 110.6 GB Engram table, which stays on disk, and the vision projector.
Requires Ollama v0.40.16 or later.
ollama run orcarouter/DeepSeek-V4.1-Flash-1017-abliterated # Mix-256G
ollama run orcarouter/DeepSeek-V4.1-Flash-1017-abliterated:mix-128g
cURL
curl http://localhost:11434/api/chat -d '{
"model": "orcarouter/DeepSeek-V4.1-Flash-1017-abliterated",
"messages": [{"role": "user", "content": "Hello!"}]
}'
Python
from ollama import chat
resp = chat(
model="orcarouter/DeepSeek-V4.1-Flash-1017-abliterated",
messages=[{"role": "user", "content": "Hello!"}],
)
print(resp["message"]["content"])
Image input
ollama run orcarouter/DeepSeek-V4.1-Flash-1017-abliterated "What is in this image? ./photo.png"
message.thinking. Pass
"think": false in the API, or --think=false on the command line, for direct answers.images field of a message, or as a file path in the prompt with ollama run.Both builds were scored against the lossless GGUF of the same checkpoint (MXFP4 experts, BF16 dense, MXFP8 Engram, converted bit-exact) on held-out text: wikitext-2 test, characters [0, 300000), 32 windows of 2048 tokens, full-vocabulary KLD. The precision search never saw this text. Each build is compared with llama.cpp’s own mixture at a similar size, quantized from the same weights with the same importance matrix:
| In memory | KLD ↓ | KLD p99 | Top-1 ↑ | PPL (original 2.259) | |
|---|---|---|---|---|---|
| Mix-256G (ours) | 235.8 GB | 0.0507 | 0.64 | 93.74% | 2.313 (+2.4%) |
llama.cpp IQ3_XXS |
212.2 GB | 0.2704 | 3.16 | 85.12% | 2.841 (+25.8%) |
| Mix-128G (ours) | 114.0 GB | 0.5202 | 4.95 | 78.50% | 3.494 (+54.7%) |
llama.cpp IQ1_S |
111.1 GB | 1.7307 | 9.02 | 54.80% | 11.858 (×5.2) |
Measured with the Engram table at MXFP8. The released files carry it at IQ4_NL (110.6 GB instead of 202.8 GB). The swap was not rescored. Per unsloth’s measurements on this model, the Engram precision barely moves top-1.
Method note. These are full-vocabulary KLD and next-token agreement on held-out text at 2k context, not a downstream benchmark.
Measured on the unquantized abliterated checkpoint, not re-measured on these GGUF builds. The KLD above is how far each build sits from that checkpoint.
Setup.
thinking_mode="chat", 64 new tokens.caveat means the model
answered but wrapped the answer in a disclaimer. Treat the numbers as indicative, not
publication-grade.Safety: harmful-prompt refusal (lower = more uncensored). Weighted mean over all 500 prompts: 0.074, against 0.874 for the base checkpoint.
| Benchmark | n | Base | Abliterated | Δ | Caveat |
|---|---|---|---|---|---|
| JBB-harmful | 100 | 0.950 | 0.030 | −97% | 0.360 |
| MaliciousInstruct | 100 | 0.930 | 0.020 | −98% | 0.610 |
| ForbiddenQuestions | 150 | 0.667 | 0.073 | −89% | 0.447 |
| SimpleSafetyTests | 50 | 1.000 | 0.120 | −88% | 0.560 |
| AdvBench | 100 | 0.990 | 0.150 | −85% | 0.550 |
Over-refusal: benign prompts wrongly refused (lower = better). Weighted mean over all 350 prompts: 0.006, against 0.069 for the base checkpoint.
| Benchmark | n | Base | Abliterated | Δ | Caveat |
|---|---|---|---|---|---|
| XSTest-safe | 250 | 0.052 | 0.008 | −85% | 0.028 |
| JBB-benign | 100 | 0.110 | 0.000 | −100% | 0.140 |
Capability retention.
| Benchmark | n | Base | Abliterated |
|---|---|---|---|
| MMLU (zero-shot, answer letter read from the next token) | 300 | 0.910 | 0.920 |
MMLU is unchanged; the one-point difference is within the sampling error of 300 questions. It is the only capability measured.
| Base model | The abliterated build of deepseek-ai/DeepSeek-V4.1-Flash-1017 |
| Architecture | deepseek41 in llama.cpp. 40 layers, hidden 5120, compressed sparse attention, LoRA-factorised output projection (8 groups), 384 routed experts top-6 + 1 shared expert, Engram n-gram lookup at layers 1 and 14, 4-wide Hyper-Connections |
| Weights in these files | 748.5B: 543.6B routed experts, 196.6B Engram, 8.2B attention / shared experts / embeddings / head. ~6 of 384 experts active per token |
| Quantization | Per-layer mixed precision found by measured-KLD search. Experts are IQ2_S–MXFP4 (256G) or IQ1_S–IQ2_XXS (128G). Dense parts are Q5_K–Q8_0 (256G) or Q4_K–Q6_K (128G). Engram is IQ4_NL. Uses an importance matrix. |
| Context | 1,048,576 tokens (inherited; evaluated at 2k) · Vocabulary 129,280 |
| Runtime | llama.cpp with PR #30817, or Ollama v0.40.16+; text and images in, text out; tool calls in DeepSeek’s DSML format |
DeepSeek-V4.1-Flash-1017. Long-context behaviour was not
tested: all measurements are at 2k context or on short chats.MIT, inherited from the base model
deepseek-ai/DeepSeek-V4.1-Flash-1017.
The embedded chat template is unsloth’s port of DeepSeek’s encoder
(unsloth/DeepSeek-V4.1-Flash-1017-GGUF, MIT).
Route Smarter · Ship Safer · Spend Less