searxng

searxng/searxng

SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled.

SearchFor consumersSelf-hostable

Ship status

Still shipping

Pushed in the last 30 days.

Last push
19 Nov 2026
today
Ship score
88/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 38,009 → 39,621 (6 Oct – 17 Nov 2026)
+1,007 stars in the 28 days to 17 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
39.7K
Forks
3.6K
Open issues
209
Watchers
183
Primary language
Python
Created
12 Apr 2021
Owner
searxng · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 141 startups in the directory ship primarily in Python.

Topics

#bing#brave#degoogle#duckduckgo#google#metasearch#privacy#python#qwant#search#search-engine#searx#searxng#startpage#yahoo

How Jev classified this project

Read by Jev, TypeSafe’s classifier, on 22 Sep 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 27% (self-hostable 86%, hosted offering 24%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 19 Nov 2026This is the badge for searxng/searxng, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/searxng/searxng.svg)](https://ossean.com/searxng/searxng)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.