feat(website): add an ecosystem band, and an ADOPTERS file to back it - #11248
Merged
Conversation
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.
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Assisted-by: Claude Code:claude-opus-5 [Bash] [Edit] [Write] [WebSearch]
localai-bot
added
the
kind/documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the "who turns up around this project" section to the landing page, plus
ADOPTERS.md.Three lists, not one logo wall
The evidence behind each claim is a different strength, so they are kept apart:
Engineers from these companies have put code in. 21 companies, from the commit history joined against the employer on each contributor's public GitHub profile. Microsoft (20 commits, 3 people), Spectro Cloud (11, 3 people, also a sponsor), VictoriaMetrics, Acronis, BearingPoint, Zendesk, Nextcloud, Scaleway, Kubermatic, Avanade, IBM, Ableton, Atlassian, TikTok, CockroachDB, MediaTek, Samsung SDS, Ant Group, Deloitte, solo.io, Qonto. Plus researchers at MIT, Edinburgh, RMIT, RIT, Miami and USC.
The commit count is shown beside every name, including the ones that are a single patch. That is deliberate: it is a claim about a person who works somewhere, not about their employer adopting anything, and the number keeps it honest.
These projects integrate LocalAI. AnythingLLM, langchain4j, LangChain, Flowise, AIKit and Kairos. Each references LocalAI in its own repository or documentation, verified with a code search, so any reader can check it without taking our word for it.
Written about elsewhere. Four SUSE Communities articles, the first by Christian Huller in November 2025.
Why names and not logos
A logo is the visual grammar of endorsement. A one-line typo fix from somebody who happens to work at a large company does not support that, and several of the trademark policies involved explicitly prohibit use that suggests affiliation. Names set in the site's own type carry the same information, match the design, and raise no question.
Logos would be defensible on the integrations row, since that is a fact about their product, and they are entirely fine for anyone who adds themselves to
ADOPTERS.md.ADOPTERS.md
The standard mechanism, as used by Kubernetes, Prometheus and Envoy: an organisation that wants to be listed opens a pull request adding itself. The PR is the evidence and the permission at once, and it stays auditable. The file also states plainly what the site does and does not claim, so the next person who asks about adding big names finds the answer in the repository.
Data
website/data/ecosystem.yamlholds all three lists with a comment explaining the evidence standard for each. Refreshing the band later is a data edit, not a template edit.Verification
Site builds clean. No em dashes. Band was rendered and reviewed in a browser at desktop width.