TimescaleDB

TimescaleDB is an open-source PostgreSQL extension that turns a standard PostgreSQL database into a high-performance store for time-series and event data.

  • Databases
  • Network Services
  • Productivity
  • Tools & Utilities
TimescaleDB is an open-source PostgreSQL extension that turns a standard PostgreSQL database into a high-performance store for time-series and event data. It adds hypertables, continuous aggregates, and full SQL support on top of PostgreSQL, so you can collect and analyze telemetry, IoT, and monitoring data in real time with the tools you already know.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

70/100 Good

Maintained
100last commit 23 days ago
Popular
8823,772 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
Security check
201 serious finding, 3 minor, CI, tests, OpenSSF Scorecard 4.6/10

Availability: platform listings confirmed today, links checked 9 days ago

GitHub stars
23,772
Open issues
445
Last commit
2026-10-29
Latest release
2.31.0
Activity
declining

Checked 23 days ago - source: GitHub (timescale/timescaledb)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start TimescaleDB locally on port 6543 Run the one-line installer or the Docker command to start TimescaleDB, then wait 1-2 minutes. Docker runs the app in its own isolated box, and this setup uses port 6543 and the password 'password' so you can connect without clashing with another local database. source
  • Check that TimescaleDB is working Connect with psql (a command-line tool for talking to the database) using localhost, port 6543, user postgres, and password 'password', then run the extension check query. If it shows timescaledb, your install is ready and you can start creating tables. source
  • Keep the TimescaleDB data volume The one-line installer stores your database files in a Docker volume (a named storage spot kept outside the container) called timescaledb_data. Keep it safe, because deleting it erases all your data and settings. source
  • Default credentials Set the POSTGRES_PASSWORD environment variable to choose the superuser password; if left at the default, both the user and password are 'postgres'. source

Fetched 37 days ago - each note links to its source

Alternatives (4)

  • Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
  • Graphite Monitoring - Graphite is a highly scalable real-time graphing system.
  • VictoriaMetrics - VictoriaMetrics is a fast, cost-effective, and scalable open-source time-series database that stores long-term monitoring metrics, accepts…
  • questdb - QuestDB is an open-source database designed to make time-series lightning fast and easy.

Checked 51 days ago - source: AlternativeTo

Common questions

What backup practices should I implement for a production self-hosted TimescaleDB instance?

The docs recommend incremental backups, database snapshots, and efficient point-in-time recovery, with many of these achievable using PostgreSQL tooling.

What TimescaleDB limitation should I consider when designing an event-data schema?

The source notes that TimescaleDB has foreign-key limitations that should influence schema design for event data.

Can TimescaleDB manage data retention?

A community thread describes TimescaleDB as solving common PostgreSQL operational problems through data retention management.

How does TimescaleDB compare to NoSQL databases for time-based logs?

A thread compares their speed and scalability for storing and parsing time-based logs and mentions performance concerns as log volumes grow.

Answers sourced from docs.timescale.com, www.reddit.com, www.reddit.com, www.reddit.com

Community

Collected 53 days ago - public community threads