Searx

Searx is no longer maintained. Thank you for your support and all your contributions. 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 . TL;DR: SearXNG is for users that want more features and bugs getting fixed quicker. If you prefer a minimalist software and stable experience, use 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. 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. 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. SearxNG has rolling releases, dependencies updated more frequently, and engines are fixed faster. It is easy to set up your own public instance, and monitor its performance and metrics. It is simple to maintain as an instance administrator.