diff --git a/README.rst b/README.rst
index 03d29da7..e10c3f47 100644
--- a/README.rst
+++ b/README.rst
@@ -66,8 +66,62 @@ contact:
 .. _openhub: https://www.openhub.net/p/searx
 .. _twitter: https://twitter.com/Searx_engine
 
--------
 
-|gluten free|
+# Frequently asked questions
 
-.. |gluten free| image:: https://forthebadge.com/images/featured/featured-gluten-free.svg
+## 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 two new proposed features privacy respecting enough. Those two features are
+engine metrics and the new theme.
+
+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 challange 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.
+
+Also, everyone who has eyes knows that the UI of searx should be improved. Thus, we
+wanted to update it. One of the promises of searx is that it works
+without Javascript by default. However, the new user interface does not. So
+we wanted to make the new design opt-in, not default.
+
+## 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.