- No infrastructure: Train frontier models without managing GPUs or RL infra
- Production-ready: Built-in tracing, monitoring, security & one-click deploy
- Fast iteration: From evaluator setup to deployed model in hours, not weeks
Quickstart: pick your training approach
Single-Turn Training
15 minutes — test locally with a simple evaluator and small model.
Remote Agents
1–2 hours — multi-turn rollouts in your environment with HTTP tracing.
Training security (BYOB)
2–4 hours — datasets stay in your GCS/S3 bucket.
How RFT works
In supervised fine-tuning you provide labeled examples of good outputs. In RFT you provide prompts and an evaluator (reward function) that scores model outputs from 0 to 1. Training iteratively improves outputs that maximize that score.1
Design an evaluator
Define how to score outputs (rules, tests, LLM-as-judge, or hybrid).
2
Prepare a dataset
JSONL with prompts (
messages array). Ground-truth completions are optional.3
Connect your agent (optional)
Local evaluators for simple tasks, or remote environments for agents.
4
Launch training
Fireworks UI,
firectl rftj, or eval-protocol CLI.5
Deploy
Promote the checkpoint and deploy LoRA on on-demand hardware.
Launch and operate
Use the docs for path choice and quickstarts. Use the Fireworks training skill for launch flags, validation, monitoring, and troubleshooting.Prerequisites
Confirm account access and quota, an RFT-compatible base model, valid prompt JSONL, and a reviewed evaluator that produces non-flat scores on a small probe.Evaluators
Evaluators turn a rollout into a reward. Test full-credit, partial-credit, zero, malformed-output, and edge cases locally before registration. Keep evaluator and preference-data guidance in the evaluator skill reference.Parameter tuning
Resolve the current defaults fromfirectl rftj create --help and the live RFT parameter reference. Start with a small run, change one optimization or rollout variable at a time, and compare reward and held-out quality.
Weighted training
Use per-example or per-token weighting only when the selected managed contract supports it. Inspect the rendered samples and effective loss mask before launch.Launch from the CLI
Usefirectl rftj create for a reproducible managed job. Prepare the full base-model, dataset, evaluator, and output-model resource names, run the documented preflight, and confirm the resolved plan before creation.
Launch from the dashboard
Use the dashboard for a guided first run: choose the model, dataset, evaluator, rollout settings, and optional W&B project, then review the summary before launch.Warm start
Warm-start from a compatible promoted LoRA when continuing SFT into RFT. Do not also supply a conflicting base-model field; verify the current CLI contract before creation.Evaluator secrets
Store credentials in the Fireworks secret-management surface and reference them by environment-variable name. Never embed secret values in evaluator code, datasets, or run reports.Cost planning
Estimate rollout inference, training runtime or tokens, candidate count, response length, and any deployment uptime. Use the live pricing page and Price vs Tinker; do not assume a free tier.Monitor training
Track state plus actual progress: optimizer steps, rollout throughput, reward distribution, validation results, logs, and W&B metrics when enabled. Inspect representative rollouts for reward hacking and stop when quality regresses or the evaluator saturates.Using Cursor, Claude Code, or Codex? Install Agent Skills to drive managed RFT with the
fireworks-training skill.Related
Remote Environment Setup
HTTP
/init contract for remote rolloutsPrice vs Tinker
Multi-turn RL cost comparison
Training API RL
Custom RL loops on dedicated or serverless infrastructure
Models
Which models support managed RFT