Models that know your business and run where your data lives.
A general model does not know your products, your terms or your exceptions. Onega customises AI to your work in the lightest way that passes your tests: better instructions and retrieval first, fine-tuning when the evidence says it pays, and a smaller model on your own hardware when cost, latency or data demand it.
Each step costs more to build and to maintain than the one before, so we climb only when the evaluation set shows that the previous step is not enough.
01
Instructions and policy
Prompts, output schemas, examples and guardrails tuned to your cases. Quick to change; no training.
02
Retrieval
Answers grounded in your documents and records through embeddings, search and reranking, with sources shown.
03
Fine-tuning
Open-weight models adapted on your approved examples with parameter-efficient methods, for tone, format, classification or domain language.
04
Distillation
A smaller model trained to match a larger one on your task, so it runs on hardware you own at a cost you can plan.
02 — Evaluation first
Nothing ships without an evaluation set.
Before any customisation, we build an evaluation set from your own examples. Every option is scored on it: the base model, the tuned instructions, retrieval and the fine-tuned model. You see the scores, the failures and the cost before you choose.
Test cases drawn from real, approved examples, with a holdout sample nobody tunes on
Scoring rules agreed with the people who do the work
Failure categories recorded, not averaged away
Cost per request and latency measured on your hardware
Regression runs on every model, prompt or data change
03 — Your data
Training data under your control.
Training runs in your environment or on infrastructure you approve. Your data is not sent to a model provider for training unless you decide it should be.
A documented lawful basis and the data owner’s approval before any personal data is used.
Redaction or pseudonymisation of training data where the task allows it.
Every dataset, base model and fine-tuned model recorded with its version and licence, and listed in OneVeer’s AI bill of materials when served there.
Open-weight licences checked against your intended use before training starts.
04 — Serving and customised solutions
Customised, then served behind your policy.
Served by OneVeer
On your hardware, behind an alias.
A fine-tuned or distilled model is packaged as GGUF so OneVeer can serve it on your CPU or GPU behind a published alias. Applications keep calling the alias; returning to the previous model is a configuration change, not a release.
Onega products
Configured to your processes.
OneVeer policies, aliases and guardrails; OneMail categories, routing rules, templates and connectors; OneDesk model providers. Each configuration is tested against your cases before go-live.
Solutions you already own
Tuned and brought under one policy.
AI features in your CRM, service desk or document platform, tuned and evaluated on your cases and, where they allow it, routed through OneVeer for one policy and one audit trail.
05 — How it runs
From evaluation set to a served model.
01
Model Evaluation Sprint · 2–3 weeks
An evaluation set from your examples, baseline scores for candidate models and methods, a data and licence review, a recommendation and a fixed-price proposal.
02
Customise · 3–5 weeks
Instructions, retrieval or training as recommended, in your environment, scored on the holdout sample.
03
Supervised run · 2–3 weeks
The customised model on real work with people reviewing its output, measured against the baseline.
04
Handover
Model card, data record, evaluation results, regression suite, serving configuration and runbook.
06 — FAQ
Questions data and AI teams ask.
Do we need fine-tuning?
Often not. Many tasks are solved by clear instructions, examples and retrieval. We recommend fine-tuning when the evaluation set shows a gap those cannot close, or when a smaller tuned model meets the same bar at lower cost on your own hardware.
Which models can you fine-tune?
Open-weight models whose licences permit your intended use, in sizes that fit your hardware. Hosted models can be customised where the provider offers it and your data policy allows. The licence and its conditions are stated in the assessment.
How much data do we need?
It depends on the task. The Model Evaluation Sprint tells you whether your examples are enough, and of good enough quality, before you pay for any training.
Who owns the fine-tuned model?
Ownership of weights trained on your data is agreed in the statement of work before training starts. The base model’s licence terms always apply as well.