Platform dashboard

Flash runs from the flash CLI, and the same account has an org-scoped web dashboard at freesolo.co/platform. After sign-in, /platform redirects you to your active org at /{org-slug}/platform. The dashboard mirrors the operational state behind the CLI: training runs, published environments, deployed models, billing, and API keys.

​

API keys

Every flash command authenticates with a Freesolo API key. Create and revoke keys in API Keys. Keys are org-wide, any org member can manage them, and a new key is shown once. Use it with flash login --api-key <key> or the FREESOLO_API_KEY environment variable. See Quickstart. API keys start with fslo_; Freesolo stores only hashed key material plus the prefix/last-four display fields, so the full key cannot be recovered later.

​

Training runs

Training Runs lists the runs submitted with flash train, with status filters and columns for state, model, environment, and cost. Open a run for the same detail exposed by flash status: the run spec, checkpoints, artifact/deployment metadata, error state, and current or final cost record.

​

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 from flash checkpoints <run-id>; deploy one with flash deploy <run-id>/step-<N>. See Deploy a specific checkpoint.

​

Environments

Environments lists the private Hub environments you publish with flash 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, and lets you inspect, pull, or delete environment source.

​

Models

Models lists the org’s deployed LoRA adapters from managed serving. 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. Rows that still have a matching Flash run link back to the run detail page. 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. New orgs can claim a one-time $50 starter credit after a card is on file. 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. Cancelled runs are repriced to the training steps they reached.
• Serving usage, charged per token.

​

Freesolo agent CLI

The freesolo command handles repo-level Freesolo agent workflows. Install it with pip install freesolo-agent, then run freesolo setup to connect a Freesolo API key, choose an operation (draft, optimize, training, or poll), and submit or follow a repository-agent job. Use flash for managed model post-training and serving.