PgSearch

PostgreSQL-based search engine with Meilisearch-compatible API.

• Meilisearch API Compatible - Drop-in replacement for Meilisearch
• PostgreSQL Backend - Use your existing PostgreSQL database
• Full-Text Search - Powered by PostgreSQL tsvector and tsquery
• Typo Tolerance - Fuzzy search using pg_trgm extension
• Built-in Dashboard - Web UI for managing indexes and testing search
• Zero Config - Works out of the box with sensible defaults

One-line installation:

curl -sSL https://raw.githubusercontent.com/datamaker/pgsearch/main/docker-compose.yml -o docker-compose.yml && docker compose up -d

Open http://localhost:7700 in your browser.

# Download and start
wget https://raw.githubusercontent.com/datamaker/pgsearch/main/docker-compose.yml
docker compose up -d

docker run -d \
  --name pgsearch \
  -p 7700:7700 \
  -e DB_HOST=your-postgres-host \
  -e DB_USER=postgres \
  -e DB_PASSWORD=yourpassword \
  -e DB_NAME=pgsearch \
  datamaker/pgsearch:latest

git clone https://github.com/datamaker/pgsearch.git
cd pgsearch
npm install
npm run migrate
npm run dev

curl -X POST http://localhost:7700/indexes \
  -H 'Content-Type: application/json' \
  -d '{"uid": "movies", "primaryKey": "id"}'

curl -X POST http://localhost:7700/indexes/movies/documents \
  -H 'Content-Type: application/json' \
  -d '[
    {"id": 1, "title": "Inception", "genre": "Sci-Fi"},
    {"id": 2, "title": "Interstellar", "genre": "Sci-Fi"}
  ]'

curl -X POST http://localhost:7700/indexes/movies/search \
  -H 'Content-Type: application/json' \
  -d '{"q": "incep"}'

Built-in web UI at http://localhost:7700

• Indexes - Create, view, delete indexes
• Documents - Add, view, delete documents
• Settings - Configure searchable/filterable attributes
• Search - Test search with filters and highlighting

Authentication is fully off by default. When the OIDC environment variables below are absent, PgSearch runs in open mode and every endpoint is accessible without credentials (backwards compatible).

To enable it, configure an OIDC identity provider:

Auth is enabled when OIDC_ISSUER, OIDC_CLIENT_SECRET, and PGSEARCH_PUBLIC_URL are all set. Register PGSEARCH_PUBLIC_URL + /auth/oidc/callback as the redirect URI in your IdP.

Users are provisioned automatically on first SSO login (JIT):

• admin — full read/write access, plus member and API key management in the dashboard. Assigned when the email is in PGSEARCH_ADMIN_EMAILS, or when it is the very first user.
• member — read/search-only via the dashboard and session cookie. Write requests return 403.

Admins can promote/demote members and deactivate accounts in the dashboard's Members page (self-demotion/deactivation is blocked to prevent lockout).

For programmatic access (SDKs, servers), admins can create API keys in the dashboard's API Keys page. Keys are shown once at creation and only a SHA-256 hash is stored. Use them Meilisearch-style:

curl http://localhost:7700/indexes/movies/search \
  -H 'Authorization: Bearer <your-api-key>' \
  -H 'Content-Type: application/json' \
  -d '{"q": "wonder"}'

API keys have full read/write access.

• Node.js 20+ / TypeScript
• Fastify
• PostgreSQL 16+ with pg_trgm

Contributions are welcome! Please feel free to submit a Pull Request.

MIT License - see LICENSE for details.