Skip to content

Build · Private model and fine-tuning

A private model, only when the hosted model falls short

Evaluate first. Fine-tune an open model in your own cloud account only if the hosted model falls short.

Who it is for
A company whose hosted model may fall short on its task.
Length
Typically two to six weeks

What you get

  • A connection (endpoint)

    The fine-tuned open model, available as a connection you can call.

  • A comparison report

    Accuracy and speed, side by side with the hosted model.

  • Your cloud account

    The model runs in your own cloud account.

  • Standalone or after a sprint

    Buy it on its own, or after an AI production sprint.

  • Your environment

    The model runs in your own cloud account. We do not train on your data without written consent.

How it works

  1. Evaluate first

    The hosted model is evaluated on your task before anything else.

  2. Fine-tune only if it falls short

    An open model is fine-tuned only when the evaluation shows the hosted model is not good enough.

  3. Compare and hand over

    You receive the connection (endpoint) and a report on accuracy and speed.

What you keep

A connection in your cloud account, and a comparison report that shows whether it is worth it.

Book a call

Questions

When do we need a private model?
When the evaluation shows the hosted model falls short on your task.
Where does it run?
In your own cloud account.
Can we buy it without a sprint?
Yes. It can be bought on its own, or after an AI production sprint.
What decides whether it is worth it?
An evaluation set built from your cases. The comparison report shows whether the private model beats the hosted one on those cases.

Private models

Our fine-tuned model against a large general-purpose model

We fine-tune a small model on one sample task and measure it against a large general-purpose model that only gets instructions, with no fine-tuning. Both are scored on the same test set.

  • 3.5×

    better reply quality

  • ~16×

    better key fields

  • ~50×

    faster replies

  • ~125x

    estimated lower running cost per ticket (internal estimate)

Reply quality as the training set grows

We fine-tuned a small model on a sample business task in our internal testing, trained it on more and more examples, and scored each version on the same held-out test set. A large general-purpose model gets only a prompt.

  • +252%

    higher reply quality

  • 3.5×

    times the large model's reply quality

Our fine-tuned model at the largest training set, against the large model.

Reply quality as the training set growsReply quality by training examples. Our fine-tuned model: 350 → 0.130, 700 → 0.369, 1,400 → 0.649, 2,800 → 0.771, 5,600 → 0.792. A large general-purpose model: 0.225.Reply quality00.510.1300.3690.6490.7710.7920.225Reply quality, Training examples 350: 0.130Reply quality, Training examples 700: 0.369Reply quality, Training examples 1,400: 0.649Reply quality, Training examples 2,800: 0.771Reply quality, Training examples 5,600: 0.7923507001,4002,8005,600Training examples
  • Our fine-tuned model
  • A large general-purpose model
Reply quality as the training set grows
Training examplesOur fine-tuned modelA large general-purpose model
3500.1300.225
7000.3690.225
1,4000.6490.225
2,8000.7710.225
5,6000.7920.225
Synthetic held-out test set for one support-ticket task.

Results on a support-ticket task. Your results depend on your data.

Sample task: support tickets. Synthetic test set held out from training. The large model got instructions and no fine-tuning. The operations comparison is an internal estimate from compute time, not a measured invoice.

Next step

Bring one process.

30 minutes. An honest answer on whether AI fits.

Other offers

All offers