English
LibreY Hosting
Search the web privately through a self-hosted metasearch front-end with no ads or tracking.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- ghcr.io/ahwxorg/librey:latest
- Default port
- 8080
How LibreY works
LibreY accepts a query through its web interface and retrieves result pages from several upstream search sources. The project can present ordinary web results and supports additional source types such as images and torrents depending on configuration and provider availability. Its own interface is deliberately simple and avoids a large client-side framework.
The application is a metasearch front end rather than an independent crawler or complete search index. Results depend on third-party providers, HTML structures, rate limits, regional behaviour, and anti-automation controls. When an upstream source changes or blocks a request, a result category can degrade until the project adapts its parser or configuration.
Key LibreY features
LibreY’s upstream project states that the application itself does not keep search logs, apart from logs that may be created by the web server or hosting environment. That distinction matters: the hosted service should not be described as eliminating every operational log, network record, provider request, or browser trace. Users also send queries through whichever upstream sources are selected.
The hosted package supplies the LibreY container without accounts, personalised history, a proprietary index, paid search APIs, proxy guarantees, content filtering administration, or assurance that every provider will remain reachable. Search quality and availability can vary across languages, regions, result types, and upstream changes.
Who uses LibreY
Privacy-conscious users can make LibreY a browser search page, while small teams may use it as a simple shared alternative for routine research. Developers can inspect how a minimal metasearch front end behaves, and educational groups can discuss the difference between a search interface and the providers supplying its results.
LibreY is not suitable when an organisation needs contractual search availability, enterprise content filtering, legal discovery, fixed source coverage, personalised recommendations, or a stable paid API. Important research should still verify primary sources because metasearch snippets can be stale, incomplete, or reordered by upstream services.
Self-hosting LibreY: requirements and cost
LibreY resource use grows with simultaneous searches, provider response latency, selected result categories, HTML parsing, image requests, and upstream retries. The catalogue records PostgreSQL and MariaDB as Not required and declares no persistent search index. Network activity and provider compatibility drive the workload more than application storage.
On AvaHost, LibreY uses Plan 1 at €2. The hosted LibreY package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. AvaHost provides the web application and normal platform services, but not a private search index or paid provider access. Upstream sources can throttle, block, or change without notice, and the page may expose normal web-server or infrastructure logs even though LibreY itself is designed not to keep query logs. No account history or personalisation is bundled.
F.A.Q
LibreY starts at €2 on Plan 1. Light personal or small-group searching fits the entry plan. Concurrent queries, slow upstream providers, image-result requests, retries, and source parsing can increase activity. A larger allocation may help a busy shared page, but it cannot prevent a third-party provider from changing or blocking responses.
A custom hostname can be connected with automated HTTPS for traffic between visitors and the hosted interface. Search requests still depend on the upstream sources LibreY contacts, and the domain does not create an independent index or provider contract. Review normal browser, network, web-server, and infrastructure logging before promising a particular privacy outcome.
LibreY parses and combines pages from external search providers. A provider can change markup, rate-limit requests, block an address, alter regional results, or retire an endpoint. AvaHost updates the application automatically, but it cannot control those upstream systems. Try another configured source and verify consequential information through primary websites when results appear incomplete.
The application package has no user-account history or relational search database. LibreY’s project describes the application as not logging searches, while noting that web-server logs may still exist. AvaHost does not promise the absence of infrastructure records, upstream provider logs, browser history, or network metadata, so assess privacy across the complete request path.