The Yandex Ecosystem Logos — How the Mark System Works

Yandex runs dozens of services — taxi, delivery, music, maps, a marketplace — and every icon reads as "Yandex" at first glance. Behind that sits a system with strict rules: one container, one typeface, a palette assigned per direction. Let's take it apart using the actual files from our catalog.

The core: the letter and the badge

The base mark is the "Yandex" wordmark and the red letter, whose full history we've covered elsewhere. For services the derived element matters more: the "Yandex" badge‑prefix before the product name. It works like a surname — first the shared brand, then the product — and the horizontal lockups show it literally:

The same surname, the same typeface; only the word on the right changes. The same umbrella logic as VK and Sber, but with stricter typographic discipline.

Service icons: one language, different words

But a surname only works where there's room for a word. In an interface the logo shrinks to a 40×40 square with no space for a caption at all — so here the system has to hold together by entirely different means. Look at the icons in a row:

The first thing a closer look reveals: these symbols are of completely different kinds. Go's mark is lettering — the word "Go" itself. Market is a letter too, an "M". From there it turns abstract: a starburst for Music, a spiral for Food, a white silhouette on blue for Lavka, a mathematical plus for Plus. As symbols, they have nothing in common.

And yet the row still reads as one family. So what holds it together isn't symbol similarity but everything around it: the same rounded square, the same stroke weight, the same optical density — plus a strict rule of one symbol per icon. No mark carries two meaningful elements at once, because a second one would destroy legibility at 40 pixels, which is where app icons actually live.

Hence the system's first property, the one it was all built for: the membership layer and the product layer are separated. The container shape says "this is Yandex"; the symbol inside says "this is Music". Change the second and you never touch the first.

Color is the third layer — and it's easy to verify against the files themselves, pulling the palettes straight out of the SVGs:

Red is reserved for the core, yellow for delivery and taxi, and Music goes black with a yellow accent. Each direction receives its shade from above, and product teams simply keep to it — exactly the mechanism logo color psychology describes. Plus falls out of that row with its gradient, and there's a reason: it sells a subscription layered over every service at once, so it has to stand out among its own.

The container that holds the whole system

Since the symbols differ yet the family still reads, that container deserves a closer look — it does most of the work. A rounded square with a fixed radius and fixed inner margins is a blank any new mark can drop into. A product drawn yesterday instantly looks like family because it lands in the same frame as services from a decade ago.

That's why the system scales without convening a design council: the shape rules are already settled, so the only thing left to discuss is the symbol. And it's the cheapest device a small business can steal outright. A shared container — circle, square, badge — plus variable contents inside is a way to assemble a mini identity out of almost nothing, without commissioning a full brand book.

What download statistics show

If the layers really are separated, there should be a measurable consequence: services live in people's heads individually, not as one undifferentiated "Yandex". Our catalog lets us check that — here's how often each ecosystem mark gets downloaded:

People come for a specific service's mark, and the ranking defies expectations. The core leads — Yandex with its 261 downloads, since anyone mentioning the company needs it. Then come the infrastructural products, Maps and Market. The household names, Alice and Go, collect 32 and 14 — several times less.

A mark gets downloaded when the service has to be written about — in an integration, a case study, a comparison table. Maps and Market are embedded into other products and benchmarked constantly, while Alice is more often discussed out loud. Demand for a mark shows how often the brand lands in other people's documents. When downloading, mind the usage rules.

Alice: a mark for something with no shape

Closing that list is Alice, whose mark follows a separate set of rules. A voice assistant has no object you could draw, so the mark went abstract — a white rounded droplet on a violet‑blue gradient. The shape allows several readings at once: a flame, a speech bubble, a drop of sound.

Alice takes her own palette too. The violet‑blue gradient moves her from the ecosystem's service tier into a technological one, toward the same color codes neural network logos run on. A voice assistant counts as technology, and the palette says so before any caption does.

In the horizontal lockup, none of that gradient survives:

An outline and a word remain — the system demands exactly that of every mark. In one color a logo has to work the way it does in full color: on a business card, in a fax, in someone else's black‑and‑white deck. A simple silhouette meets that demand, and for the same reason it animates well into "listening/thinking/answering": there's nothing in it to break in motion.

2021What happened when the center was replaced

Extension tests a system weakly. Replacing its center tests it properly, and Yandex went through that on 31 March 2021, changing its logo for the first time in 13 years. A new mark appeared — the letter "Я" in a red circle — and the search bar stopped echoing the arrow shape the company had used for years. The Cyrillic and Latin spellings were equalized at the same time, so today it's one form in two alphabets:

One typeface, one cap height, the red accent strictly on the first letter — the Latin version works as a second native form of the mark.

The hundreds of service icons stayed as they were: none had to be redrawn. Only the core updated, while the links between it and the services — container, typeface, palette — survived. That's how decoupled layers work in practice: replacing the center triggered no chain reaction at the edges. We cover the same mechanics in the full Yandex logo history and in how careful rebrands work.

What to take from it

So the whole system comes down to one decision made at the very start: split membership and product into separate layers. The container, typeface and palette say "this is Yandex"; the symbol inside says "and this is Music". Everything else follows. A new service ships in a day because the only open question is its symbol. Colors don't collide because the palette is allocated from above. The company logo can be redrawn while Maps and Market stay untouched — they rest on the shared container.

All of it works under one condition: the rules hold without exceptions. That discipline is what people call a visual identity. One considered departure across the whole family, like Alice's gradient, the system absorbs. A dozen decisions of the "we did it our way here" kind will break it.

All Yandex service logos — current and archival variants — are gathered on the ecosystem page and in the catalog: SVG, PNG, brand colors. Compare with other ecosystems: Sber, VK, Google.