head to head · open source
Cube vs peerdb
Cube has 21,147 GitHub stars, 2,179 forks, 1,185 open issues and last shipped yesterday. peerdb has 3,313 stars, 232 forks, 204 open issues and last shipped yesterday. Cube leads on adoption by 538% (21,147 vs 3,313 stars). Cube is written in Rust under a custom or non-standard licence; peerdb is written in Go under AGPL-3.0. Cube has attracted 10% as many forks as stars, peerdb 7%. peerdb was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (bigquery), 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 20902 open source comparisons
Side by side
| Cube | peerdb | |
|---|---|---|
| GitHub stars | ★ 21K | ★ 3.3K |
| License | Custom / other | AGPL-3.0 |
| Written in | Rust | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 2.2K | ⑂ 232 |
| 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 peerdb if
- You want the peerdb feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Go
- You evaluated both and peerdb 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 peerdb
Frustratingly simple ETL for Postgres PeerDB At PeerDB, we are building a fast, simple and the most cost effective way to stream data from Postgres to Data Warehouses, Queues and Storage engines. If you are running Postgres at the heart of your data stack and move data at scale from Postgres to any of the above targets, PeerDB can provide value. We support different modes of streaming log based (CDC), cursor based (timestamp or integer) and XMIN based. Performance wise, we are 10x faster than existing tools. Features wise, we support native Postgres features such as comprehensive set of data types incl…
read the full peerdb 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 peerdb more popular?
Cube has 21,147 GitHub stars and peerdb has 3,313. Cube has the larger community by that measure.
Are Cube and peerdb free?
Both are open source. Cube has no licence declared in this registry, and peerdb is licensed under AGPL-3.0. Both are free to self-host.
What is the difference between Cube and peerdb?
Cube is written in Rust and peerdb in Go. 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 peerdb?
Choose Cube if you want the larger community (21,147 stars) or its Custom / other licence terms. Choose peerdb if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.