In Progress
Vector Search
- Native vector search (beta). The ParadeDB index natively indexes pgvector’s
vectortype, addressing pgvector’s limitations around filtered queries — specifically, queries that combine vector similarity with metadata filters or full-text search predicates. - Incremental index maintenance. Vector search quality currently degrades as indexed rows are updated. We are implementing SPFresh to maintain index quality incrementally.
- Remaining pgvector types. Implement support for pgvector’s
halfvec,sparsevec, andbittypes.
JOIN Improvements
- Join pushdown (beta). Join pushdown pushes search predicates directly into the index for significantly better performance.
- Smarter JOIN planning for search indexes. Apply index-aware optimizations and cost estimation strategies when multiple ParadeDB-indexed tables are joined.
Ecosystem Integrations
- ORMs. Official support for more ORMs, like Prisma and others, is coming. Drizzle, Django, SQLAlchemy, Rails, and Entity Framework Core are already available.
- AI Frameworks. Official support for LangChain, LlamaIndex, CrewAI, and others is coming.
- PaaS Providers. Official tutorials for hosting ParadeDB on more platform-as-a-service providers like Heroku and others are coming. Railway, Render, Fly.io, DigitalOcean, and Dokku are already available.
Managed Cloud
- Today, you can deploy ParadeDB self-hosted, on cloud platforms, or with ParadeDB BYOC. We’re also building ParadeDB Cloud, a fully managed ParadeDB: first-class search from Postgres, with a developer experience to match. Join the waitlist to get notified when it launches.
Long Term
Deeper Analytics Improvements
- Push Postgres visibility rules into the index. This is currently a filter applied post index scan that adds overhead to large scans.