Joshua Terranova
Back to highlights

GCSP · Entrepreneurship

BenchHost · Metered Robotics Benchmarking

2026

Server racks with status lights and network cabling in a data center
Photo by Unsplash on Unsplash
GCSP Portfolio

Metered robotics benchmarking so labs can verify shared run certificates without rebuilding GPU workers and billing from scratch.

BenchHost is my Entrepreneurship anchor: hosted metered benchmarking for university robotics labs with deterministic JSON certificates.

Shared discovery tooling dies when every lab rebuilds workers and billing alone. I modeled whether a default run is affordable (~$34.24 for 12 GPU-min at $2.478/GPU-min effective) before chasing live payments.

Journal

What I worked on during 2026. Hover underlined terms for quick definitions.

Scope · Reflective capstone

BenchHost is a GCSP reflective capstone distilled from Module 11benchmark suite economics and shipped-product lessons from KumonScanKumonScan and SpaAIderSpaAIder. Integer-cent pricing, idempotency, certificate verification, and lab-scoped metering are real (32 Vitest tests). Simulated GPU workers, live Stripe, and production Postgres are explicitly out of v1 scope.

Because ClinRad-Bench · Economic access

ClinRad-BenchClinical ML evaluation framework made uncertainty quantification non-negotiable. The next question was cost: shared discovery tooling dies in demos if every lab rebuilds workers, billing, and certificate verification alone.

BenchHost asks whether a university lab can rerun a benchmark and verify the certificate without standing up its own GPU farm. I modeled unit economicsdocs/unit_economics.md: ~$34.24 default 12 GPU-min run, academic subsidy cap per domain before Stripe integration; entrepreneurship evidence is the math and edge cases, not live payment rails in v1.

Build · Certificates and metering

Certificates let a third party recompute run results field-by-field instead of trusting a PDF screenshot. `GET /api/runs/[id]/verify` recomputes deterministically; tamper tests fail as expected.

Optional idempotency_keyDuplicate POST returns the original run without double billing and lab-scoped usage metering prevent the edge cases that kill trust in shared infrastructure.

Handoff · Trust beyond billing

Economic access does not cover procedural trust on a test stand. Rocket Propulsion Laboratory hot-fire work pushed me to HotFire-LedgerChecklist role locks and hash-chained ledger as the multidisciplinary complement.

What I learned

Entrepreneurship evidence for scientific tooling is the unit-economics math and edge cases, not a payment integration checkbox. Shared discovery infrastructure dies if every lab rebuilds workers and verification alone.

Related highlights

All highlights