head to head · open source
llama_index vs Grepture
llama_index has 52,779 GitHub stars, 8,500 forks, 770 open issues and last shipped 8 days ago. Grepture has 12 stars, 0 forks, 0 open issues and last shipped yesterday. llama_index leads on adoption by 439,725% (52,779 vs 12 stars). llama_index is written in Python under MIT; Grepture is written in TypeScript under AGPL-3.0. llama_index has attracted 16% as many forks as stars, Grepture 0%. Grepture 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
| llama_index | Grepture | |
|---|---|---|
| GitHub stars | ★ 53K | ★ 12 |
| License | MIT | AGPL-3.0 |
| Written in | Python | TypeScript |
| Last push | 2026-10-26 | 2026-11-02 |
| Forks | ⑂ 8.5K | ⑂ 0 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick llama_index if
- You weight community size — 53K stars and counting
- You want the MIT license terms
- Your stack matches Python
- 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 llama_index
🗂️ LlamaIndex (OSS Framework) 🦙 [!NOTE] The current focus of LlamaIndex is to build the best AI powered engine for document parsing and extraction. LlamaParse is our enterprise platform for agentic OCR, parsing, extraction, indexing and more. LiteParse represents our efforts to build the best free, fast, cheap text parser in the market. ParseBench and ExtractBench represent our commitment towards open benchmarking for parsing and extraction. The company itself has undergone an evolution since when this OSS framework first launched 3 years ago in 2023. Since the early days, the framework has consisted of a…
read the full llama_index 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 llama_index or Grepture more popular?
llama_index has 52,779 GitHub stars and Grepture has 12. llama_index has the larger community by that measure.
Are llama_index and Grepture free?
Both are open source. llama_index is licensed under MIT and Grepture under AGPL-3.0. Neither carries a licence fee.
What is the difference between llama_index and Grepture?
llama_index is written in Python 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, llama_index or Grepture?
Choose llama_index if you want the larger community (52,779 stars) or its MIT licence terms. Choose Grepture if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.