Learn how InfluxDB and TimescaleDb 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.
Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
Self-hosted
Repository

Both InfluxDB and TimescaleDb have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with InfluxDB having 31,732 stars and TimescaleDb having 23,465 stars on GitHub. In terms of developer contributions, InfluxDB has 3,716 forks, indicating strong developer engagement.
TimescaleDb is growing faster, adding 219 stars in the last 30 days (+0.9%) against adding 54 stars for InfluxDB (+0.2%). TimescaleDb is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with InfluxDB last updated 2 days ago and TimescaleDb 1 day ago.
Both tools share common technology foundations, being built with Bash, Python. However, they differ in their additional technology choices: InfluxDB uses Rust while TimescaleDb leverages C, Objective-C, Perl.
InfluxDB has been in development longer, starting 13 years ago, compared to TimescaleDb which began 10 years ago. This 3.5-year head start suggests InfluxDB may have more mature features and established processes.
InfluxDB is licensed under Apache-2.0, while TimescaleDb's license terms are not publicly specified.
Both tools serve similar use cases in Time Series Databases. However, they also have distinct specializations: TimescaleDb extends into Relational Databases (SQL).
Both InfluxDB and TimescaleDb offer self-hosting capabilities, giving you full control over your data and infrastructure.