Developers

Architecture

A static-first Next.js app, a WebGPU engine in a worker, and one Postgres database.

BROWSERNEXT.JS ON VERCELDATATest pageReact, R3F, ZustandEngine workerWebGPU kernels, timinglocalStorageoperator key, recent runsStatic and ISR pageshome, docs, economyDynamic pagesstack, boards, rewards, runsAPI routesticket, runs, stack, boardsShare imagesnext/og, ArchivoToken registryread every 6 hNeon Postgrespooled connectionspostMessageframe acksfetch
The benchmark runs entirely in the browser. The server validates, stores and ranks.

Browser

Engine
WGSL kernels and robust statistics. Runs in a dedicated worker; falls back to the main thread when the worker has no GPU.
Runner
Hosts the worker, paces rendering against samples, fetches the ticket and submits the result.
State
Zustand stores: bench (run state, samples, result) and viz (what the 3D stack shows). The scene reads viz inside its frame loop, so samples never re-render React.
3D
React Three Fiber. Rendered once per sample during measurement; paused when offscreen.
Identity
A random operator key and recent run ids in localStorage. No cookies.

Server

Static
Home and docs are prerendered. Home reads live totals client-side. Memory Economy regenerates every 6 hours from the token registry.
Dynamic
The Stack, leaderboards, rewards and run pages render per request from an in-process cache.
Cache
Single-flight memo with short TTLs, bounded to 1,000 entries, cleared on this instance after every insert. Route handlers add CDN Cache-Control headers.
Runtime
Node.js on Vercel Fluid compute.