Your data and fine-tuning

Fine-tuning on rackAI turns an open model into one that fits your use case, without handing your data to anyone else's model.

At a glance

  • What you get: LoRA and QLoRA fine-tuning on 1 to 8 GPUs, with adapters served beside the base model.
  • What you control: your datasets and adapters stay in your Tenant until you delete them.
  • What never happens: base model weights are never changed, and training jobs never reach the network.

How it works

  1. Upload a dataset to a Tenant. rackAI accepts JSON Lines in chat, ShareGPT, Alpaca or completion format, up to 256 MiB per file. Every line is checked as it arrives. If a line is wrong you'll see which one, and nothing from a rejected upload is kept.
  2. Start a fine-tuning job with LoRA or QLoRA on a model from your catalogue, on 1 to 8 GPUs. Settings you leave unset use sensible defaults, and the job reports every value it used.
  3. Get an adapter. A finished job produces a LoRA adapter: a small set of weights that sits on top of the base model.
  4. Serve it. Add the adapter to a deployment of the same base model. Several adapters can be served beside their base model at once. Call one by name in the model field of your request.

What happens to your training data

Adapters and base weights

Retention and deletion

What fine-tuning costs

During the trial, fine-tuning jobs don't use your trial tokens. Pricing for training is not yet published.

Start building free →How rackAI keeps your data isolated →