Websurfx

Aggregate results from other search engines (metasearch engine) without ads while keeping privacy and security in mind. It is extremely fast and provides a high level of customization (alternative to SearX).

Slowing · 37
37/100
Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 9/40
Releases 21/25
Community 8/20
Momentum 0/15

Commit activity more than 22% of tracked projects; popularity more than 38%. How this is calculated.

Commits, last 11 months

2025-10: 1 commits 2025-11: 0 commits 2025-12: 1 commits 2026-01: 9 commits 2026-02: 15 commits 2026-03: 16 commits 2026-04: 14 commits 2026-05: 9 commits 2026-06: 0 commits 2026-07: 0 commits 2026-08: 0 commits
2025-10 65 total 2026-08
Stars1.2k
Latest releasev1.29.9 · 13 May 2026
Repo updated13 May 2026
LicenceAGPL-3.0
Built withRust, Docker

Is Websurfx actively maintained?

Websurfx logged 65 commits over the last 11 months, but none in the most recent quarter. Development has paused rather than stopped outright — worth watching before a production deployment.

The most recent tagged release, v1.29.9, is about 5 months old.

Note that Websurfx depends on a third-party service to work fully. It is self-hosted, but not self-contained: if that external service changes its terms or disappears, your instance is affected.

Websurfx ranks #13 of 16 tracked search engines projects. Several better-maintained options exist in the same category — they are listed below.

What Websurfx actually does

Websurfx is an open-source metasearch engine written in Rust that queries multiple upstream search providers simultaneously. It strips out advertisements and telemetry to return aggregated results with a focus on user privacy. It serves as a direct alternative to platforms like SearX.

Best fit: It suits self-hosters who want to bypass commercial search engine tracking and advertising while maintaining a lightweight infrastructure.

Worth knowing: The project overlaps heavily with the more mature and widely adopted SearXNG, and upstream changes to target search engines can occasionally break result parsing.

Deployment notes

As a containerised Rust application, you will typically deploy it via Docker behind a reverse proxy to handle TLS termination, with minimal persistent storage requirements as it generally does not rely on a separate database.


Alternatives to Websurfx

Projects in the same categories, ordered by health score.