Should you use RAG or fine-tuning to teach a model new information?

RAG for facts that change or need a citation, fine-tuning for a fixed skill, tone, or format you want baked into the model itself. RAG leaves the model’s weights untouched and looks up the relevant chunk of your corpus at request time, so updating a document takes effect on the next query with no retraining, and it gives you something fine-tuning can’t: the actual passage an answer drew from, so a reader can check it. Fine-tuning does the opposite. It changes what the model does by adjusting its weights, so the new behavior holds even without a retrieval step, but every change to what it should know means training again.

The two aren’t a choice between opposites so much as a division of labor. A fine-tuned model can still receive retrieved context, and teams commonly fine-tune the stable parts of behavior, like tone, output format, or when to call a tool, while using RAG for whatever keeps changing underneath it, like documentation, prices, or policy.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y