Skip to main content
Self-hosting lets you store Brandfetch logos on your own servers, CDN, or devices instead of loading them from Brandfetch’s CDN, for products that can’t hotlink an image from a third party. It’s part of the Enterprise plan, shown as Custom on the pricing page, and it’s set up with the sales team because the files you keep, how you refresh them, and how your product may use them are written into your contract. On every other plan, Logo API images have to be hotlinked, so the <img> tag points at cdn.brandfetch.io and the image is never downloaded, proxied, or re-hosted, as described in Caching.

When to self-host

Hotlinking is the simpler choice whenever it works, because the same URL returns a brand’s new logo when it changes and there’s no copy for you to maintain. Self-hosting is for products where loading an image from Brandfetch isn’t possible or allowed:
  • Privacy or compliance rules forbid requests to third-party domains from your app, which is common in banking and other regulated software.
  • The product works offline, such as a mobile app that shows logos without a connection, or a desktop tool that saves logos inside the files it creates.
  • Logos are served from your own CDN or API, for example in a brand directory, or in data you provide to your own customers.
  • You need the whole dataset at once, rather than one logo at a time as users ask for them.

How it works

Self-hosting follows the same pattern as data ingestion, with a one-time load to fill your storage, followed by updates that keep it current.
1

Agree on the scope

You and the sales team agree on the brands you need, either the full dataset or a defined list, together with the logo formats and types, how long you can keep the files, and where your product will show them.
2

Receive the initial load

Brandfetch delivers the company logo dataset as a bulk file in CSV or JSON, with the logo files it references, to your S3 bucket or SFTP server, or as a secure download.
3

Keep it current

Webhooks notify you when a brand you track changes, with brand.updated for any change to a brand’s data and brand.rebranded when it gets a new logo, so you fetch only the brands that changed instead of pulling the whole dataset again. Brands that are new to your product are looked up through the Brand API, which also has a batch endpoint that takes up to 100 brands in one request.

What’s included

Logos come in the same formats and variants the Logo API and Brand API serve, which are SVG, PNG, WebP, and JPEG files of each brand’s logo, icon, and symbol, in light and dark versions where the brand has them. Your agreement sets which of these you receive, and it can also include the rest of each brand’s data, such as colors, fonts, and company information.

Licensing

Self-hosting comes with custom licensing terms instead of the standard ones, because storing and serving logos goes beyond what the terms of service allow by default. The order form for your plan sets how long you can keep the files, how often you refresh them, where they can appear, and what happens to them when the contract ends, and it takes precedence over the general terms. Enterprise contracts can be flat-fee and multi-year. Brandfetch licenses its data and files to you, but the logos themselves still belong to their brands, so the logo fair use guide applies to a self-hosted logo in the same way as a hotlinked one.

Hotlinked or self-hosted

FAQ

Only with an Enterprise agreement that includes self-hosting. On every other plan, Logo API images must be hotlinked from cdn.brandfetch.io, while Brand API responses and the images they link to can be cached for up to 30 days, as described in Caching.
Yes, the Enterprise plan delivers logos in bulk, as a CSV or JSON file with the logo files it references, to your S3 bucket or SFTP server. You can take the full dataset or a list of the brands you need, and webhooks keep it current afterward.
Subscribe to brand.updated and brand.rebranded webhooks for the brands you store, and fetch a brand again through the Brand API when one arrives. That way you replace only the logos that changed, without pulling the whole dataset again.
That depends on your agreement, because showing logos inside your product and passing them on to your customers are licensed differently. Tell the sales team how your product will use the logos, and the order form will cover it.
Pricing depends on the number of brands, the refresh frequency, and how the logos are used, so it’s quoted by the sales team. Enterprise contracts are billed yearly and can be flat-fee or multi-year.

Get started

Talk to sales

Tell us which brands you need and where your product shows them

Data ingestion

See how the bulk load and webhook updates fit together