Firecrawl-postgres

Firecrawl NuQ PostgreSQL is the dedicated PostgreSQL database for a self-hosted Firecrawl deployment, storing its NuQ job queue and application data.

  • Databases
  • Network Services
  • Productivity
  • Tools & Utilities
Firecrawl NuQ PostgreSQL is the dedicated PostgreSQL database for a self-hosted Firecrawl deployment, storing its NuQ job queue and application data. It runs the official Firecrawl nuq-postgres image and connects to Firecrawl over the Docker network with no host port required, giving self-hosters a ready-to-use backing database without managing a separate generic PostgreSQL server.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

41/100 Fair

Maintained
No data
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 22 days ago

No GitHub repository data collected yet.

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your Firecrawl API key Create the Firecrawl client with your API key (the fc-... value that identifies your account). Without it, Firecrawl will not accept scrape or crawl requests from your app. source
  • Install Playwright browsers When setting up the scraping service, install Playwright and its browser packages. These provide the real web browser used to load pages; without them, some scraping jobs can fail or return empty results. source
  • PostgreSQL connection settings Configure POSTGRES_USER (default postgres), POSTGRES_PASSWORD (required), and POSTGRES_DB (default postgres). The service listens on internal port 5432 and Firecrawl connects over the Docker network, so no host port is needed. Data persists at /mnt/user/appdata/firecrawl/postgres. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Firecrawl-postgres require a host port to be exposed?

No. The PostgreSQL service listens on internal port 5432, and Firecrawl connects over the Docker network, so no host port is needed.

Which PostgreSQL connection environment variables should be configured?

Configure POSTGRES_USER, whose default is postgres, POSTGRES_PASSWORD, which is required, and POSTGRES_DB, whose default is postgres.

Where is Firecrawl-postgres data stored for backups?

Data persists at /mnt/user/appdata/firecrawl/postgres.

Does the Python SDK require an API key for scrape or crawl requests?

Yes. Create the Firecrawl client with your API key, the fc- value that identifies your account. Without it, Firecrawl will not accept scrape or crawl requests.

Why might scraping jobs fail or return empty results in a self-hosted Firecrawl deployment?

Install Playwright and its browser packages when setting up the scraping service. They provide the real browser used to load pages, and without them some scraping jobs can fail or return empty results.

Answers sourced from ca.unraid.net, github.com, github.com

Community

Collected 3 days ago - public community threads