Why Every Service Has a Logo: Our Logo.dev Partnership

Little details compound. Real logos on every vault entry are one of them.

The design bet

A vault of text rows looks like a spreadsheet. A vault with recognizable service logos looks like the services themselves. That change alone makes the vault easier to scan by an order of magnitude.

Why Logo.dev

Because building and maintaining our own logo catalog is a full-time job we'd rather not do. Logo.dev has a licensed, up-to-date, high-quality catalog and a friendly API. We pay them so you don't have to think about it.

The attribution page

Legally we're required to credit Logo.dev. Practically we want to — they built the thing we're using. The /attribution page keeps the credit clean and out of the way.

How lookup works

When you add a service to the vault, we look up the service by domain in our internal catalog, which maps to a Logo.dev URL. If the service isn't in our catalog, the entry gets a generic placeholder.

Caching and performance

Logos are cached aggressively (browser + CDN). A returning visitor never re-fetches the same logo. Even on first paint, they arrive quickly because they're small SVGs.

What we don't do with logos

We don't modify them, don't tint them, don't crop them beyond safe boundaries. Brand guidelines matter.

Coverage

Our current catalog is about 230 major services. If yours isn't there, tell us and we'll add it.

Removing logos from marketing

You'll notice the public marketing pages don't lean on partner logos. That's deliberate — we don't want to imply endorsement by any service.

A worked example

A vault of 40 entries with logos scans in three seconds. The same vault without logos takes three times as long to eye-scan. Small change, big effect.

Wrap it up

The logo integration is the kind of detail that seems trivial until you turn it off. Then you realize how much of the interface was doing quiet work.