Why We Built Omnifetch

"Where do you find a new product made by a Turkish maker today?" There's no clean answer. A few Twitter circles, some Discord servers, the occasional Medium piece. Most products don't even make it that far — they get announced to the maker's immediate network, drift for a day or two, then vanish.

Omnifetch is built for that gap.

The invisible products

Anyone who's shipped knows the script. Months of code, demos shown to friends, a launch date picked. The day comes, a Twitter post goes out, a few likes trickle in, and that's it. Three days later the only proof your product exists is the open browser tab on your laptop.

What bothers us about this in Turkey isn't that the products are bad. It's that the good ones disappear the same way. Product Hunt is English-first and global; a Turkish maker can launch there, but reaching Turkish users isn't guaranteed. Local communities are fragmented. Tech press covers funded teams; it doesn't cover the dev who shipped a CLI tool over a weekend or a free Chrome extension that solved an actual annoyance.

The result: good products fail to find the right audience and quietly die. The maker walks away convinced shipping isn't worth it.

Why not just another Product Hunt?

The question we kept asking ourselves while designing this: "Are we just cloning Product Hunt?" The answer had to be no, otherwise there was no reason to build it.

Three things are different.

The /tr page surfaces only products made in Turkey; /en is the global feed. That single split makes "I want to look at SaaS made by Turkish founders today" a real workflow — something you can't do on Product Hunt.

Profile pages are not vote tallies. They're what you've made, the categories you publish in, the work behind a name. Turkey's maker ecosystem is still small enough that knowing the person carries about as much information as knowing the product.

New-product feed, community posts, and the blog all live under the same roof. Discovering a product isn't enough; the discussion around it, the trends in the ecosystem, the "wait, somebody built this?" reaction — they all belong in the same place.

Open source and transparency

Omnifetch itself isn't open source — for now. But the category system tries to be fair to projects that are: "Open Source" is its own product type rather than a sub-tag, because open-source projects shouldn't be measured on the same axis as VC-backed SaaS. Different goals, different community dynamics.

For sponsored placements: the outbound link gets rel="sponsored". The real reason isn't Google's signal — it's that readers should be able to tell editorial picks from paid ones at a glance. Trust in this ecosystem has eroded enough; whatever scale, the small thing that breaks it is worse than the small thing that protects it.

Who is this for?

The maker first: weekend project or full-time startup, the thing you made should be discoverable. Submitting takes two minutes; in return you get a categorised, indexable home page for your project.

Then the curious user or researcher: someone asking "what AI tools have Turkish makers built?" can scan the category page in thirty seconds.

Finally the editor or analyst: bloggers writing year-end roundups, researchers doing ecosystem work, VCs sourcing deals — all need a single place to query.

What we expect to work, and what we don't know yet

The platform is new. We have hypotheses, but framing them as "data" wouldn't be honest:

We expect community posts to fill faster than the product feed because the friction is lower; whether that holds we'll see in a few months. The trending sort is based on 7-day vote counts, so until enough votes accumulate it'll look similar to the main feed — that's the math, not a bug. Category pages are thin at launch; the blog exists partly to fill them. This article is part of that opening.

Things we plan to build but haven't yet: founder interviews, an API for third-party clients, a curator program for active collection-builders. They're on the roadmap; we'd rather not commit to dates we'd miss.

If you're shipping something — small or large — share it via /submit. If you're here to discover, browse the categories.