For privacy reasons a browser tells us at most
"≥ 8 GB RAM, 8 cores" - same reading whether you have 8 GB
or 128 GB. It has no idea how much RAM is free right now, which
apps are open, or whether you have a GPU.
The Abliteration app is integrated with your machine
It reads your exact RAM, GPU model and VRAM,
free memory right now, and picks the sharpest quant that
still fits. Every model page lights up precisely for your rig.
And you can chat with any model, right now
The app is a full local runtime - no API keys, no subscription,
everything runs on your machine. Click any model on this site and
start a conversation in seconds.
Method inferred from partial signals - repository name, related files, or tag patterns. Producer identity not confirmed; label may sharpen or shift as we gather more evidence.
'abliterated' in name/tags
is_gguf=0 (base model)
no specific method indicators - defaulting to M1 (most common)
Full BF16 weights of Nemotron-3-Ultra-550B-A55B-abliterated-uncensored — an abliterated, uncensored variant of NVIDIA's Nemotron-3-Ultra-550B-A55B (550B total / 55B active). The abliteration was applied directly to the full-precision BF16 weights (highest fidelity — no quantization round-trip), and the model keeps Nemotron-3's hybrid Mamba-2 / Attention / Latent-MoE reasoning stack fully intact — including the MTP speculative-decoding head and the enable_thinking reasoning mode. Tensor names, shapes and config.json (NemotronHForCausalLM, model_type: nemotron_h) match the base model exactly, so it is a drop-in replacement and the ideal source for your own quants (NVFP4 / FP8 / AWQ / GGUF).
The pipeline:
Refusal Ablation — A residual-stream refusal direction was extracted by diff-in-means on a labeled harmful/harmless prompt set, read at the end of the model's own reasoning trace (</think>), then baked into the BF16 weights as an offline orthogonal projection on the residual-write modules — using our own custom abliteration framework. No training.
Layer-profiled edit — The projection is concentrated on the mid-network layers that carry the refusal decision and tapered to zero on the early layers (token/fluency) and final layers (output stability), removing refusals while preserving coherence and factual precision.
Capability preservation — The direction was orthogonalized against language / multilingual and security-analysis subspaces so multilingual fluency and genuine security/technical engagement are retained.
Sampling:temperature=1.0, top_p=0.95 (the values in generation_config.json). A mild repetition_penalty (~1.1) is recommended for long generations.
Thinking mode: set enable_thinking=True in chat_template_kwargs; reasoning streams inside <think>…</think> before the answer. Do not feed previous-turn reasoning back into multi-turn history.
Hardware
Full BF16 weights are ~1.1 TB. Serving in BF16 needs a large multi-GPU node or multi-node setup (e.g. 16× H100/H200, 8× B200/B300, or 2 nodes with tensor + pipeline parallel). For single-node or smaller deployments, use the NVFP4 build (~329 GB, fits 4× B200/B300 or 8× H100), or quantize these weights yourself (FP8 / NVFP4 / AWQ / GGUF).
Notes
License: OpenMDW-1.1 (inherits from the base model)
Use is the responsibility of the user. Ensure your usage complies with applicable laws, platform rules, the OpenMDW-1.1 license terms, and your deployment requirements.
README history
2 versions
The author's README evolved over time. Click a version to see its content at that point.
2026-06-16Move Support & Community section to top (below banner); unify across modelsb69bc9d6 KB
Loading...
2026-06-11Upload folder using huggingface_hube450afb6 KB
Loading...
Catalog is the map. Apps are the tools.
Run models on your own machine, not in the cloud.
Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.