paradedb
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
💡 Why It Matters
This project extends PostgreSQL with a custom Rust-based extension that combines full-text search, vector retrieval, BM25 scoring, and OLAP-style aggregations within a single database engine. It eliminates the need to maintain separate search infrastructure by embedding search and analytics capabilities directly into Postgres using proven Rust libraries like Tantivy and Apache DataFusion. Backend engineers and platform teams benefit from this unified approach, especially when ACID transactions and SQL compatibility are priorities. The project is reasonably mature with over 9,500 stars and recent commits, although its growth signal is not significant yet, indicating it may still be evolving in adoption and ecosystem maturity. It is not a good fit if you require a dedicated, standalone search engine with broader language support or a more established ecosystem, such as Elasticsearch or OpenSearch, especially when decoupling search from the primary database is preferred.
🎯 When to Use
Choose this when you want to consolidate application data and search capabilities in one PostgreSQL database, leveraging SQL for both transactional and analytical queries. If your workload demands a standalone search engine or you need more mature vector search tooling, consider Elasticsearch or Vespa instead for their broader feature sets and production track records.
👥 Team Fit & Use Cases
Typically used in systems that require integrated full-text and vector search alongside transactional data, such as internal knowledge bases with advanced search ranking or analytics dashboards combining OLAP queries and search filters. It suits teams building applications that want to avoid managing separate search infrastructure while preserving SQL workflows.
🎭 Best For
🏷️ Topics & Ecosystem
📊 Activity
Latest commit: 2026-11-14. Over the past 87 days, this repository gained 336 stars (+3.7% growth). Activity data is based on daily RepoPi snapshots of the GitHub repository.