xtdb/xtdb

An immutable SQL database for application development, time-travel reporting and data compliance. Developed by @juxt

View on GitHub ↗Jump to charts ↓Open shareable report →

xtdb/xtdb has 3k+ stars and 150+ forks on GitHub, is written in Clojure, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Server / PlatformCategory(s):Relational & SQL DatabasesDatabases & Storage
Added to GitGenius on September 22nd, 2026
Created on March 19th, 2018
Open Issues & Pull Requests: 768 (+0)
GitHub issues: Enabled
Number of forks: 193
Total Stargazers: 3,086 (+0)
Total Subscribers: 56 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.1 hours
Mean response time: 109.1 days
90th percentile: 259.9 days
Tracked items: 1,333

Maintainer activity

9 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 68% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bench" is answered fastest, typically in under an hour, while "1.x" waits about 9 weeks. 45% of tracked open issues have had no activity in three months. Only 58% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 589
New in 7 days: 38
Closed in 7 days: 21
Avg open age: 551 days
Stale 30+ days: 512
Stale 90+ days: 418

Recent activity

Opened in 7 days: 14
Closed in 7 days: 16
Comments in 7 days: 3
Events in 7 days: 83

Top labels

  • 1.x (194)
  • sql (129)
  • pgwire (109)
  • performance (95)
  • spec-reqd (77)
  • documentation (69)
  • repro-reqd (66)
  • good first issue (54)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

XTDB is an immutable SQL database that provides comprehensive time-travel capabilities for application development, time-travel reporting, and data compliance.

XTDB addresses the challenge of maintaining complete data history and handling complex temporal requirements without snapshots or backup restoration. It implements bitemporal versioning, which tracks both system time (when updates occur) and valid time (when data is, was, or will be valid in the business domain). The database is optimized for current-time queries while allowing full audit trails of historical states. It uses an immutable, columnar architecture built on Apache Arrow and designed for object storage, with a log-centric coordination model for distributed deployments.

The tool suits applications requiring strict data compliance, audit trails, or complex temporal queries. Its dynamic schema allows documents with arbitrarily nested data to be inserted without upfront schema definition. XTDB exposes both SQL and XTQL, a full SQL dialect implementing bitemporal functionality as specified in the SQL:2011 standard, available over the Postgres wire protocol. This makes it accessible to teams familiar with standard SQL tooling while providing specialized temporal query capabilities.

The project maintains active engagement with its community through GitHub Discussions and a Discord community. Development activity shows consistent attention to documentation and release management, with organized development resources and a maintained bibliography of related research. The codebase is written in Clojure and supported by JUXT, the organization behind the project.