|
| 1 | +# Who shows up around LocalAI, and the evidence for each claim. |
| 2 | +# |
| 3 | +# Three lists, three different strengths of evidence. Keep them separate: a |
| 4 | +# person fixing a typo is not their employer adopting the project, and saying |
| 5 | +# so invites a takedown request. |
| 6 | +# |
| 7 | +# contributors someone with commits in this repository whose public GitHub |
| 8 | +# profile names that employer. Evidence is the commit history |
| 9 | +# plus a self-declared field, so the claim is about the person. |
| 10 | +# integrations the other project's own repository or documentation |
| 11 | +# references LocalAI. Checkable by anyone, needs no permission. |
| 12 | +# press somebody else published a piece about LocalAI. |
| 13 | +# |
| 14 | +# Companies that want to say they use LocalAI add themselves to ADOPTERS.md at |
| 15 | +# the repository root. That pull request is the permission, which is why the |
| 16 | +# adopters list is kept apart from this file. |
| 17 | +# |
| 18 | +# Refreshed on 2026-07-31. Contribution counts are from the GitHub API. |
| 19 | + |
| 20 | +contributors: |
| 21 | + note: "Engineers whose public profile names these employers have commits in the repository." |
| 22 | + companies: |
| 23 | + - { name: "Microsoft", people: 3, commits: 20 } |
| 24 | + - { name: "Spectro Cloud", people: 3, commits: 11 } |
| 25 | + - { name: "VictoriaMetrics", people: 1, commits: 5 } |
| 26 | + - { name: "Acronis", people: 1, commits: 5 } |
| 27 | + - { name: "BearingPoint", people: 1, commits: 4 } |
| 28 | + - { name: "Zendesk", people: 1, commits: 3 } |
| 29 | + - { name: "Nextcloud", people: 1, commits: 2 } |
| 30 | + - { name: "Scaleway", people: 1, commits: 2 } |
| 31 | + - { name: "Kubermatic", people: 1, commits: 2 } |
| 32 | + - { name: "Avanade", people: 1, commits: 2 } |
| 33 | + - { name: "IBM", people: 1, commits: 1 } |
| 34 | + - { name: "Ableton", people: 1, commits: 1 } |
| 35 | + - { name: "Atlassian", people: 1, commits: 1 } |
| 36 | + - { name: "TikTok", people: 1, commits: 1 } |
| 37 | + - { name: "CockroachDB", people: 1, commits: 1 } |
| 38 | + - { name: "MediaTek", people: 1, commits: 1 } |
| 39 | + - { name: "Samsung SDS", people: 1, commits: 1 } |
| 40 | + - { name: "Ant Group", people: 1, commits: 1 } |
| 41 | + - { name: "Deloitte", people: 1, commits: 1 } |
| 42 | + - { name: "solo.io", people: 1, commits: 1 } |
| 43 | + - { name: "Qonto", people: 1, commits: 1 } |
| 44 | + academia: |
| 45 | + - MIT |
| 46 | + - University of Edinburgh |
| 47 | + - RMIT |
| 48 | + - Rochester Institute of Technology |
| 49 | + - University of Miami |
| 50 | + - USC |
| 51 | + |
| 52 | +integrations: |
| 53 | + note: "These projects reference LocalAI in their own repository or documentation." |
| 54 | + projects: |
| 55 | + - name: AnythingLLM |
| 56 | + by: Mintplex Labs |
| 57 | + url: https://github.com/Mintplex-Labs/anything-llm |
| 58 | + what: "Runs LocalAI as a model provider for its chat and document workspaces." |
| 59 | + - name: langchain4j |
| 60 | + url: https://github.com/langchain4j/langchain4j |
| 61 | + what: "Ships a LocalAI module, so JVM applications can target it directly." |
| 62 | + - name: LangChain |
| 63 | + url: https://python.langchain.com/docs/integrations/providers/localai/ |
| 64 | + what: "Documents LocalAI as a provider in the Python integrations." |
| 65 | + - name: Flowise |
| 66 | + by: FlowiseAI |
| 67 | + url: https://github.com/FlowiseAI/Flowise |
| 68 | + what: "Offers LocalAI as a node for chat and embeddings in its visual builder." |
| 69 | + - name: AIKit |
| 70 | + by: Sertac Ozercan |
| 71 | + url: https://github.com/sozercan/aikit |
| 72 | + what: "Builds fine-tuned models into images that serve through LocalAI." |
| 73 | + - name: Kairos |
| 74 | + url: https://github.com/kairos-io/kairos |
| 75 | + what: "Ships LocalAI as part of its immutable Linux distribution." |
| 76 | + |
| 77 | +press: |
| 78 | + note: "Written about LocalAI, by people who do not work on it." |
| 79 | + articles: |
| 80 | + - outlet: SUSE |
| 81 | + title: "Running AI locally" |
| 82 | + author: "Christian Huller" |
| 83 | + date: "2025-11-24" |
| 84 | + url: https://www.suse.com/c/running-ai-locally/ |
| 85 | + what: "Deploying LocalAI on openSUSE, then driving it from VS Code." |
| 86 | + - outlet: SUSE |
| 87 | + title: "Adding own documents to your local AI using RAG" |
| 88 | + url: https://www.suse.com/c/adding-own-documents-to-your-local-ai-using-rag/ |
| 89 | + what: "Retrieval over your own documents, on top of LocalAI." |
| 90 | + - outlet: SUSE |
| 91 | + title: "Local AI and Confluence" |
| 92 | + url: https://www.suse.com/c/local-ai-and-confluence/ |
| 93 | + what: "Putting a Confluence space behind a local model." |
| 94 | + - outlet: SUSE |
| 95 | + title: "Introduction to AI training with openSUSE" |
| 96 | + url: https://www.suse.com/c/introduction-to-ai-training-with-opensuse/ |
| 97 | + what: "Training a LoRA and serving it through LocalAI." |
0 commit comments