Privacy-respecting, hackable metasearch engine / pronunciation sks.
If you are looking for running instances, ready to use, then visit searx.space.
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.
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 challenges. 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.
Are you privacy conscious user? Then yes.
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.
As a user, it provides a prettier user interface and nicer experience.