daab94134c
Adds the "who turns up around this project" section, split into three lists
because the evidence behind each one is a different strength and collapsing
them into a single logo wall would overclaim.
Contributors 21 companies whose engineers have commits here. Evidence is
the commit history plus the employer on that person's public
GitHub profile, so it is a claim about the person. Commit
counts are shown next to each name, including the ones that
are a single patch, because hiding that would be the whole
problem.
Integrations six projects that reference LocalAI in their own repository
or documentation, which anyone can verify without asking us.
Press four SUSE Communities articles about running LocalAI.
Names are set in type rather than fetched as logos. A logo reads as
endorsement, and a one-line typo fix from somebody who happens to work at a
large company does not support that, quite apart from what their trademark
policy says about it.
ADOPTERS.md is the mechanism for the stronger claim. An organisation that
wants to be listed as a user opens a pull request adding itself, which is both
the evidence and the permission, and is publicly auditable afterwards. The
file says plainly what the website does and does not claim, so the next person
to ask "can we add some big names" has the answer in the repository.
Assisted-by: Claude Code:claude-opus-5 [Bash] [Edit] [Write] [WebSearch]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Co-authored-by: Ettore Di Giacinto <mudler@localai.io>
2.0 KiB
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
- Add a row to the table, in alphabetical order.
- Use your organisation's usual name and a link to your site.
- Say briefly what you use LocalAI for, and whether it is in production.
- 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. We will not ask why.
Who is using LocalAI
| 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.
This file is the third, stronger thing: organisations that chose to say so.