|
| 1 | +--- |
| 2 | +type: post |
| 3 | +title: Introducing Search Engine Adapter |
| 4 | +author: Andrew Wray |
| 5 | +subtitle: One URL for Google, ChatGPT, and Wikipedia |
| 6 | +summary: SEA routes search queries to different services with nginx. |
| 7 | +date: 2025-07-07 |
| 8 | +tags: ["sea", "nginx", "search"] |
| 9 | +--- |
| 10 | + |
| 11 | +Our [previous post](/blog/post/2025-06-01-chatgpt-default-search-engine/) |
| 12 | +explained how to make ChatGPT your search engine. |
| 13 | + |
| 14 | + |
| 15 | +[Search Engine Adapter (SEA)](https://github.com/dense-analysis/sea) |
| 16 | +builds on that idea. |
| 17 | + |
| 18 | +SEA is a lightweight nginx proxy that chooses between Google, the ChatGPT API, |
| 19 | +or Wikipedia based on keywords in your query. |
| 20 | +It compiles nginx config files from a simple TOML source using Go, resulting in |
| 21 | +a small and secure deployment. |
| 22 | + |
| 23 | +## Key Features |
| 24 | + |
| 25 | +* Dynamic keyword routing with nginx's `map` directive. |
| 26 | +* One HTTPS endpoint easily secured with Let's Encrypt. |
| 27 | +* Minimal dependencies and small attack surface. |
| 28 | + |
| 29 | +You can configure SEA using `config-example.toml`, then compile the final |
| 30 | +`nginx.conf`. Once deployed, every search is forwarded to the matching service. |
| 31 | + |
| 32 | +A live instance is available at |
| 33 | +[https://search.denseanalysis.org/?q=%s](https://search.denseanalysis.org/?q=who+is+w0rp+and+what+is+ALE) |
| 34 | +for anyone who wants to try it. The instance does not log any access or error |
| 35 | +logs, so Dense Analysis pledges not to spy on your searches, but don't trust us. |
| 36 | +The configuration and program to make it are available on |
| 37 | +[GitHub](https://github.com/dense-analysis/sea), and you may deploy your own |
| 38 | +instance locally, remotely, or wherever you want. We welcome feedback and |
| 39 | +contributions! |
0 commit comments