OpenRouter, concept 2026

Show it, don’t say it.

The hero: Every model. One endpoint., cradled by a ribbon of violet, blue, green and lime that merges into one line in the middle
Role
Design and engineering
Timeline
October 2026
Team
Solo
Status
Unofficial concept
Live
rahazh.com/openrouter

Why

OpenRouter has the numbers. The page should show them.

Hundreds of models, a hundred providers, trillions of tokens a week. I wanted the landing to show that, not just say it.

The hero

A ribbon that is the product.

Many lines come in wide and merge into one in the middle: many models, one endpoint. I tried five placements and kept the first.

The hero: Every model. One endpoint., cradled by a ribbon of violet, blue, green and lime that merges into one line in the middle

The data

Live numbers, read like a benchmark site.

Tokens a week and every model by release date and price, from OpenRouter's own feed. Pick a lab and only its models stay lit.

Four figures, then two charts: tokens a week over the last year, and every model by release date and price

Iteration

The price and policy cards took six rounds.

Logos first, then plain facts. Nobody reads that. Then line art, then speed as bars and policy as where your prompt goes.

An earlier take: the price card as three numbers and the policy card as three rule rows
Plain facts: it read as text.
The final take: speed by provider as a bar chart, and a prompt routed only to the providers that delete it
Where it ended.

Agents

From a list to a wheel.

Three takes, a marquee, then a wheel like Granola's: tiles turning past, one name at a time.

Agents run on OpenRouter: a wheel of agent tiles, one name and its tokens under it

Process

Rules first, then cutting.

I wrote the rules down (one accent, no capitals, nothing under 12px) and checked every change with an audit script. Motion came last: four animations, each with a reason.