Local models

Your local AI already runs. Now let’s make it right.

We deploy open models on your servers or in an EU cloud, measure them on your real cases and, only when the numbers call for it, fine-tune them for your task. Your data stays in-house and the weights are yours.

What it covers: Open models, On your servers or in the EU, Evaluation on your cases, Fine-tuning with LoRA and QLoRA, Catalan and Spanish, Vision on your images, You keep the weights, Evaluation report

Before training, we measure. Often a good open model with your documents is enough; when it is not, we prove it with numbers and train only what is needed.

Four ways to start

From a review of the AI you already run to a model trained for your task. All of them start from an evaluation set built on your cases.

Rescue

Your local AI, evaluated and tuned

You already run Ollama, vLLM or LM Studio, but you don’t know how often it is right or how to improve it. We review it, build an evaluation set from your cases and make the first adjustment.

  • Review of the model, the instructions and document retrieval
  • Evaluation set built on your real cases
  • First adjustment, measured before and after

Deployment

An open model on your infrastructure

We pick the model that best solves your task, install it on your servers or in an EU cloud and leave it running inside your network, with its licence checked.

  • Model comparison on your data
  • Served with vLLM, llama.cpp or Ollama
  • Licence checked for commercial use

Fine-tuning

A model trained for your task

When the evaluation shows that a model with your documents falls short of the quality, speed or cost you need, we fine-tune it with LoRA or QLoRA on your examples.

  • Data prepared and reviewed by people
  • Training on our own GPU or a rented one in the EU
  • Compared with the base model on the same evaluation

Vision

Vision models trained on your images

Detection, counting or classification trained on photos from your operation: crops, defects, parts or traffic. Small, fast and able to run offline.

  • Labelling with human review
  • Validated on images the model has not seen
  • Ready to run on your own hardware

How we do it

It is the method of Sostingut Lab, our tool for evaluating and training models. Every step leaves numbers you can check.

  1. We define the task and your success criterion

    What the model has to do and when you consider it good, in your words and with a threshold.

  2. We measure what you have today

    A baseline: your current system, a simple rule or the model you already use. Without a baseline there is no improvement to prove.

  3. We build the question bank

    Real cases with their answer and where it comes from, validated by someone on your team.

  4. We calibrate the judge

    If a model scores the answers, we first check on a blind sample that it agrees with a person.

  5. We compare options

    Open models running locally and, if your data allows it, a commercial one; with and without your documents.

  6. We train only if needed

    Fine-tuning when the comparison shows a gap that your documents do not close.

  7. Report and follow-up

    Results with confidence intervals, a technical sheet in the style of the EU AI Act and a new evaluation every month.

What you keep

The weights
The tuned model is yours and runs on your infrastructure.
The evaluation
The question bank and the results, to measure again when the base model changes.
The process
The documented steps to repeat the training with new data.
The technical sheet
Which data was used, how it was evaluated and where it fails, ready for your inventory of AI systems.

What we don’t do

  • Train a language model from scratch
  • Promise a percentage before measuring
  • Use your data for other clients’ models
  • Send personal data to providers outside the EU

What we need from you

  • Someone who knows the task and validates the cases
  • Real examples: from a few hundred to a few thousand, depending on the task
  • Access to the server or cloud where the model will live
  • A 2-hour session at the start and another at delivery

Frequently asked questions

Do I need to buy a GPU?

Not to start. Fine-tuning a 7–8 billion parameter model with QLoRA fits on a single 24 GB GPU, which can be rented by the hour in an EU cloud. We only recommend buying hardware when usage justifies it.

How much data is needed?

It depends on the task. For format, style or classification a few hundred to a few thousand good examples usually do. For the model to learn new knowledge it takes more, and giving it your documents is often better. Quality matters more than quantity.

Isn’t giving it my documents enough?

Often it is, which is why we measure first. Training pays off for stable, repeated tasks, when your documents alone don’t reach the quality, speed or cost you need.

Does it work in Catalan?

Yes. We compare models with good Catalan, such as Salamandra and ALIA from the Barcelona Supercomputing Center, or Gemma, and evaluate in Catalan on your cases, not on impressions.

What if I already run a model?

That is the best starting point. We measure it as it is, see where it fails and decide whether the fix is in the instructions, the document retrieval or a fine-tune.

Does my data leave the company?

Not unless you want it to. We work on your infrastructure or in an EU cloud, and personal data never goes to providers outside the EU.

Who maintains it afterwards?

You keep the process and the evaluation. If you like, we re-evaluate every month and retrain when your data changes or a better base model comes out.

Let’s measure your case

In a 30-minute call we look at the task you want to solve, the data you have and whether a local model is worth it for you.