01Case study · AI

Our own project: software we built and operate ourselves.

TinyServe

A real language model computes answers live in your browser, via WebGPU. On screen you watch the conversation's memory grow (the KV cache grid), which words the model looks at (attention heatmaps), and how a small model prompts the large one (speculative decoding). What usually happens out of sight on a server, you watch here with your own eyes.

Open the live demoGet my free audit
TinyServe: KV cache grid and live visualization of a language model running in the browserLive demo
02Challenge

An LLM is a black box, even for engineers

Teams shipping AI often ask: why does a long prompt compute fast while the answer comes out slowly? Why does graphics card memory run out on a longer conversation? Slide decks and blog-post diagrams do not answer that. TinyServe shows these mechanics live, on a real model, with no server and nothing to install.

03How it works

Four inference mechanics, visible live

Prefill vs decode

The two inference phases rendered separately: why a long prompt computes fast (prefill, parallel) while generating text is slower (decode, one token at a time).

KV cache grid

A 3D grid (layers x heads x positions) that fills in live as tokens are generated: you see exactly how much GPU memory a longer conversation actually costs.

Attention heatmaps

A per-layer, per-head attention heatmap: which earlier tokens the model is actually looking at while generating the next one.

Speculative decoding and paged memory

A small model proposes a token, the large model accepts or rejects it (speedup with no quality loss); separately, a simulation of a block-based memory allocator (like vLLM's) versus contiguous allocation, with an out-of-memory visualization.

04Numbers

A real model, not an animation for show

5

models you switch live (Qwen3 0.6B and 1.7B, Llama 3.2, LFM2.5 1.2B, DeepSeek-R1) and compare their behavior with your own eyes.

570 MB

is the smallest model (Qwen3 0.6B): you run a real language model in the browser with no long wait.

0

server requests during generation: everything runs on your machine, so nothing leaks out.

Check these numbers yourself in the live demo
05Stack

Every choice has a reason

Language
TypeScript, no framework
Vanilla DOM + canvas/WebGL, zero component library
Build
Vite 8
Fast dev server, static production build
Inference
@huggingface/​transformers (WebGPU)
A real language model running on the browser's GPU, WASM as a fallback
Visualizations
three.js + D3
3D KV cache grid, attention heatmaps, memory and throughput charts
06Contact

Got a nagging problem? Describe it, I'll code the rest.

One sentence is enough to start. Tell me what's bothering you. Within 48 hours I come back with a clear answer: can it be done, and at what fixed price.

No obligation: describing your problem costs nothing
Free intro audit: you keep the report either way
Fixed price agreed upfront or we don't start: no surprises on the invoice
A limited number of projects at a time, each with full attention: reach out early if the deadline matters
We reply within 48 hours