Search · facts read November 20, 2026
Postgres full-text search
Search built into Postgres (tsvector, tsquery and GIN indexes), in the database you already run. No new vendor or sync job: search the rows where they live, with tenant filters as a plain WHERE clause.
- Free plan
- Free: part of Postgres; you pay only for the database you already have.
- Paid from
- Not stated on the pricing page
- Monthly cost at 1,000 users
- $0/month No separate bill; 10,000 records with a GIN index is a few MB in the Postgres you already have.
- Free plan allows commercial use
- Yes
- Open source
- Yes
- Self-hostable
- Yes
Source: Postgres full-text search pricing, read November 20, 2026. Prices change; check the vendor's page before you commit.
Best for
- A search bar over tens of thousands of rows
- Filtering search results by tenant or permissions in SQL
- Fewest moving parts
Watch out for
- No typo tolerance out of the box; the pg_trgm extension adds fuzzy matching.
- Relevance tuning and facet counts take hand-written SQL.
- Search load runs on your database, so heavy search traffic competes with everything else.
How Cuely scores Postgres full-text search
The published scores, from −3 to +3, that decide when Cuely picks it. Method
- +3fewer vendors. Search stays in your existing Postgres; no new vendor or index to keep in sync.
- +3keep costs as low as possible. No separate bill; it uses the database you already pay for.
- +3prefers open source or self-hosting. Part of open-source Postgres, on any host.
- −1high volume. Past millions of rows or heavy search traffic, a dedicated search engine is easier to tune and keeps load off the database.