About
Kismet started with one ruined dinner plan and a coin that had no answers. Here's the story, the philosophy, and the small team letting fate decide.
Kismet started the way these things always start: six friends, ninety minutes of “I’m easy, you pick,” and a dinner that never happened.
The insight
Groups don’t fail to decide because they lack options — they fail because deciding has social cost. Whoever picks owns the outcome. If the restaurant is mid, it’s your fault. So everyone defers, the loudest voice wins or nobody does, and the group chat scrolls into oblivion.
Randomness fixes the cost. If fate picks, nobody owns the outcome — and everyone gets to want something again. But a coin flip in a group chat has no ceremony, no fairness anyone can trust, and no commitment attached. It needed to be an event.
The ritual
So we built the ritual: hidden picks (so wanting something is safe), a sealed lock (so the suspense is real), a server-side draw (so the fairness is provable), a synchronized reveal (so the moment is shared), and the pact — no take-backs (so the decision actually sticks). Every feature in Kismet exists to protect one of those five beats.
“Fate,” in this house
The answer ball isn’t mysticism — it’s a game mechanic with good manners. Fate is the name we give the referee everyone can trust: perfectly random, impossible to lobby, immune to being blamed. The ball just gives it a face worth watching.
The team
Kismet is built by a tiny team that takes indecision personally — native on iOS and Android, with a full guest experience on the web, because the whole crew counts even when half of them won’t download anything.
Have a story about a fate you accepted? We collect them.