flash CLI. The same account has an org-scoped web
dashboard at platform.freesolo.co. Product
updates are published in the changelog.
Projects
The dashboard groups work into org-level projects: training runs, published environments, and recorded traces are organized by project, and the navigation is scoped to the project you have open. A project selector in the top bar switches between projects from anywhere in the dashboard. A new organization starts with a project calledExample, holding a starter
environment and one example trace, so the shape of the workflow is visible
before you train anything. The environment is published to your org’s Hub
namespace moments after the org is created, so it is briefly pending on a brand
new org. It is an ordinary project: nothing selects it implicitly, and it
carries no special protection, so you can rename or delete it like any other.
Every project-scoped operation names its project explicitly. There is no
default, no fallback, and no implicit selection: flash env push and
flash env delete take a required --project, a
training config sets a required top-level
project field, and trace recording requires an explicit
project id. A missing, malformed, or inaccessible project fails the command
rather than picking one for you, so a run can never land in a project you did
not name. Create projects in the dashboard or with
flash projects create, and list the ones you can
reach with flash projects list.
API keys
Commands that contact Freesolo authenticate with a Freesolo API key. Create and revoke keys in API Keys. Keys are org-wide; any org member can manage them. A new key is shown once. Use it withflash login --api-key <key> or the
FREESOLO_API_KEY environment variable. See
Quickstart.
Training runs
Training Runs lists the runs submitted withflash train. Filter by status; columns cover state,
model, environment, and cost. Open a run for the same detail exposed by
flash runs status: its configuration, checkpoints, deployment details, error
state, and current or final cost record. For GRPO and OPD runs, the run page
also shows a sampled completions panel: per training step it surfaces
example prompts and the completions the model generated, each tagged with its
GRPO reward or OPD distillation loss, so you can watch what the model produces
as it trains.
Checkpoints
A run detail page lists its deployable checkpoints: the per-step adapters available to serve, including intermediate checkpoints from a run that stopped mid-training. This is the same set you get fromflash runs checkpoint <run-id>; deploy one with
flash models deploy <run-id>/step-<N>. See
Deploy a specific checkpoint.
Environments
Environments lists the private Hub environments you publish withflash env push. A managed environment id is
namespace/name, where namespace is your org slug. The page tracks publish
time, last use, and run count. From it you can inspect, pull, or delete
environment source.
Traces
Each project has a Traces tab for the LLM calls your app records through Freesolo’s recording endpoint, with a per-trace detail view and project aggregates: score, pass rate, p50 latency, average output tokens and LLM calls per trace, and error rate. Select traces to export them as a dataset you can train on; see View traces in the dashboard for how that compares withflash traces export.
Models
Models lists the org’s deployed LoRA adapters from managed serving. Each deployed run appears as one stable run-alias row, not separate rows for immutable revisions. It shows the adapter id, base model, serving URL, latest reward when the adapter came from a Flash run, per-token billing, and serving status. The alias routes only to a revision that passed deployment verification, while older immutable revisions can remain directly callable. Rows that still have a matching Flash run link back to the run detail page. Open a model for its deployment detail, where you can start and tear down serving without switching to the CLI. Deploying from the dashboard runs the same verification asflash models deploy: the run alias
begins routing only once the new revision answers a smoke request, and
undeploying stops further requests to that adapter, and with them the per-token
charges. A deployed adapter you send no requests to costs nothing.
Model access is org-scoped: the serving endpoint authorizes external chat
requests against the org that owns the adapter.
Billing
Flash is prepaid. Billing settings show the org balance, activity, payment method state, manual top-ups, and auto-top-up configuration. Any org member can view the summary; owners and Freesolo team members manage payment methods and top-ups. Starter credit comes in two tiers, $60 in total, each claimed once from billing settings: $10 with no payment method at all, and a further $50 once a card is on file. Adding a card does not credit your balance on its own. Manual top-ups range from $50 to $10,000. The activity log itemizes:- Training runs, charged after successful completion at the Flash cost quote. Setup time is reported but not billed. A cancelled run is prorated from its accepted quote by the share of the work it completed, capped at that quote.
- Serving usage, charged per token.