My independent search engine focused on user control
I've always been frustrated with search engines. Google used to be the one I always used, but it's now completely overrun with ads and AI Overview. Alternatives like Mojeek, Marginalia, DuckDuckGo, or Startpage don't seem to give me the results I'm looking for. What's even worse is that search engines like DuckDuckGo, Startpage, and Ecosia are using AI Overviews too. These features ARE optional, but I still felt annoyed that I had to opt out of everything. This is why I created my search engine Slick. Slick is an independent search engine with its own index. It aims to be everything users…
What it does
In the maker’s words, at launch
I've always been frustrated with search engines. Google used to be the one I always used, but it's now completely overrun with ads and AI Overview. Alternatives like Mojeek, Marginalia, DuckDuckGo, or Startpage don't seem to give me the results I'm looking for. What's even worse is that search engines like DuckDuckGo, Startpage, and Ecosia are using AI Overviews too. These features ARE optional, but I still felt annoyed that I had to opt out of everything. This is why I created my search engine Slick. Slick is an independent search engine with its own index. It aims to be everything users want from a search engine, whether that's privacy, speed, transparency, or customization. We aim to let users have full control over their search engine. Currently, we have implemented this using custom per-domain ranking (similar to Kagi) and custom bangs (DuckDuckGo bangs, but faster and with the ability to add your own). For revenue, we WILL be using ads in the future, but we want to approach them differently. The ads are intentionally made very visible (bright yellow text, bigger font, etc) instead of using a tiny "sponsored" label. Ads will only be visible on the first page, and there is a maximum of 1 ad per page instead of Google's 1-4. We are also experimenting with keeping the ads in the actual search results, and I would really like your feedback on this. Since the ads are very visible, instead of forcing them to the very top, we rank them similarly to normal results (with a slight boost so they stay on the first page). The idea is that if an ad is shown, it should at least already be relevant to your query. Now I'm not going to make the mistake of claiming "privacy" like I did in my Reddit post. Not because Slick isn't private, but because it's not open source and users currently have no way to verify what we say. We want users to feel safe when searching, which is why we want to eventually invest into audits regularly once the project is in a more stable position. I've only been listing good things about Slick so far, so now it's time for the issues Slick is currently facing for full transparency. Slick's major issues right now are result quality and speed. When I say bad result quality, I don't mean bad ranking. I've made a detailed overview of Slick's ranking in our blog pasted below. The issue mainly comes from our small index. Since we're a completely independent search engine, we have to do all of the crawling ourselves. Our web index is currently only around 2.5 million documents, although it is slowly growing. The second issue is speed. This is something we are actively working to fix, but we are heavily limited by infrastructure. Slick isn't running on a massive server, or even a good PC. We are currently running on a Beelink EQR5, which is suboptimal (suboptimal may be an understatement). These are only the issues I've personally noticed so far, but there are probably many more. I posted Slick on Reddit a while back, but I didn't get exactly what I was hoping for. A lot of people told me that if the search engine was truly private, they would need the source code. That's part of why I've decided not to lean too heavily into privacy claims on this HN post. I would really like your ideas, critiques, bug reports, and feedback on Slick. We hope you can support our endeavour to build a search engine that puts users first. Blog: https://blog.slicksearchhq.com Search Engine: https://slicksearchhq.com Reddit: https://reddit.com/r/SlickSearchHQ
Does the same job
all alternatives →
- IBI built a 2B-page search engine, independent of Google/Bing2025 · ▲8
Hi HN, For the last 18 months, I've been working solo on building a completely independent search engine from scratch. Today, I'm opening it up for beta testing and would love to get your feedback. The project powers two public sites from the same 2-billion-page index: Searcha.Page: A session-aware search engine that uses a persistent browser key (not a cookie) for better context. Seek.Ninja: A 100% stateless, privacy-first version with no identifiers at all. The entire stack is self-hosted on a single ~$4k bare-metal EPYC server in my laundry room (no cloud, no VC funding). The search…
- IMI made a better interface for Google Tasks and I can't go back2011 · gtasker.com · ▲122
I recently decided to try out Google Tasks as my only task management system, and while I find some things about the interface great, it really isn't suited for someone like me who has multiple lists with lots of elements on each. So, I whipped this together real fast and I can't imagine using Google Tasks without it anymore. I realized you might want it too, so I put it on the web. Enjoy :)
- IMI'm Building Ahrefs for AI Search Results2025 · linrush.com · ▲9
AI search results are quickly becoming more important than SEO, but as businesses, we have no visibility over it! That's why I'm building "Ahrefs for AI search results". Track keyword performance on AI tools like ChatGPT, Claude, Perplexity & more
- RARunnaroo – A new web search engine2020 · ▲20
In the sprit of releasing to the public early, I would like to share a search engine/portal I have been building in my spare time: https://www.runnaroo.com Why: I started to not be able to easily tell the different between ads and organic search results in other search engines (even on DuckDuckGo), and I have been disappointed with recent UI changes in a lot of the major search engines. My main guiding rule when adding features has been to ask, "is it better for the user?" Important to know: I still believe Google currently returns the most relevant web results, so like…
- POPriEco (open source, 400M index, EU search engine) integrated GogglesJul 2026 · prieco.net · ▲6
Back in 2021 I wanted to switch away from Google and try alternatives. To my disappointment they were... not great. I took a way of comparing qualities and disadvantages of each web search engine back then. What I discovered I cared about the most was privacy (like DuckDuckGo), ecology (Ecosia) and Google index (likely to signal quality of results, Startpage). To my disappointment there wasn't a single one that I could find that offered all 3 of these qualities. After a long time of deciding if and how I could build my own web search engine I decided to do it. At first, for 4 years, it was…
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, May 2026
the whole month →
Parallel agents, diff reviewer, and multi-model comparisons
Dev tools · May 2026 · kilo.ai
- NW
Hey HN, Henry here from Cactus. We open-sourced Needle, a 26M parameter function-calling (tool use) model. It runs at 6000 tok/s prefill and 1200 tok/s decode on consumer devices. We were always frustrated by the little effort made towards building agentic models that run on budget phones, so we conducted investigations that led to an observation: agentic experiences are built upon tool calling, and massive models are overkill for it. Tool calling is fundamentally retrieval-and-assembly (match query to tool name, extract argument values, emit JSON), not reasoning. Cross-attention…
Life & fun · May 2026 · github.com
- FM
Dev tools · May 2026 · github.com