How kerberos255/searxng-windows works
This repository packages a native Windows SearXNG installer and operations toolkit, with an optional API-first search gateway. The main workflow is a client querying local SearXNG directly or, when enabled, the Broker; the Broker tries configured API providers in priority order, then falls back to free SearXNG engines. The graph also shows installation/configuration, provider health state, and the SearXNG adapter. Broker internals are sampled; lifecycle scripts and upstream SearXNG behavior are represented from README documentation, not inspected source.
Main entry points: app.py Search Broker · base.py Provider Interface · parallel.py Parallel Search · tavily.py Tavily Search
Components 19
Windows Operations
- Install Toolkit
scripts/install.ps1 - Service Launcher
scripts/start.ps1 - Health Check
scripts/check.ps1 - Source Updater
scripts/update.ps1 - Local Configuration
config/settings.example.yml
SearXNG Search
- SearXNG Service
- API Pool Engine Adapter
patches/api_pool.py - Date-Range Compatibility
scripts/patch_time_range_engines.py - Free SearXNG Engines
API Pool Broker
- Search Broker
api_pool/app.py - Broker Configuration
api_pool/config.py - Provider State
api_pool/state.py
Search Providers
- Provider Interface
api_pool/providers/base.py - Parallel Search
api_pool/providers/parallel.py - Tavily Search
api_pool/providers/tavily.py - Brave Search
api_pool/providers/brave.py - Firecrawl Search
api_pool/providers/firecrawl.py
Other components
- Search Client
- Search Upstreams
Connections 27
- Install Toolkit → SearXNG Service: installs
README.md - Install Toolkit → Local Configuration: generates
README.md - Service Launcher → SearXNG Service: starts
README.md - Service Launcher → Search Broker: starts if enabled
README.md - Health Check → SearXNG Service: checks health
README.md - Source Updater → SearXNG Service: updates source
README.md - Search Client → SearXNG Service: searches port 8888
README.md - Search Client → Search Broker: searches port 8890
README.md - SearXNG Service → API Pool Engine Adapter: dispatches search
patches/api_pool.py - API Pool Engine Adapter → Search Broker: posts query
patches/api_pool.py - Search Broker → Broker Configuration: reads settings
api_pool/app.py - Search Broker → Provider State: reads and updates
api_pool/app.py - Search Broker → Parallel Search: dispatches by priority
README.md - Search Broker → Tavily Search: dispatches by priority
README.md - Search Broker → Brave Search: dispatches by priority
README.md - Search Broker → Firecrawl Search: dispatches by priority
README.md - Search Broker → Free SearXNG Engines: falls back when needed
README.md - Free SearXNG Engines → SearXNG Service: queries engines
README.md - Parallel Search → Provider Interface: uses shared client
api_pool/providers/parallel.py - Tavily Search → Provider Interface: uses shared client
api_pool/providers/tavily.py - Brave Search → Provider Interface: uses shared client
api_pool/providers/brave.py - Firecrawl Search → Provider Interface: uses shared client
api_pool/providers/firecrawl.py - Parallel Search → Search Upstreams: requests search
api_pool/providers/parallel.py - Tavily Search → Search Upstreams: requests search
api_pool/providers/tavily.py - Brave Search → Search Upstreams: requests search
api_pool/providers/brave.py - Firecrawl Search → Search Upstreams: requests search
api_pool/providers/firecrawl.py - Date-Range Compatibility → SearXNG Service: patches date filtering
scripts/patch_time_range_engines.py