You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Noémi Ványi d004439646 Update documentation to fix blog link 4 days ago
.github chore: Set permissions for GitHub actions (#3225) 3 months ago
dockerfiles Allow overriding env vars SEARX_SETTINGS_PATH,UWSGI_SETTINGS_PATH 1 year ago
docs Update documentation to fix blog link 4 days ago
examples Fix whitespaces 6 years ago
searx update version file 2 weeks ago
searx_extra Remove `httpx` and use `requests` instead (#3305) 3 weeks ago
tests Bump splinter from 0.17.0 to 0.18.1 (#3307) 3 weeks ago
utils Fix typo in utils/searx.sh (#3331) 2 weeks ago
.codecov.yml codecov : update the commit status 5 years ago
.config.sh [mod] utils/searx.sh install: create branch if not already exists 2 years ago
.coveragerc [mod] use github actions instead of travis 2 years ago
.dir-locals.el [mod] remove obsolete virtualenv command 2 years ago
.dockerignore [enh] update documentation about docker 2 years ago
.gitattributes [enh] add simple theme (WIP) 5 years ago
.gitignore Update httpx and friends to 0.21.3 (#3121) 7 months ago
.landscape.yaml Add landscape.io configuration 8 years ago
.pylintrc Bump pylint from 2.12.2 to 2.14.5 (#3293) 3 weeks ago
AUTHORS.rst update AUTHORS.rst 2 weeks ago
CHANGELOG.rst Update changelog for v1.1.0 2 weeks ago
CONTRIBUTING.md [mod] documentations & comments: update http://* URL to https://*. 2 years ago
Dockerfile Install searx as root in Docker 7 months ago
LICENSE [fix] full AGPLv3+ license according to #382 7 years ago
Makefile [mod] replace makefile boilerplate by 'manage' script 1 year ago
PULL_REQUEST_TEMPLATE.md Add PR template and contribution guidelines 2 years ago
README.rst Reword readme again 2 months ago
babel.cfg [enh] babel.cfg added 9 years ago
manage Fix command to get git version 2 weeks ago
requirements-dev.txt Bump selenium from 4.3.0 to 4.4.0 (#3339) 7 days ago
requirements.txt Bump setproctitle from 1.3.1 to 1.3.2 (#3338) 7 days ago
setup.py Add searx_extra package 1 year ago
tox.ini [enh] tox.ini added to rewrite standard pep8 rules 8 years ago

README.rst


searx install searx homepage searx wiki AGPL License Issues commits OpenCollective searx backers OpenCollective searx sponsors

Privacy-respecting, hackable metasearch engine / pronunciation sɜːks.

If you are looking for running instances, ready to use, then visit searx.space.

Otherwise jump to the user, admin and developer handbooks you will find on our homepage.

contact:

openhub // twitter // IRC: #searx @ Libera (irc.libera.chat)

Frequently asked questions

Is searx in maintenance mode?

No, searx is accepting new features, including new engines. We are also adding engine fixes or other bug fixes when needed. Also, keep in mind that searx is maintained by volunteers who work in their free time. So some changes might take some time to be merged.

We reject features that might violate the privacy of users. If you really want such a feature, it must be disabled by default and warn users about the consequances of turning it off.

What is the difference between searx and SearxNG?

TL;DR: If you want to run a public instance, go with SearxNG. If you want to self host your own instance, choose searx.

SearxNG is a fork of searx, created by a former maintainer of searx. The fork was created because the majority of the maintainers at the time did not find the new proposed features privacy respecting enough. The most significant issue is with engine metrics.

Searx is built for privacy conscious users. It comes a unique set of challanges. One of the problems we face is that users rather not report bugs, because they do not want to publicly share what engines they use or what search query triggered a problem. It is a challenge we accepted.

The new metrics feature collects more information to make engine maintenance easier. We could have had better and more error reports to benefit searx maintainers. However, we believe that the users of searx must come first, not the software. We are willing to compromise on the lack of issue reports to avoid violating the privacy of users.

Furthermore, SearxNG is under heavy refactoring and dependencies are constantly updated, even if it is unnecessary. It increases the risk of introducing regressions. In searx we strive for stability, rather than moving fast and breaking things.

Is searx for me?

Are you privacy conscious user? Then yes.

In searx we decided to double down on being privacy respecting. We are picking engine changes from SearxNG, but we are not implementing engine detailed monitoring and not adding a new UI that relies on Javascript.

If you are willing to give up some privacy respecting features, we encourage you to adopt SearxNG. Searx is targeted for privacy conscious users who run their instances locally, instead of using public instances.

Why should I use SearxNG?

SearxNG has rolling releases, depencencies updated more frequently, and engines are fixed faster. It is easy to set up your own public instance, and monitor its perfomance and metrics. It is simple to maintain as an instance adminstrator.

As a user, it provides a prettier user interface and nicer experience.