Fine-Tune
Start from an open-weight base and train on prompts, completions, or conversation logs. Freuron runs versioned jobs on managed GPUs — typically within hours — so you ship a model fitted to your workload, not a shared generalist.
Turn production traffic into a dedicated open-weight model — trained, evaluated, and served on a private endpoint. Freuron keeps the loop running as new data arrives, so quality compounds without you owning the ML stack.
Freuron is the infrastructure underneath production open-weight systems — managed training, private inference, evaluation-gated cutovers, and traffic-driven retrain on serverless GPUs that scale to zero.
Start from an open-weight base and train on prompts, completions, or conversation logs. Freuron runs versioned jobs on managed GPUs — typically within hours — so you ship a model fitted to your workload, not a shared generalist.
Promote a validated version to a private, single-tenant endpoint via POST /api/v1/inference/chat. Cold start, scale-to-zero, and per-token billing are handled by the platform — no cluster to keep warm.
Production traffic and feedback feed the next training loop. Retrain on a schedule or threshold, evaluate the candidate, then switch the live endpoint — or roll back in one call. The MLOps loop stays on Freuron.
General-purpose endpoints are built for broad consumption and are typically over-provisioned for specific workloads. Freuron fine-tunes a smaller open-weight base on your data and serves it from a private, single-tenant endpoint — lower per-call cost, tighter latency for the target workload, and isolated customer data.
Connect Langfuse, Helicone, or OpenTelemetry in read-only mode. Freuron reviews cost, latency, and volume, then highlights the workloads that justify an open-weight fine-tune and private endpoint.
Private inference, evaluation-gated cutovers, persistent memory, web search, and traffic-driven retrain ship with the platform — not as separate tools you have to wire yourself.
Submit JSON or JSONL prompt-completion datasets, including MongoDB Q→A imports. Freuron provisions compute, runs training on open-weight bases, and exposes a versioned model — without you managing GPUs or training scripts.
Deployed models land on serverless GPUs behind POST /api/v1/inference/chat. Same messages / choices shape as OpenAI chat completions — swap URL and key, nest generation params, and you are on Freuron.
Training completes into a candidate version. Quality gates and eval loss surface before the live endpoint switches, so deploy is a deliberate promotion — not an accidental overwrite.
Pass a user id and Freuron keeps cross-session context — preferences, tone, prior interactions — scoped per end user. No separate vector database to operate alongside inference.
Toggle live web search per model. Results fold into replies with inline citations — useful grounding without a custom retrieval pipeline.
New production data triggers automatic retraining. When a run passes evaluation, the platform can switch the live endpoint to the new version. Roll back to a prior version in one call when needed.
The path runs over HTTP. Freuron handles validation, training, evaluation-gated version switches, and serving — you do not provision or operate ML infrastructure.
POST a JSON or JSONL file of prompts and completions. Freuron validates the schema, deduplicates rows, and stages the dataset for fine-tuning.
Submit a fine-tune request on the model. The platform schedules training on managed GPUs, executes the run, and streams progress through the API.
When training completes, inspect the candidate and promote it when ready. Retrain on fresh production data later, or roll back the live model — each via a single POST. Freuron handles the active endpoint transition.
POST /api/v1/inference/chat with an Inference key and the familiar messages payload. Response content lands at choices[0].message.content. The platform serves the request, scales to zero between calls, and bills per token.
A single POST with an Inference key and the OpenAI-familiar messages / choices shape. Swap URL and key, nest generation params — memory, web search, and per-end-user identity are optional request fields.
access