Learn how QuestDB and TDengine differ in their key features, development activity, technology stack and community adoption, so you can decide which of these time series databases is best for you.

Both QuestDB and TDengine have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with QuestDB having 17,220 stars and TDengine having 25,011 stars on GitHub. In terms of developer contributions, TDengine has 5,012 forks, indicating strong developer engagement.
Both projects show recent activity, with QuestDB last updated 9 hours ago and TDengine 1 day ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, Golang, Rust, C, Objective-C, PHP, Java, C++, C#. However, they differ in their additional technology choices: TDengine leverages CSS, MATLAB, Lua, R, Ada.
QuestDB has been in development longer, starting 12 years ago, compared to TDengine which began 7 years ago. This 5.3-year head start suggests QuestDB may have more mature features and established processes.
The projects use different licenses: QuestDB is licensed under Apache-2.0 while TDengine uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Time Series Databases.

vs
Activity score
Stars
Forks
Last commit
Repository age
Version
License
Repository
Activity score
Stars
Forks
Last commit
Repository age
Version
License
Repository