Skip to main content
ParadeDB Banner

Who is ParadeDB for?

You are likely a good fit for ParadeDB if you identify with the following:
  1. Your primary database is Postgres, either managed (e.g. AWS RDS) or self-managed
  2. You have used Postgres’ built-in search capabilities via tsvector and the GIN index, but have reached a scale where you’re limited by performance bottlenecks or missing features like BM25 scoring or fuzzy search
  3. You are evaluating a search engine like Elasticsearch, but don’t want to introduce another cumbersome dependency to your stack

Why ParadeDB?

For teams that already use Postgres, ParadeDB is the simplest way to bring Elastic-quality search to your application.

Zero ETL Required

Syncing Postgres with an external search engine like Elastic can be a time-consuming, error-prone process that involves babysitting ETL pipelines and debugging data inconsistency issues. ParadeDB eliminates this class of problems because you can:

Search That Feels Like Postgres

In ParadeDB, writing a search query is as simple as writing SQL. ParadeDB supports JOINs, which removes the complexity of denormalizing your existing schema.

As Reliable As Postgres

ParadeDB supports Postgres transactions and ACID guarantees. This means that data is searchable immediately after it’s written to ParadeDB, and durable thanks to Postgres write-ahead logging.

ParadeDB vs. Alternatives

People usually compare ParadeDB to two other types of systems: OLTP databases like vanilla Postgres and search engines like Elastic.
OLTP databaseSearch engineParadeDB
Primary roleSystem of recordSearch and retrieval engineSystem of record and search/analytics engine
ExamplesPostgres, MySQLElasticsearch, OpenSearch
Search featuresBasic FTS (no BM25, weak ranking)Rich search features (BM25, fuzzy matching, faceting, hybrid search)Rich search features (BM25, fuzzy matching, faceting, hybrid search)
Analytics featuresNot an analytical DB (no column store, batch processing, etc.)Column store, batch processing, parallelization via shardingColumn store, batch processing, parallelization via Postgres parallel workers
LagNone in a single clusterAt least network, ETL transformation, and indexing timeNone in a single cluster
Operational complexitySimple (single datastore)Complex (ETL pipelines, managing multiple systems)Simple (single datastore)
ScalabilityVertical scaling in a single node, horizontal scaling through KubernetesHorizontal scaling through shardingVertical scaling in a single node, horizontal scaling through Kubernetes
LanguageSQLCustom DSLStandard SQL with custom search operators
ACID guaranteesFull ACID compliance, read-after-write guaranteesNo transactions, atomic only per-document, eventual consistency, durability not guaranteed until flushFull ACID compliance, read-after-write guarantees
Update & delete supportBuilt for fast-changing dataStruggles with updates/deletesBuilt for fast-changing data

Production Readiness

As a company, ParadeDB is over two years old. ParadeDB launched in the Y Combinator (YC) S23 batch and has been validated in production since December 2023. ParadeDB Community, the open-source version of ParadeDB, has been deployed over 400,000 times in the past 12 months. ParadeDB Enterprise, the durable and production-hardened edition of ParadeDB, powers core search and analytics use cases at enterprises ranging from Fortune 500s to fast-growing startups. A few examples include:
  • Alibaba Cloud, the largest Asia-Pacific cloud provider, uses ParadeDB to power search inside their data warehouse. Case study available.
  • Bilt Rewards, a rent payments technology company that processed over $36B in payments in 2024. Case study available.
  • Modern Treasury1, a financial technology company that automates the full cycle of money movement.
  • Span1, one of the fastest-growing AI developer productivity platforms
  • TCDI1, a giant in the legal software and litigation management space.
1. Case study coming soon

Next Steps

You’re now ready to jump into our guides.