Why Kokoye?

Thirty-one miles.

That was the distance between us and a plate of Jamaican food on a Thursday afternoon when my wife,  born in Port-au-Prince, raised on the smell of diri kole and the particular percussion of a Haitian kitchen, said she wanted something from home. And if not from her home, exactly, something at least from the neighborhood of home. The Caribbean. Something that understood the pantry, the heat, the logic of seasoning.

We had recently moved closer to the San Diego area. We were hopeful. We searched.

Google returned nothing Haitian. Nothing Jamaican. At one point, nothing Caribbean at all, and then, in the blur of results that included places with no geographic or culinary relationship to the Caribbean whatsoever, a single Jamaican restaurant surfaced,  in Oceanside, California. Thirty-one miles away. We went. The food was worth every mile, and I mean that without sentiment: the jerk had that specific char-to-smoke ratio that lives in the wrist of whoever is working the drum, the rice and peas carried the full heft of coconut milk cooked down properly, and for a few hours we were somewhere that understood exactly what it was feeding us.

But I sat with something on the drive home that I could not put down.

I had seen this before. In every city I had lived in, there were restaurants like that one,  small, owner-operated, run by people who had brought the full weight of a culinary tradition with them and were quietly, stubbornly keeping it alive. Haitian spots that made legim the way it takes time to make legim. West African kitchens where the egusi had real depth, where the fufu had texture worth fighting with. Caribbean spots where the curry goat had been started the night before. These were not hobbyists. These were culture carriers, working in one of the hardest businesses in the world to stay alive in, one with razor-thin margins, brutal hours, and the particular vulnerability of being small and undercapitalized in a market that rewards scale.

And often they would disappear before anyone outside their immediate community even knew they existed.

Not because the food wasn't there. Because the infrastructure to find it wasn't.

Here is what I have come to understand about the way we search for food now: the tools we use were built for volume, not for meaning. Google will return 300 restaurants within a given radius. Yelp will give you stars and photographs. Both will show you what is popular, what is proximate, and what has been reviewed enough times to register as real. What they will not do, what they are structurally unable to do, is tell you which kitchen's pepper soup tastes like someone in it misses somewhere. They were not built to hold that kind of information. They were built for the general audience, and the general audience has never had to search for what it grew up eating.

The diaspora has. Always. And the search has always been the same: a group chat, a Facebook post, an auntie who knows somebody, a tip passed at a community event. This is not quaint. This is a survival network, and it has been doing extraordinary work for decades with no infrastructure underneath it at all.

That gap isn’t a niche. It’s the entire story.

The restaurants caught inside it are doing something that deserves more than algorithmic obscurity. They deserve to be found by the person who already knows what they're looking for and is not just searching for "food near me" but for something that a “generic search” can struggle to produce a result for. The person who will drive thirty-one miles and call it worth it. That person exists in enormous numbers, and they have been navigating a food discovery system that was never designed to see them.

What I have also come to understand is this: a restaurant that is only findable through Instagram or a Facebook group is not fully findable. Those platforms do real work within the communities they are already part of, but they are closed loops. They do not reach the person who has opted out of social media. They do not reach the next generation, aging into curiosity about the food their parents cooked. They do not provide the kind of stable, searchable presence that allows a small business to be discovered on a Tuesday by someone who didn't already know to look.

A restaurant that has no website and relies entirely on social posts for its presence is, in practical terms, invisible to a significant part of the people who would be its ideal customers. Not because the food is insufficient, but because the architecture of visibility is. And in a business where the difference between survival and closing down can be measured in how many new tables you turn in a month, that is not a small problem. It’s a question of survival. The cooks I am describing, the ones with the real knowledge, the ones who are making the food the way it should be made, who carry decades of technique in their hands,  they are rarely failing for lack of skill or love of craft. They are failing because they are spending every available hour feeding people, which leaves no hours for the kind of internet presence that, in this era, functions as the first handshake between a business and a stranger who might become a regular.

That specific gap, the one between an extraordinary kitchen and the audience that would cross cities to eat from it, is the space Kokoye was built to fill.

The name collapses something large into a single word, which is appropriate, because what Kokoye is trying to do is collapse a distance that has always felt too large: between the cook who kept the tradition and the diner who needs to find them, between the food that arrived here in someone's memory and the second generation trying to locate it in a city that has never served it, between the culture that a community carries and the infrastructure that makes that culture visible and survivable.

This is not food discovery as a flat, scrollable grid of results. It is food discovery that understands that every dish on a Haitian menu, every plate coming out of a Senegalese kitchen, every bowl produced in an Ethiopian spot in a strip mall,  and I use that phrase as the mark of honor it should be,  carries a specific cultural logic, a specific set of hands, a specific history that arrived here and stayed. And that each of those cooks, whatever the shared tradition they're working from, has their own signature inside it. The pepper sauce that’s unlike anyone else's pepper sauce. The particular spice balance that marks one kitchen as distinct from every other kitchen, making the same dish. That individuality is not incidental to what Kokoye surfaces,  it is the entire point.

The food of the diaspora isn’t only a category. It’s proof that a culture arrived here and did not dissolve. It is a familiar place that can be shared with the community that remembers it and with anyone ready to come to the table and understand something true.

What we’re building is a place where the people who keep the culture and traditions of our foods are not lost in the noise of “generic search”. A place where the search ends not just with a star rating from a stranger, but with the shared memories of a community that lives the culture.

That's the hunger no algorithm has learned to name. Kokoye was built by people who felt it.