SLSearch
SLSearch
Quick frequently asked questions
Does SLSearch store my searches?
No. SLSearch does not store or save any search history.
Does SLSearch support SafeSearch?
Currently, SafeSearch is not supported because SLSearch relies on whichever API provider is selected for your query.
Is SLSearch open source?
No. The project itself is closed-source, but it uses many open-source libraries and APIs.
What browsers does SLSearch support?
SLSearch works in all modern browsers.
Why does SLSearch exist?
SLSearch started as a personal hobby project and as a small companion service for SLBr around 2021-2022.
SLSearch is not designed to compete with major search engines.
It serves mainly as:
A learning project
A search engine for SLBr
A place to experiment with search features and instant answers
A functional, lightweight search engine for everyday searches
Is SLSearch based on Searx or any existing engines?
SLSearch is not built using Searx, SearXNG, Whoogle, or any other existing metasearch engine codebase.
It is written entirely from scratch using Flask and a collection of Python libraries.
This makes SLSearch lighter and easier to maintain.
Developer's Note
When SLSearch began, I wasn't aware of engines like SearXNG at the time. But even so, I would've still built my own from scratch as an experiment with my own ideas.
Why is SLSearch slow sometimes?
Response time depends on which search engine is chosen.
Some providers are very fast, others may be temporarily slow or rate-limited.
If the selected provider is experiencing delays, the search may take a moment longer than usual.
Does SLSearch track me or use analytics?
No. SLSearch does not track your identity, build profiles or log searches.
Security data is only used for bot detection.
Why doesn't SLSearch merge or rank results from multiple engines?
Traditional metasearch engines merge and rank results from many sources simultaneously.
This requires:
Multiple API calls (more API rate limits)
Heavy & complex ranking logic
More server resources
SLSearch avoids this complexity by selecting just one engine per search.
This makes the system easier to maintain and keeps server cost very low.