---
title: ParadeDB Enterprise
description: Feature comparison between ParadeDB Community and Enterprise
canonical: https://www.paradedb.com/docs/operate/deploy/enterprise
---

<Note>
  If you're a non-profit or a non-commercial open source project and are
  interested in self-hosting ParadeDB Enterprise, please [contact
  sales](mailto:sales@paradedb.com). We provide complimentary access on a
  case-by-case basis.
</Note>

ParadeDB ships in two versions: ParadeDB Community and ParadeDB Enterprise.
Both editions expose the same SQL APIs for search, filtering, sorting, joins,
and analytics.

ParadeDB Community is the open source edition, licensed under AGPL-3.0. It supports single-node deployments.

ParadeDB Enterprise adds commercial licensing, support, and physical replication for ParadeDB indexes, enabling high availability, failover, and read replicas. It is included with [ParadeDB Cloud](/operate/deploy/cloud). To self-host it, [contact sales](mailto:sales@paradedb.com).

## Feature Comparison

| Feature                                            | ParadeDB Community | ParadeDB Enterprise |
| -------------------------------------------------- | ------------------ | ------------------- |
| **Index Configuration**                            |                    |                     |
| Support for most Postgres types                    | ✅                 | ✅                  |
| Custom tokenizers and filters                      | ✅                 | ✅                  |
| Stemming and multilingual text analysis            | ✅                 | ✅                  |
| Partial and expression indexes                     | ✅                 | ✅                  |
| Columnar indexing                                  | ✅                 | ✅                  |
| Vector indexing                                    | ✅                 | ✅                  |
| **Query Capabilities**                             |                    |                     |
| Full-text search with BM25                         | ✅                 | ✅                  |
| Vector search                                      | ✅                 | ✅                  |
| Hybrid search                                      | ✅                 | ✅                  |
| Fuzzy, phrase, proximity, and regex search         | ✅                 | ✅                  |
| Relevance tuning and highlighting                  | ✅                 | ✅                  |
| Filtering                                          | ✅                 | ✅                  |
| Sorting and Top K                                  | ✅                 | ✅                  |
| Accelerated JOINs                                  | ✅                 | ✅                  |
| Aggregates and facets                              | ✅                 | ✅                  |
| **Concurrency and Consistency**                    |                    |                     |
| ACID transactions and consistent reads<sup>1</sup> | ✅                 | ✅                  |
| Concurrent, non-blocking writes                    | ✅                 | ✅                  |
| **Deployment <sup>2</sup>**                        |                    |                     |
| Crash recovery                                     | ✅                 | ✅                  |
| Point-in-time recovery                             | ✅                 | ✅                  |
| High availability<sup>3</sup>                      | ❌                 | ✅                  |
| Read replica support<sup>3</sup>                   | ❌                 | ✅                  |

<Info>
**Footnotes**

<p className="text-sm">
  1. The ParadeDB index supports Postgres' multi-version concurrency control (MVCC)
  rules. The index reflects the current state of the underlying table at all
  times, changes to the index are atomic, and queries are transactionally
  consistent with the table.
  2. Deployment features and limitations are specific to the ParadeDB index.
  ParadeDB Community can still use standard Postgres replication, crash recovery,
  and point-in-time recovery for heap tables and other Postgres indexes like
  B-tree indexes.
  3. In a primary-replica topology, ParadeDB indexes in ParadeDB Community are
  only available on the primary because Community does not physically replicate
  the ParadeDB index.
</p>
</Info>