head to head · open source
CocoIndex vs metorikku
CocoIndex has 11,572 GitHub stars, 900 forks, 83 open issues and last shipped yesterday. metorikku has 589 stars, 156 forks, 65 open issues and last shipped 17 days ago. CocoIndex leads on adoption by 1,865% (11,572 vs 589 stars). CocoIndex is written in Rust under Apache-2.0; metorikku is written in Scala under MIT. CocoIndex has attracted 8% as many forks as stars, metorikku 26%. CocoIndex was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (etl), so they are genuine substitutes rather than adjacent tools.
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 8884 open source comparisons
Side by side
| CocoIndex | metorikku | |
|---|---|---|
| GitHub stars | ★ 12K | ★ 589 |
| License | Apache-2.0 | MIT |
| Written in | Rust | Scala |
| Last push | 2026-09-17 | 2026-09-01 |
| Forks | ⑂ 900 | ⑂ 156 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick CocoIndex if
- You weight community size — 12K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Rust
- You value the larger contributor base for long-term maintenance
pick metorikku if
- You want the metorikku feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Scala
- You evaluated both and metorikku fits your workflow better
About CocoIndex
CocoIndex is an open source incremental data transformation engine for AI workloads, built in Rust with a Python interface and positioned in the data engineering, ETL, indexing, and AI agent ecosystem. It turns codebases, meeting notes, inboxes, Slack, PDFs, and videos into continuously fresh context for AI agents and LLM applications.
read the full CocoIndex overview →
About metorikku
Metorikku is a library that simplifies writing and executing ETLs on top of Apache Spark. It is based on simple YAML configuration files and runs on any Spark cluster. The platform also includes a simple way to write unit and E2E tests. Getting started To run Metorikku you must first define 2 files. Metric file A metric file defines the steps and queries of the ETL as well as where and what to output. For example a simple configuration YAML (JSON is also supported) should be as follows: yaml metric: "/path/to/metric" mocks: name: table 1 path: mocks/table 1.jsonl tests: df2: id: 200 name: test id: 300 name: test2…
read the full metorikku overview →
More in Data & Analytics
Related comparisons
More Data Engineering & Integration projects
Compare either of these against the rest of the Data Engineering & Integration field.
Frequently asked questions
Is CocoIndex or metorikku more popular?
CocoIndex has 11,572 GitHub stars and metorikku has 589. CocoIndex has the larger community by that measure.
Are CocoIndex and metorikku free?
Both are open source. CocoIndex is licensed under Apache-2.0 and metorikku under MIT. Neither carries a licence fee.
What is the difference between CocoIndex and metorikku?
CocoIndex is written in Rust and metorikku in Scala. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, CocoIndex or metorikku?
Choose CocoIndex if you want the larger community (11,572 stars) or its Apache-2.0 licence terms. Choose metorikku if its feature set, stack or MIT licence fits better. Both are self-hostable.