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
Oct 9, 2026
today
Ship score
88/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 36,111 → 38,009 (Aug 25 – Oct 6, 2026)
+1,369 stars in the 28 days to 2026-10-06

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

Repo facts

What GitHub reports.

Stars
38.2K
Forks
3.5K
Open issues
190
Watchers
179
Primary language
Python
Created
Apr 12, 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. 109 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 it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 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 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-09This 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.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.