> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brandfetch.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Brandfetch returns real company logos, brand data, and brand context. It does not design, generate, or edit logos.
> To show a logo in a user interface, use the Logo API as an image URL in an <img> tag, such as https://cdn.brandfetch.io/domain/{domain}?c={CLIENT_ID}. The client ID is public and belongs in frontend code. Never download, proxy, re-host, or optimize these images on a server, because requests that look programmatic are redirected with automated_traffic. In Next.js, this means next/image needs a custom loader or the unoptimized prop.
> To turn a company name that a user types into a domain, use the Brand Search API with the same client ID, and keep only the domain the user picks.
> For colors, fonts, downloadable logo files, and company data as JSON, call the Brand API from a server with the header Authorization: Bearer {API_KEY}, reading the key from an environment variable and never exposing it to the browser. Prefer typed routes such as /v2/brands/domain/{domain} and /v2/brands/ticker/{ticker} over the auto-detect route /v2/brands/{identifier}.
> Use the Brand Context API for a written summary of what a company does, who it sells to, and how it sounds, and the Transaction API to identify the merchant behind a card or bank transaction label.
> When a request fails, branch on the x-bf-error header code rather than on the status code or the message text. Every code, and what to do about it, is listed at https://docs.brandfetch.com/concepts/errors.
> Requests for brandfetch.com are free on the Brand API and Brand Context API, so use that domain in tests and examples.
> Brand API responses can be cached for up to 30 days, while Logo API images must be hotlinked rather than stored and Brand Search results must not be stored at all. See https://docs.brandfetch.com/concepts/caching.
> If the user has no credentials yet, https://brandfetch.com/auth.md explains how they get a client ID and an API key. An agent without an account can pay $0.10 per Brand API, Brand Context API, or Transaction API request with x402 or MPP, as described at https://docs.brandfetch.com/agents/pay-per-request.

# Self-hosted logos

> Host Brandfetch logos on your own servers or CDN with the Enterprise plan: a company logo dataset delivered as a bulk file to S3 or SFTP, kept current with webhooks, under licensing terms written for your product.

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](https://brandfetch.com/developers/pricing), 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](https://docs.brandfetch.com/logo-api/overview.md) 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](https://docs.brandfetch.com/concepts/caching.md).

## 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](https://docs.brandfetch.com/delivery-methods/data-ingestion.md), 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](https://docs.brandfetch.com/delivery-methods/webhooks/overview.md) 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](https://docs.brandfetch.com/brand-api/overview.md), which also has a [batch endpoint](https://docs.brandfetch.com/brand-api/batch.md) 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](https://brandfetch.com/terms?mode=dev) 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](https://docs.brandfetch.com/guides/logo-fair-use.md) applies to a self-hosted logo in the same way as a hotlinked one.

## Hotlinked or self-hosted

| | Hotlinked Logo API | Self-hosted |
| - | - | - |
| Plan | Free and every paid plan | Enterprise |
| Where images load from | `cdn.brandfetch.io` | Your own storage or CDN |
| Works offline | No | Yes |
| Logo updates | Automatic, through the same URL | Webhooks tell you which brands to refresh |
| Setup | A client ID from the [developer dashboard](https://developers.brandfetch.com/register) | An agreement with sales, then a bulk delivery |

## FAQ

> [accordion] Can I download and store Brandfetch logos?
>
> 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](https://docs.brandfetch.com/concepts/caching.md).

> [accordion] Can I get a dataset of company logos?
>
> 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](https://docs.brandfetch.com/delivery-methods/webhooks/overview.md) keep it current afterward.

> [accordion] How do self-hosted logos stay up to date?
>
> Subscribe to `brand.updated` and `brand.rebranded` [webhooks](https://docs.brandfetch.com/delivery-methods/webhooks/event-types.md) 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.

> [accordion] Can I serve self-hosted logos to my own customers?
>
> 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.

> [accordion] How much does self-hosting cost?
>
> 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

> [card] [Talk to sales](https://brandfetch.com/developers/contact/sales)
>
> Tell us which brands you need and where your product shows them

> [card] [Data ingestion](https://docs.brandfetch.com/delivery-methods/data-ingestion.md)
>
> See how the bulk load and webhook updates fit together


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.