Skip to content
Ricklayer
RUEN
← All work

02 · EloStore ecosystem

EloStore

A CS2 boosting marketplace

14 days from the decision to launch. We turned a boosting service into a marketplace: a client posts a request for free, boosters offer their own price and timeline, and the money waits with the platform until the result. Written from scratch: 136,322 lines of code and 1,021 automated tests.

How an order goes

The client posts a request, boosters respond with a price and a deadline, the client picks one and pays. The money waits with the platform until the client accepts the result.

The animation from the elostore.ru home page

Try it yourself

Price a boost in the EloStore calculator and post the order: then boosters respond, you choose, and the money waits with the platform until the result.

The real EloStore calculator and scenes with elostore.ru prices. Nothing is actually ordered

What a screen is made of

The EloStore interface is built from shared tokens: colors, corner radii, the typeface. Every element takes them from one place, so the screens read as one system, and a section for a new game is built from the same parts.

Real EloStore components, nicknames and prices are made up

Boosters on the storefront

Every booster has their own card on the homepage: an agent render, FACEIT level 10 and ELO. The service's team moved to the marketplace in full.

Renders from elostore.ru: made from our prompts on our 3D work and our model

0

boosters moved to the marketplace without signing up again

0

received the LEGEND mark for working with EloStore before the marketplace

Stack

Next.js 15 · React 19 · TypeScript strict · Tailwind v4 · Drizzle ORM · PostgreSQL · Zod · Pino · Vitest · Playwright · Telegram Bot API · Claude Haiku · nginx · systemd