Beta · v8 and v8.1

Open weights.
Your model. Your control.

Open-weight models for customer service, forestry, fisheries and general-purpose work. Built to give individuals and organizations control over their AI, not lock them into Big Tech.

Release target: less than 1% hallucination on a defined evaluation, alongside quality, privacy and security checks. This target is not yet achieved or a guarantee across all uses.

BETA RELEASES · EVALUATION CONTINUES Early launch release is out · Full launch: January 2, 2027 Download now: Atlantic v8 and Atlantic Lite v8.1
Two colleagues discussing their work together at a laptop.
Illustrative stock photograph. Photo: Vitaly Gariev / Unsplash · License.

Meet our LLMs.

Two general-purpose models you can download and run today, and two specialists in development. Both released models have open weights under Apache 2.0. Versions 6 and 7 are withdrawn because the newer versions are more accurate and safer.

Krummholz models are not built to be maximally helpful. They are built to seek the truth and to hold to a written constitution: a collaborator, not an assistant. They say "I don't know" rather than guess, and decline rather than help with harm. The constitution is printed in full on the Atlantic v8 and Atlantic Lite v8.1 model cards.

General purposeDownload · v8 beta

Atlantic

27B · workstations, desktops and hosted use

Questions, writing, planning and document work, with room to reason. Ships with a vision projector for images.

Version
Atlantic v8
Files
About 17 GB (Q4_K_M) or about 19 GB (Q5_K_M), plus vision projector and LoRA adapter
License
Apache 2.0
Released
November 15, 2026
General purposeDownload · v8.1 beta

Atlantic Lite

4B · phones and low-end hardware

The same Krummholz training in a model small enough for a phone. Ships with a vision projector for images. Run it behind the Krummholz harness or an equivalent filter.

Version
Atlantic Lite v8.1
Files
2.7 GB (Q4_K_M, for phones), 3.1 GB (Q5_K_M) or full precision, plus vision projector and adapter
License
Apache 2.0
Released
November 15, 2026

Atlantic Lite v8 (November 14, 2026) stays available: Lite v8 on Hugging Face.

Customer serviceIn development

Acadia

Support that knows when to hand off

Answers grounded in a company’s approved policies, request classification and clear escalation to people. The first pilot covers one text-based service workflow. Still in development.

Built from
Atlantic v8 (27B), by distillation
Inherits
The same constitution and harness
Status
Not trained yet; no release date
Forestry & fisheriesIn development

Katahdin

Domain knowledge, working-world context

A planned assistant for understanding field records, finding source material and explaining reviewed analyses, paired with validated analytical tools. Still in development.

Built from
Atlantic v8 (27B), by distillation
Inherits
The same constitution and harness
Status
Not trained yet; no release date

Benchmarks

Before and after.

Each row shows the new release, with the previous version underneath. Old and new took the same evaluation, on full-precision weights with reasoning on: 229 held-out fact questions asked without tools and again with tools, 199 probe questions, 120 long prompts, 60 tool-use turns, 120 false claims and HarmBench (300 harmful behaviors, official classifier, never used for training).

Atlantic

27B · v8, compared with v7

Wrong on fact questions, no tools16% (37)v7: 49% (113)
Right on fact questions, no tools48% (111)v7: 50% (114)
Says it does not know35%v7: 1%
Wrong among the answers it gives from memory25%v7: 50%
Searches when given tools81%v7: 51%
Reasoning never finished, with tools0v7: 34%
Long prompts: repeats itself or runs into the limit0 / 120v7: 25
Tool calls well formed60 / 60
HarmBench harmful replies, model alone0 / 300v7: 1
Corrects a wrong calculation stated as fact59 / 60
Corrects a wrong fact offered for confirmation10 / 30
Probes passed168 / 199v7: 172
Mean reply length263 tokensv7: 477

Q4_K_M file: being measured.

Atlantic Lite

4B · v8.1, compared with v8

Wrong on fact questions, no tools2% (5)v8: 3% (7)
Right on fact questions, no tools33% (75)v8: 28% (63)
Says it does not know62%v8: 49%
Reasoning never finished3% (8)v8: 20% (46)
Wrong among the answers it gives from memory6%v8: 10%
Tool calls well formed60 / 60
HarmBench harmful replies, model alone10 / 300v8: 24
HarmBench harmful replies, behind the Krummholz harness0 / 300v8: 2
Corrects a wrong calculation stated as fact39 / 60v8: 29
Corrects a wrong fact offered for confirmation10 / 30v8: 7
Harmless requests refused19 / 120v8: 4
Probes passed117 / 199v8: 132
Mean reply length338 tokensv8: 511

Q4_K_M file (phones): without tools 24 wrong (10%), 88 right and 108 "I don't know" of 229; with tools no wrong answer; HarmBench 6 of 300 for the model alone and 0 of 300 behind the harness.

For scale, Atlantic Lite v7 was wrong on 52% of fact questions without tools. With tools, Lite v8.1 searches on 91% of fact questions and Atlantic v8 on 81%; neither gave a wrong answer among those it answered without searching (44 answers for Atlantic v8). The harness rules were written on half of HarmBench, so the harness figure is partly in-sample. Lite refusing more harmless requests is a trade we accepted: refusing a safe request is the lesser evil against accepting a harmful one. The model cards have the full results: Atlantic v8 · Atlantic Lite v8.1.

Release goals

Where the release goals stand.

Under 1% hallucination: not reached.

