Skip to main content
Make three choices independently:
  1. Workflow: Managed Fine-Tuning or Training API.
  2. Infrastructure: Serverless or dedicated, only when you choose Training API.
  3. Interaction surface: Coding agent, UI, CLI or REST API, or Python SDK.

Step 1: Choose the workflow

Managed Fine-Tuning

Standard jobs with a platform-managed loop.

Training API

Programmable loops built from cookbook recipes or the SDK.

Step 2: If Training API, choose infrastructure

Serverless Training

Shared pooled trainer, no provisioning, per-token billing.

Dedicated Training

Provisioned trainer and deployment resources with explicit lifecycle control.
See the detailed serverless versus dedicated comparison.

Step 3: Choose how to interact

The interface does not determine the workflow or infrastructure: Install the Fireworks training skill to bring your own coding agent.

Examples

Standard SFT from labeled JSONL

  • Workflow: Managed Fine-Tuning
  • Infrastructure: Managed by the platform; no Training API infrastructure choice
  • Interface: Coding agent, UI, CLI, or REST API

First custom GRPO experiment

  • Workflow: Training API
  • Infrastructure: Serverless when the model and LoRA workload are supported
  • Interface: Cookbook through Python or a coding agent

Sustained full-parameter RL

  • Workflow: Training API
  • Infrastructure: Dedicated
  • Interface: Cookbook or direct SDK, optionally orchestrated by a coding agent

Before launch

Verify current model support, shapes, access status, pricing, limits, and quota in the linked live pages. A coding agent asks for confirmation before upload, registration, paid inference, job creation, promotion, deployment, or another mutation. Material changes require approval again; promotion and deployment are confirmed separately.