Browser-first benchmark surfaces for local LLMs
Benchmark local LLMs with a story you can inspect before access opens.Quantified.
LocalBench is building a browser-first benchmark harness for Ollama and LM Studio that favors explicit diagnostics, reviewable methodology, and honest trust boundaries over vague screenshots or leaderboard theater.
Browser-first measurement
The benchmark runs through the browser against a localhost runtime on this machine, so the trust boundary stays visible instead of hidden behind a remote service.
Separated confidence paths
Standard and YOLO runs stay clearly separated so exploratory data can exist without quietly borrowing the credibility of controlled benchmark runs.
Inspectable outputs
Results, methodology notes, consent language, and launch constraints are all visible so visitors can judge the benchmark story before the gate opens wider.
Verified performance intelligence
Mirror the real launch shape, not a generic SaaS pitch.
LocalBench is in V0-alpha. The public site is for inspection first: visitors can review the benchmark story, legal posture, and waitlist before broader access opens.
LocalBench public shell
Browser-first review set
Public pages
Open for review
Benchmark access
Admin-gated
Alpha path
Waitlist + notification
Public routes
Headless profiling.
The roadmap still includes optional CLI tooling for repeatable, low-friction runs in labs and automation contexts. The public shell keeps that future visible without pretending it is the current product.
Roadmap step 1
Inspect the benchmark story
Public pages explain the methodology, trust model, legal posture, and current launch limits before anyone is asked to trust the product.
Roadmap step 2
Join the narrow alpha queue
Interested visitors can leave an email address for alpha notifications without creating a public account or implying immediate access.
Roadmap step 3
Open access deliberately
Broader testing should follow only after the benchmark flow, consent language, and release posture are credible enough to support it.
Alpha notifications
Put your email on the waitlist for controlled alpha access.
Join the alpha waitlist if you want a notification when broader access opens. We store the address only for that purpose and handle removal or correction requests manually.
Storage
Email and consent are stored in Postgres.
Use
Alpha notification only, not general marketing.
Control
Removal or correction requests go through contact.
We only use this email for alpha-access notifications.