Reading collection

Self-Hosted Search Engine: SearXNG or Private Index?

Choose between web metasearch and local document search based on query privacy, relevance, access control and recovery.

Editorial update

Decision in brief

Use SearXNG when you want web results from multiple upstream engines through an instance you operate. Build a private index when you need to search your own records or cannot send queries to outside services. Keep conventional browser search if upstream failures in the pilot make the extra service hard to justify.

Choose what to search: Web sources — Metasearch. Your records — Private index. Simple needs — Browser search.
Check what data the search sends to upstream providers and how their failures affect the pilot.

Separate web results from documents you own

SearXNG sends web queries to configured search engines and combines their responses. Your deployment controls local access and logging. Upstream engines still receive relevant queries from the instance and can time out, throttle or return no results. Review settings for outgoing timeouts and enabled engines, and keep sensitive internal searches on a different endpoint.

A private index serves documents you feed into it. Use a file or history search tool for one person's approved local data. For a team catalog, consider a managed index or a self-hosted service such as Meilisearch and plan ingestion, deletion and permission evaluation. Keep admin credentials out of any browser integration.

Search taskStarting pointWhat to measure
Public web with self-managed interfaceSearXNG with a small engine allowlistTop-five relevance, empty responses and latency by query group.
Offline private filesLocal index over a named folder or corpusExpected results without external connectivity and removal after deleting a source.
Team documents with permissionsAccess-controlled indexing with a filtered query pathEvery permitted result appears and prohibited documents stay hidden for the test identity.
Standard personal web searchExisting browser default as a baselineSwitch only if relevance and reliability make the new operational burden worthwhile.

Two HN cases showing different failure modes

In an AgentSearch thread, tahseen0amin reported that a SearXNG-backed service responded but returned zero results. Include a known-answer smoke query to distinguish a running interface from a functioning upstream search path.

dandaka described building Traul to index messages from several apps in a local database. In that design retrieval quality depends on the set of ingested sources and the freshness of the sync. Review what enters the index and rehearse removing a test result from it.

Evaluate a week of representative queries

  1. Prepare 20 harmless searches with an expected result or relevance rubric. Keep public queries and synthetic private documents in distinct sets. If the use case is web search, compare your browser default and private metasearch instance.
  2. Record top-five hits, latency, empty responses and upstream timeouts under ordinary use. Retest with one configured engine intentionally disabled. If using a document index, test insert, update, deletion and two roles.
  3. Verify browser use from the intended devices, review local request logs for query retention, and restore one configuration or rebuild the synthetic index from source.
  4. Proceed if at least 18 of 20 suitable queries find expected results in the top five, the chosen latency target holds and every private visibility test passes. Stop if private search requires web requests or any forbidden document appears.

Related articles