Providers / observed usage

What developers used—not a quality score.

A seven-day view of completed UTC days, ranked by observed create volume. Success and latency are descriptive for Wildflower traffic; they are not controlled provider benchmarks.

Snapshot withheld

Not enough verified traffic yet.

The publication pipeline is ready, but showing empty or invented provider rows would be misleading. The first snapshot will appear only after a complete seven-day UTC window contains at least 100 observed create operations and passes the local redaction and denominator checks.

How to read this ranking

01 / rank

Observed create volume

Rank and share use only sandbox create operations observed by Wildflower Computer during the stated window.

02 / outcomes

Descriptive, not causal

Success reflects this traffic mix. It does not control image, region, account configuration, workload, or provider plan.

03 / latency

Successful provider samples

p50 and p95 include only successful creates where provider latency was observed. Missing samples render as an em dash, never zero.

Publication and privacy

The checked-in snapshot can contain only provider-level rank, counts, percentages, latency percentiles, UTC window timestamps, methodology, and source revision. The importer rejects unknown fields and never accepts account, project, request, machine, credential, command, file, path, payload, sandbox, or user identity data.

Pricing and controlled comparisons stay separate

Provider pricing comes from reviewed official pricing sources. Controlled performance comparisons require the same workload, region, benchmark version, time window, and visible sample count. Neither is mixed into this observed usage rank.