Skip to content
DevUtils Online

Databases

directus vs QuestDB

QuestDB leads by 5.6 · narrow

A

directus

84.8

38,739 stars · license n/a

B · leads

QuestDB

90.4

17,538 stars · Apache-2.0

directus versus QuestDB is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. directus is written mainly in TypeScript; QuestDB is written mainly in Java. The composite score is 84.8 for directus and 90.4 for QuestDB.

directus has 38,739 GitHub stars to QuestDB's 17,538, a gap of 21,201 (2.21×). Forks are 5,001 for directus and 1,701 for QuestDB. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 87.

Push history: directus was last pushed on 17 November 2026 (0 days ago), and QuestDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 346 for directus (0.009 per star) and 1,515 for QuestDB (0.086 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.

directus is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. QuestDB 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. License scores in this pair are 30 for directus and 96 for QuestDB. This is a procurement signal, not legal advice.

Only QuestDB is marked self-hostable here (17,538 stars, deploy score 100). directus is not (38,739 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: directus is unpriced in this catalog, QuestDB is open source.

The lead is split. directus is furthest ahead on issue health (84 to 52), while QuestDB is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

QuestDB finishes ahead at 90.4 against directus at 84.8, a 5.6 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

directus versus QuestDB metrics
Signal directus QuestDB
GitHub stars 38,739 17,538
Forks 5,001 1,701
Open issues 346 1,515
Adoption 100 92
Activity 100 100
Community 100 87
Issue health 84 52
License 30 96
Self-hosting 35 100
Composite 84.8 90.4

directus

The flexible backend for all your projects 🐰 Turn your DB into a headless CMS, admin panels, or apps with a custom UI, instant APIs, auth & more.

Project site · GitHub · Full profile

QuestDB

QuestDB is a time-series database with SQL and a focus on ingestion speed. It is used for metrics, market data, and other timestamp-heavy workloads.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, directus or QuestDB?

directus has more GitHub stars: 38,739 versus 17,538 for QuestDB. The gap is 21,201 stars.

Which was updated more recently, directus or QuestDB?

Both were last pushed on 17 November 2026.

Can I self-host both directus and QuestDB?

Only QuestDB is marked self-hostable. directus is not.

Which license is easier to embed in a commercial product, directus or QuestDB?

directus is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. QuestDB 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the directus vs QuestDB score?

QuestDB scores 90.4 and directus scores 84.8. This page calls that a narrow lead for QuestDB.

Related comparisons