Skip to main content

​
Pricing

Prime Traces is priced by data volume: One GiB is 1,073,741,824 bytes. Ingestion is charged when data is ingested; storage depends on the volume retained over time. For illustration, ingesting 10 GiB and retaining it for approximately one month costs approximately $11: $10 ingestion and $1 storage. Trace charges are separate from training, inference, and other platform usage. Exporting legacy samples is free, but data subsequently uploaded to Prime Traces incurs the rates above.

​
Control run uploads

Prime Traces is enabled by default. Traces uploaded by platform runs incur ingestion and storage charges. To disable uploads for a workspace:
  1. Select the appropriate personal or team workspace.
  2. Open Billing → Usage Limits.
  3. Disable Upload runs to Prime Traces.
Turning off uploads does not delete stored traces. Existing traces remain viewable in the dashboard; account-level opt-out also disables trace reads through the SDK and CLI. See Viewing and deleting traces to manage existing data.

​
Opt out for a run or client

The controls below are documented in the Prime Runs SDK at CLI release v0.9.4. Update older installations before using them; separately installed SDKs must also include these controls. For a single run, pass traces_opt_out=True to your existing prime_runs.init(...) call. For a shell or job:
For runs using this machine’s Prime configuration:
Client setting precedence is: explicit init() argument, then PRIME_TRACES_OPT_OUT, then the config file. These client controls do not override an account-level opt-out. They control Prime Runs routing; they are not a substitute for workspace permissions on standalone Traces API requests. Opted-out runs use legacy sample storage while that service remains available. This is a temporary compatibility path, not permanent free trace storage. See the November 6 retirement and export instructions. To allow uploads again, enable them for the workspace and remove or set to false any applicable client opt-out. Change the setting before starting the run.

​
Usage limits

Check the selected workspace’s Usage Limits when an upload fails because storage is over its limit. Verify the workspace first, then review its configured limit and stored data. See deletion and quota troubleshooting. A usage limit and a pricing rate are different: the limit controls available capacity; the rates above determine charges for accepted usage.