Evidence and setup status
Checking evidence and runner readiness.
Active runs
—
syncing
Verified results
—
usable in decisions
Open blockers
—
checking
1
Sign in
Account attached
2
Pair a runner
Local execution ready
3
Choose evidence
Recommendation ready
4
Run or compare
Next action
Recommend
Which setup should I run?
Recent runs
Tracked execution
More tools
Exports and community
Open exports and contributor activity
Download evidence snapshots or inspect community activity.
Top contributors
Community evidence stays cumulative and exportable.
Recommendations
Find the setup to run
Why this answer?Open full comparisonClose comparison
Plot, table, caveats, and next benchmark.
Tradeoffs ready
Open for plot, table, caveats, and next run.
Question and filters
Known-good questions first, with light scope edits.
Download data
Explore
Inspect families, setup matches, and evidence
Historical Results
Recent benchmark evidence
Model
Backend
Use Case
TTFT
Tok/s
Hardware
Capability
Verification
Compare
Choose between families, variants, and quants
Preset views
Start from a useful model-choice stance, then refine the exact variants or inspect individual runs.
Individual run comparison
Result
Result
Family Explorer
Branches, quants, and nearby matches
Download data
Build
Build the next evidence run
Why run this benchmark
Run the benchmark that would change the answer.
Start from Recommend when possible; otherwise choose a model and evidence lane below.
1 Model2 Benchmarks3 Queue
Execute this run
Start a tracked local or cloud run directly from the Hub.
Run locally
Pair a machine once, keep it listening, and queue tracked runs.
No local run has been created for this plan yet.
Start a runner
InferGrade will highlight the one next action that matters for this plan.
Runner recovery commands
Start listener
Use this if the paired app or listener is not running.
Run immediately
Run this once on the current machine.
Run in cloud
Create a managed cloud run when this Hub has a provider configured.
Make this run count as evidence
These steps help the result join the comparable evidence pool instead of staying sample-only.
Use a real run, not a dry run, so timing measurements are recorded.
Keep the artifact pinned so others can reproduce the same bundle.
Let the run finish and upload so its evidence label is applied automatically.
Advanced recovery commands
Preflight only
Check local readiness before starting a run.
Execute only
Run directly if Hub queueing is unavailable.
Upload only
Publish a completed result if automatic upload did not run.
Run plan JSON
Inspect or export the prepared plan.
Run plan
Ready to queue after preparation.
No run plan prepared yet.
Run Status
Active and recent runs
Recent runs
Live timeline
Saved plans
Reusable runs
My Runs
Contributor activity
Recommendation plot
Deployment tradeoff
Sign in to InferGrade Hub
Use a configured hosted OAuth provider, or a dev handle when you are working locally.