# Adopters

Organisations running LocalAI, listed by the people who run it.

If your organisation uses LocalAI and you are happy to say so publicly, open a
pull request adding a row to the table below. That pull request is how we know
we have permission to list you, which is why we do not add anybody ourselves.

You do not need to be a large company, and you do not need to disclose anything
sensitive. A sentence on what you use it for is more useful to other readers
than a logo.

## How to add yourself

1. Add a row to the table, in alphabetical order.
2. Use your organisation's usual name and a link to your site.
3. Say briefly what you use LocalAI for, and whether it is in production.
4. Open the pull request from an account that makes it plausible you speak for
   the organisation, or say in the description who you are. We may ask.

To be removed, open a pull request deleting your row, or email
[info@localai.io](mailto:info@localai.io). We will not ask why.

## Who is using LocalAI

<!-- Keep alphabetical. Columns: Organisation | What for | Status -->

| Organisation | What they use it for | Status |
|---|---|---|
| _Your organisation here_ | | |

## What this list is not

This is not a list of everyone who has ever starred the repository, and it is
not a list of the employers of people who have contributed a patch. Both of
those are easy to scrape and neither means what a logo wall implies.

The website shows two separate things, both of which are checkable without
anybody's permission:

- **Engineers from these companies have contributed code.** Evidence is the
  commit history plus the employer on that person's public GitHub profile. It
  is a claim about a person, not about their employer.
- **These projects integrate LocalAI.** Evidence is a reference to LocalAI in
  that project's own repository or documentation.

Those two lists live in [`website/data/ecosystem.yaml`](website/data/ecosystem.yaml).
This file is the third, stronger thing: organisations that chose to say so.