What is OpenSERP?

This free, MIT-licensed project lets you run a local REST service that fetches live search results from six major engines and returns them in a consistent JSON structure. You can query several engines at once and get merged, deduplicated results, or pull the full text of linked pages as clean markdown. It also handles image searches, lets you filter by language, date, file type, or site, and outputs in JSON, Markdown, plain text, or NDJSON. Deployment is a single Docker command or a Go binary; no API keys or usage fees apply. The server listens on port 7000 and includes built-in proxy support, response caching, and automatic retries. A paid cloud offering with API keys and monitoring is available separately.

Should you self-host OpenSERP?

OpenSERP scores 56/100 on selfhost.directory (how scoring works) and ranks #5 of 13 in API. It has 1 513 GitHub stars.

It shipped 9 stable releases in the past year. The latest, v0.8.15, came out on 25 October 2026. New versions land roughly every 3 weeks.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is MIT-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is Hoppscotch Community Edition (83/100, 80 706 stars). It scores higher overall, so compare the two before you pick. See OpenSERP vs Hoppscotch Community Edition side by side.

Features

Browser-rendered results
CLI Tool
Image Search
Megasearch
Multi-engine search
Multiple Output Formats
Proxy Support
Raw HTTP mode
Response caching
REST API server
Retry logic
SERP features parsing
URL extraction

FAQ

Will results always match what I see in my browser?

Not necessarily. Search results change with time, region, language, personalization, and engine availability.

What is the difference between self-hosting and Cloud?

Self-hosting runs OpenSERP on your infrastructure using Docker or a Go binary; Cloud provides a hosted API with API keys, usage history, billing, and monitoring.