#6868th of 204 in Backends, databases and hosting

citus

PostgreSQL extension that shards tables across nodes for distributed queries

Stars
12.9k
License
AGPL-3.0
Last commit
Nov 2026
Last release
Oct 2026
Language
C
Stars, last 29 weeks+481
25 Apr 2026: 12,385 stars2 May 2026: 12,402 stars9 May 2026: 12,424 stars16 May 2026: 12,442 stars23 May 2026: 12,457 stars30 May 2026: 12,474 stars6 Jun 2026: 12,491 stars13 Jun 2026: 12,515 stars20 Jun 2026: 12,530 stars27 Jun 2026: 12,542 stars4 Jul 2026: 12,548 stars11 Jul 2026: 12,567 stars18 Jul 2026: 12,586 stars25 Jul 2026: 12,601 stars1 Aug 2026: 12,620 stars8 Aug 2026: 12,642 stars15 Aug 2026: 12,667 stars22 Aug 2026: 12,690 stars29 Aug 2026: 12,704 stars5 Sept 2026: 12,719 stars12 Sept 2026: 12,739 stars19 Sept 2026: 12,755 stars26 Sept 2026: 12,769 stars3 Oct 2026: 12,779 stars10 Oct 2026: 12,788 stars17 Oct 2026: 12,807 stars24 Oct 2026: 12,819 stars31 Oct 2026: 12,837 stars7 Nov 2026: 12,852 stars14 Nov 2026: 12,866 stars

12,385 on 25 Apr 202612,866 on 14 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

Citus is a C-based PostgreSQL extension that adds distributed tables, replicated reference tables, a distributed query engine and columnar storage. It runs on a single node or a coordinator plus worker cluster, with shard rebalancing when nodes are added. Aimed at multi-tenant, real-time analytics and time-series workloads that outgrow one Postgres server.

Who it is for: Teams scaling PostgreSQL beyond one node for multi-tenant or analytics workloads

Strengths

  • Runs inside regular PostgreSQL, so existing SQL, extensions and tools keep working
  • Co-located distributed tables allow distributed joins and foreign keys on the distribution column
  • create_distributed_table_concurrently converts live tables without blocking reads or writes
  • Schema-based sharding for multi-tenant and microservice apps without query changes

Weaknesses

  • Columnar tables do not support update, delete or foreign keys
  • Licensed AGPL-3.0, which may constrain some commercial use
  • Multi-node setup needs manual coordinator and worker configuration and shard rebalancing
  • Requires choosing a distribution column up front for good query routing

What it needs

  • no GPU
  • Needs PostgreSQL 18

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Known problems

Open now, reported in the last 90 days

Reported, then fixed by a linked change

Titles are the reporters' own words, taken from the project's GitHub issues and ranked by reactions. We have not tried to reproduce any of them.

Also in Backends, databases and hosting

See all 204
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.7k starscustom license94 out of 100
2coolifySelf-hosted Heroku and Vercel alternative that deploys apps and databases over SSH66.2k starsApache-2.093 out of 100
3strapiHeadless CMS that generates REST and GraphQL APIs from content models Live demo ↗ (opens in a new tab)73.5k starscustom license92 out of 100
#4traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.6k starsMIT92 out of 100
#5appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58.2k stars+653 (+1.1%) in 30 daysBSD-3-Clause92 out of 100