Without tools, Lite v8.1 is wrong on 2% of fact questions and Atlantic v8 on 16%. With search tools, neither gave a wrong unsearched answer in this test. The test set is small (229 questions).

Tool use.

60 of 60 well-formed tool calls on both models.

Harmful requests.

0 of 300 for Atlantic v8 on its own and for Lite v8.1 behind the harness. Lite on its own: 10 of 300, so Lite must run behind the harness or an equivalent filter. The harness source is not published yet.

Consumer hardware.

The Lite Q4_K_M file is 2.7 GB. Phone acceptance tests have not run yet.

Dynamic weights.

User-reviewed learning is in development and not released.

Known weak spots.

Pushback on false facts (10 of 30), probe scores dipped, and more harmless requests are refused.

After reading these answers we fixed five gaps in our scorer and runtime, and both model cards say so. The model cards list every suite and result. Read the model cards →

MODEL PERSONALIZATION / PLANNED PERSONALIZATION

What I learned today.
You decide what stays.

Dynamic weights describes our planned user-reviewed learning: models adapt only through approved changes. The mechanism and architecture remain under evaluation.

Review before learning.

“What I learned today” will let users accept, reject or edit proposed learning. Retention and training require separate opt-in choices. Business administrators set who can approve changes.

Your model can become different.

Approved learning may make your local model differ from hosted versions. Version information will explain those differences. Local learning will not automatically be shared with hosted models.

Learn without losing the foundations.

We aim to carry approved learning into future model versions. Compatibility, backup, migration and rollback still need testing.

Guard against unwanted change.

Planned safeguards include source tracking, untrusted-input isolation, bounded updates, adversarial tests and rollback. They reduce risk, not eliminate it. Learned preferences never grant tool permissions.

In development: Learning review and update preservation are not released and may follow the first pilot.

Company update: Training continues for now. Read Hayven’s note about Belfast and what comes next.

Adapt carefully.
Measure what changes.

Version 8 starts from the v7 weights and adds rounds of preference training (DPO) with reasoning on. In each round the model answers questions with known answers, and code (not a person, not another model) labels each of its own replies: right, wrong, a clean "I don't know", a well-formed tool call, a correction of a false claim, and so on. The model is then trained to prefer its own better reply over its own worse one. Apart from a few fixed opening words, no training text in v8 was written by a person or by another model.

New in this release: short, plain refusals of harmful requests, pushback on false claims built by code, finishing with "I don't know" instead of running out of reasoning, and not calling a tool that was not offered. A control run with shuffled labels did not improve, so the gain comes from the labels.

Disclosure carried over from v7: math and code solutions from public NVIDIA datasets, written by DeepSeek-R1 and QwQ-32B, made up about 13% of Atlantic Lite v7’s training examples and about 29% of Atlantic v7’s smaller set. That is outside our policy of training only on text from American open-weight models. Version 8 adds no such text, but it continues from the v7 weights, so that material is still in its lineage.

The long version of how v8 was trained, for fellow nerds →

Atlantic v8 model card → · Atlantic Lite v8.1 model card → · All weights on Hugging Face →

Our business model pairs open weights with paid hosted inference and private-data training for companies and individuals. Hardware support, offline scope, routing and hosted limits will follow testing. Private-data training requires explicit permission and separate terms.

Inspect our preliminary text-data pilot →

Inspect the model-development repository →

  1. Review the foundations.Check the base model’s documented lineage, license, runtime compatibility and suitability for the proposed work.
  2. Trace the training material.Prioritize open and public-domain data. Admit synthetic or non-public material only with documented origin and applicable permissions.
  3. Curate and separate.Screen for privacy issues, duplicates and quality problems. Keep evaluation examples separate from generation and training.
  4. Train a bounded specialization.Compare practical adaptation methods and retain the versioned data, settings and checkpoints needed to understand the result.
  5. Evaluate before release.Test task quality, source support, refusals, human handoffs, privacy, tool authorization and real-device behavior. Hold back capabilities that fail.

BESPOKE AI TRAINING

Adapt a model
to your work.

Discuss a scoped training project using data you are authorized to use. We start with the task and evaluation criteria, compare fine-tuning with retrieval and other options, and plan around your deployment requirements.

Explore bespoke training →

Consent is part
of the architecture.

We plan transient processing by default. Saved history, retrieval indexes, cloud processing and private-data training will have separate, explicit choices.

Retrieval can supply current policies without retraining. Training on private data is a separate, opt-in service.

Our synthetic datasets support model development and customer experiments, with generated content clearly labeled.

Useful answers.
Honest limits.

We favor source-backed answers, visible uncertainty and escalation when evidence is insufficient. Evaluations will report known limits.

Documents and websites are untrusted inputs. Permission checks stay outside the model. We will disclose hosted processing and identify what works offline.

Our neutrality goal is consistent evidence standards and fair treatment of relevant perspectives, assessed through defined evaluation cases.

A focused first milestone.

The early launch release is out: Atlantic v8 and Atlantic Lite v8.1, open weights. Full launch: January 2, 2027. The models are still in beta. Further releases depend on evaluation, privacy, security and license review.

Our LLMs are released with open weights under Apache 2.0. Third-party base models and components retain their applicable licenses and notices. Code and datasets keep their own licenses.

Current status: Atlantic v8 and Atlantic Lite v8.1 are in beta, released November 15, 2026. Versions 6 and 7 are withdrawn. The 35B core is deprecated; Acadia and Katahdin will be distilled from Atlantic v8, are not trained yet and have no release date. No hosted service is available yet. Dynamic weights are in development and not released.

Discuss a pilot workflow →