pgai
Not yet source-checkedA suite of tools to develop RAG, semantic search, and other AI applications more easily with PostgreSQL
Machine-drafted from the vendor's site · not yet source-checkedProfile updated Link checked How we rate
In short
pgai turns PostgreSQL into a RAG engine with automatic embedding sync. Note: it is no longer maintained as of February 2026.
Developers building RAG and Agentic applications who want to use PostgreSQL as a retrieval engine with automatic embedding synchronization.
Users seeking an actively maintained or supported library, as the project is no longer being maintained or supported as of February 2026.
pgai is a Python library that transforms PostgreSQL into a robust, production-ready retrieval engine for RAG and Agentic applications. It automatically creates and synchronizes vector embeddings from PostgreSQL data and S3 documents, ensuring embeddings update as data changes. The tool includes a Semantic Catalog feature that enables natural language to SQL by automatically generating database descriptions. It supports powerful vector and semantic search using pgvector and pgvectorscale. The system is designed to be production-ready out-of-the-box, handling batch processing, model failures, rate limits, and latency spikes. It works with any PostgreSQL database, including Timescale Cloud, Amazon RDS, and Supabase. The architecture consists of an application, a PostgreSQL database, and stateless vectorizer workers that decouple data modifications from the embedding process to ensure resilience.
The page documents pgai as a Python library for creating RAG and Agentic applications using PostgreSQL. It highlights features like automatic embedding synchronization, semantic search, and text-to-SQL capabilities. The page explicitly states that the project is no longer being maintained or supported as of February 2026 and that the repository is archived and read-only. It lists supported embedding models including OpenAI, Ollama, and Cohere, and details the architecture involving stateless vectorizer workers. The page does not provide specific pricing for the tool itself, noting it is open s
— The AI Tool Bible editorial team
Pros
- ✅ Automatically create and synchronize vector embeddings from PostgreSQL data and S3 documents
- ✅ Enable natural language to SQL with AI via Semantic Catalog
- ✅ Production-ready out-of-the-box with built-in handling for model failures, rate limits, and latency spikes
- ✅ Works with any PostgreSQL database, including Timescale Cloud, Amazon RDS, and Supabase
- ✅ Resilient architecture where data modifications are decoupled from the embedding process
Cons
- ⚠️ As of February 2026, this project is no longer being maintained or supported
- ⚠️ The repository was archived by the owner on May 27, 2026, and is now read-only
- ⚠️ Requires running a vectorizer worker if not on Timescale Cloud
- ⚠️ Requires an OpenAI API key for the quick start example
Facts
- Platforms
- cli, api
- API available
- Yes
- Open source
- Yes (license: PostgreSQL)
- GitHub stars
- 5,794 (checked Nov 13, 2026)
- Last GitHub push
- May 27, 2026
- First commit
- May 2024
- Archived on GitHub
- Yes
- Package downloads (30 d)
- 2,017 · pypi pgai · checked Nov 18, 2026
Where this tool sits
Use cases
Frequently asked
- Is pgai free to use?
- Yes, pgai is listed as free. However, the project is no longer being maintained or supported as of February 2026, so users should consider this before adoption.
- Which databases does pgai support?
- It works with any PostgreSQL database, including Timescale Cloud, Amazon RDS, and Supabase. It uses pgvector and pgvectorscale for vector and semantic search capabilities.
- How does pgai handle data changes?
- It automatically creates and synchronizes vector embeddings from PostgreSQL data and S3 documents. This ensures embeddings update as data changes, using stateless vectorizer workers to decouple modifications from embedding.
- What features does pgai offer for SQL generation?
- It includes a Semantic Catalog feature that enables natural language to SQL by automatically generating database descriptions. This supports Text-to-SQL use cases within the tool.
- Is pgai suitable for production environments?
- The system is designed to be production-ready out-of-the-box, handling batch processing, model failures, rate limits, and latency spikes. However, it is no longer maintained as of February 2026.