Firecrawl, the open source web scraping and crawling API that turns any website into clean, LLM ready markdown or structured data, rendered on box and secured on first boot.
Firecrawl is an open source web scraping and crawling API. Point it at a URL and it fetches the page, renders it in a real headless browser so JavaScript heavy sites work, and returns clean markdown or structured data ready to feed to a language model or a data pipeline. It crawls whole sites, following links up to a depth and page limit you choose, and returns each page as markdown, so you can build search indexes, knowledge bases and retrieval augmented generation datasets from live web content. Scraping and crawling run entirely on the instance using the bundled browser service, with a Postgres backed job queue and Redis for rate limiting and caching, so large crawls run reliably in the background.
It suits developers and data teams who need web content as clean text without building and operating a browser farm: feeding retrieval augmented generation and AI agents with up to date pages, monitoring and extracting data from sites, and turning documentation or catalogues into structured datasets. The self hosted deployment does real scraping and crawling with no external cloud key, so your requests and the pages you fetch stay inside your own cloud account.
cloudimg delivers Firecrawl fully installed with its headless browser renderer, job queue database, message broker and cache on the same instance and the API fronted by nginx, so the scraping API answers the moment the instance boots. Because self hosted Firecrawl ships with no built in authentication and is open by default, the image is secure by default: nothing is exposed without a token. A unique API bearer token, together with the database, cache, broker and admin secrets, is generated on the first boot of each instance before the port is reachable, written to a root only credentials file, and enforced at the nginx front door so every request except the health check must carry the token. The renderer, queue database, broker and cache are reachable only on the instance, state starts empty on first boot, and the image ships with a paired step by step deploy guide and 24/7 cloudimg support.