A · leads
oceanbase
94.7
10,422 stars · Apache-2.0
Analytics
oceanbase leads by 6.2 · narrow
A · leads
94.7
10,422 stars · Apache-2.0
B
88.5
9,535 stars · AGPL-3.0
oceanbase versus paradedb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. oceanbase is written mainly in C++; paradedb is written mainly in Rust. The composite score is 94.7 for oceanbase and 88.5 for paradedb.
oceanbase has 10,422 GitHub stars to paradedb's 9,535, a gap of 887 (1.09×). Forks are 1,932 for oceanbase and 515 for paradedb. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 82.
Push history: oceanbase was last pushed on 17 November 2026 (0 days ago), and paradedb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 610 for oceanbase (0.059 per star) and 284 for paradedb (0.030 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
oceanbase is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. paradedb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for oceanbase and 52 for paradedb. This is a procurement signal, not legal advice.
In Analytics, both oceanbase (10,422 stars) and paradedb (9,535 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: oceanbase is open source, paradedb is open source.
The lead is split. oceanbase is furthest ahead on license flexibility (96 to 52), while paradedb is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
oceanbase finishes ahead at 94.7 against paradedb at 88.5, a 6.2 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | oceanbase | paradedb |
|---|---|---|
| GitHub stars | 10,422 | 9,535 |
| Forks | 1,932 | 515 |
| Open issues | 610 | 284 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 52 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 88.5 |
OceanBase is the unified distributed database for the AI era — open-source, multi-model, one engine for your most demanding workloads.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
oceanbase has more GitHub stars: 10,422 versus 9,535 for paradedb. The gap is 887 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both oceanbase and paradedb as self-hostable. Confirm each project's deploy docs before you plan a migration.
oceanbase is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. paradedb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
oceanbase scores 94.7 and paradedb scores 88.5. This page calls that a narrow lead for oceanbase.