head to head · open source
Cube vs metorikku
Cube has 21,147 GitHub stars, 2,179 forks, 1,185 open issues and last shipped yesterday. metorikku has 589 stars, 155 forks, 65 open issues and last shipped 2 months ago. Cube leads on adoption by 3,490% (21,147 vs 589 stars). Cube is written in Rust under a custom or non-standard licence; metorikku is written in Scala under MIT. Cube has attracted 10% as many forks as stars, metorikku 26%. Cube 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
| Cube | metorikku | |
|---|---|---|
| GitHub stars | ★ 21K | ★ 589 |
| License | Custom / other | MIT |
| Written in | Rust | Scala |
| Last push | 2026-11-02 | 2026-09-01 |
| Forks | ⑂ 2.2K | ⑂ 155 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Cube if
- You weight community size — 21K stars and counting
- You want the Custom / other 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 Cube
Website • Docs • Examples • Blog • Slack • X Cube Core is the open source semantic layer. Define metrics, dimensions, joins, and access rules once in code, then expose them through SQL, REST, and GraphQL APIs to anything downstream — BI tools, custom applications, or AI agents. Cube Core is headless: it doesn't ship a UI, so you can build the analytics experience that fits your product. Cube Core works with all SQL data sources, including cloud data warehouses like Snowflake, Databricks, and BigQuery; query engines like Presto and Amazon Athena; and application databases like Postgres. It has a built in…
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…
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 Cube or metorikku more popular?
Cube has 21,147 GitHub stars and metorikku has 589. Cube has the larger community by that measure.
Are Cube and metorikku free?
Both are open source. Cube has no licence declared in this registry, and metorikku is licensed under MIT. Both are free to self-host.
What is the difference between Cube and metorikku?
Cube 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, Cube or metorikku?
Choose Cube if you want the larger community (21,147 stars) or its Custom / other licence terms. Choose metorikku if its feature set, stack or MIT licence fits better. Both are self-hostable.