head to head · open source
LocalAI vs Grepture
LocalAI has 50,187 GitHub stars, 4,574 forks, 201 open issues and last shipped yesterday. Grepture has 12 stars, 0 forks, 0 open issues and last shipped 2 days ago. LocalAI leads on adoption by 418,125% (50,187 vs 12 stars). LocalAI is written in Go under MIT; Grepture is written in TypeScript under AGPL-3.0. LocalAI has attracted 9% as many forks as stars, Grepture 0%. LocalAI was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| LocalAI | Grepture | |
|---|---|---|
| GitHub stars | ★ 50K | ★ 12 |
| License | MIT | AGPL-3.0 |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-03 |
| Forks | ⑂ 4.6K | ⑂ 0 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick LocalAI if
- You weight community size — 50K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick Grepture if
- You want the Grepture feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and Grepture fits your workflow better
About LocalAI
Deutsch Español français 日本語 한국어 Português Русский 中文 LocalAI is the open source AI engine. Run any model LLMs, vision, voice, image, video on any hardware. No GPU required. A small core, not a bundle. Each backend wraps a best in class engine (llama.cpp, vLLM, whisper.cpp, stable diffusion, MLX...) in its own image, pulled only when a model needs it. You install nothing you don't use. Composable by design : backends are separate and pulled on demand, so you install only what your model needs Open and extensible : load any model, or build your own backend in any language against an open interface Drop in API…
read the full LocalAI overview →
About Grepture
Grepture Proxy An LLM API proxy that detects and redacts PII, blocks sensitive content, and tokenizes fields — all before requests reach your AI provider. Quick Start The proxy starts on port 4001 by default. Send requests through it by setting the X Grepture Target header to your upstream API: The proxy will redact john@example.com before it reaches the API, based on your rules. Configuration Body Storage The proxy logs request and response bodies as part of its traffic log. For local mode runs, bodies are written to stdout and there is no size limit beyond what fits in memory (default 10MB per request). For…
read the full Grepture overview →
More in AI & Machine Learning
Related comparisons
More Machine Learning Infrastructure projects
Compare either of these against the rest of the Machine Learning Infrastructure field.
Frequently asked questions
Is LocalAI or Grepture more popular?
LocalAI has 50,187 GitHub stars and Grepture has 12. LocalAI has the larger community by that measure.
Are LocalAI and Grepture free?
Both are open source. LocalAI is licensed under MIT and Grepture under AGPL-3.0. Neither carries a licence fee.
What is the difference between LocalAI and Grepture?
LocalAI is written in Go and Grepture in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, LocalAI or Grepture?
Choose LocalAI if you want the larger community (50,187 stars) or its MIT licence terms. Choose Grepture if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.