Your own AI model with LoRA fine-tuning, from Barcelona
A model that speaks like your business: your jargon, your formats and your tasks. We build the dataset, train the model and measure whether it really improves.
LoRA fine-tuning adapts an open model to your business (vocabulary, format, tasks) and leaves it running on your hardware. For organisations with highly specific knowledge and good-quality examples. It takes 4 to 8 weeks, with your own dataset, training and before-and-after evaluation, and the resulting model is yours.
Businesses with their own technical vocabulary that generic models don’t handle well
Educational and publishing projects that want an assistant with their own method and tone
Teams that repeat a task with a fixed format: data sheets, reports or classifications
Anyone who already has a RAG and needs more precise answers in their own style
What is included
Preliminary study: we check whether fine-tuning is needed or whether RAG and good instructions are enough
Design and creation of the dataset from your documents and examples
Generation of synthetic examples with a local model, validated by your team
A simple tool for your team to review and correct examples
LoRA training with Unsloth or Axolotl on a local GPU
Evaluation with reference questions: base model versus fine-tuned model
Merging, quantisation and deployment on your AI server
What you get
Your own documented dataset, in a standard format and owned by you
Fine-tuned model (LoRA adapter and merged version) ready to serve
Evaluation report with metrics and before-and-after examples
Reproducible recipe for retraining with new data
The problem: the model doesn’t speak like your business
Generic models know a little about everything, but they fail exactly where your business is different: your sector’s terminology, the exact format of your reports, the method you use to explain things, the tone you take with your clients. It can be corrected with long instructions and a private RAG search, and often that is enough. When it isn’t, the solution is to teach the model with examples: fine-tuning.
Doing it in the cloud means uploading your best examples to a third party, and those are usually your most valuable knowledge and often contain personal data subject to the GDPR or information under professional secrecy. With LoRA, training can be done on your own hardware: the dataset and the resulting model stay in-house, and the model then runs on your server without paying per token.
How we do it, step by step
Needs test. We measure the base model with your real questions. If RAG and good instructions are enough, we stop here and you save yourself the rest.
Dataset design. We decide which kinds of examples it needs: direct answers, step-by-step reasoning, multi-turn conversations and trick cases it should know how to reject.
Creation and validation. We start from your documents, generate synthetic examples with a local model and your team reviews them in a simple tool.
LoRA training on a local GPU, with several parameter trials.
Honest evaluation: the fine-tuned model against the base model, with the same questions and the criteria we agreed at the start.
Deployment on your server, merged and quantised so it runs fast.
The technology, in plain words
LoRA: instead of retraining the whole model, you train a small layer of adjustments, an “adapter”. It is much cheaper, fits on an office GPU or a DGX Spark and can be switched on or off.
Unsloth and Axolotl: open tools for training LoRA adapters efficiently.
Datasets in standard formats (ChatML, ShareGPT), so you don’t depend on us or on any platform.
Quantisation and serving with vLLM or llama.cpp, connected to your LiteLLM gateway as just another model.
When we DON’T recommend it
If what you want is for the model to “know” your data, such as your catalogue, your clients or regulations that change, fine-tuning isn’t the right tool: it forgets them, mixes them up and goes out of date. That’s what RAG is for. Nor do we recommend it if there are no good-quality examples and nobody to validate them, or if a commercial cloud model already does the task well and your data isn’t sensitive. For most businesses we see in Barcelona, fine-tuning is the second step, not the first.
We use it every day
For Nuzic, an educational music and mathematics project from Barcelona, we built the dataset factory (examples with reasoning, trick questions that contrast with classical music theory and multi-turn conversations, in three different tones), a curation website where the team validates each example, and the LoRA fine-tuning of a custom model. That’s why we know the real work is in the data, and that’s where we put the effort.
A field agent that speaks Catalan, knows your farm and keeps the logbook for you.
Voice field logbook
Local weather and history
Pests and diseases from photos
Learn more →
Frequently asked questions
What hardware do I need to train the model?
Less than you might think: with LoRA, training fits on an office GPU or a DGX Spark, and the fine-tuned model is then served on your server like any other. The real work is in preparing a good dataset. We work from Barcelona, remotely or at your office.
What is the difference between fine-tuning and RAG?
RAG gives the model up-to-date information with every question; fine-tuning teaches it how to answer: style, format, vocabulary and typical reasoning. For data that changes, RAG; for behaviour, fine-tuning. Often the best option is to combine them.
How much data do I need?
Usually, from a few hundred good examples for a specific task. If you don’t have them, we generate them from your documents and your team validates them; quality matters more than quantity.
Who owns the resulting model?
You do. The dataset, the LoRA adapter and the merged model stay on your server. Before we start, we check the base model’s licence with you to make sure it allows the commercial use you need.
Free assessment
LoRA fine-tuning adapts an open model to your business (vocabulary, format, tasks) and leaves it running on your hardware. For organisations with highly specific knowledge and good-quality examples. It takes 4 to 8 weeks, with your own dataset, training and before-and-after evaluation, and the resulting model is yours.