About Kahoo

The idea

Most of the internet shows you people who are like you — the same country, the same language, the same argument you were having yesterday. Kahoo does the opposite. One window, one stranger, one conversation, and then it is gone.

That only works if two things are true: leaving has to be effortless, and behaving badly has to have consequences. Everything else in the product follows from those two.

How it is built

• Astro for the pages you are reading — static HTML, almost no JavaScript.
• Cloudflare Workers for the API.
• Durable Objects for presence, matchmaking and signalling. One single-threaded coordinator is why two people can never be handed the same partner.
• D1 for accounts, guest allowances, moderation and analytics.
• WebRTC for the call itself, browser to browser, never through us.

The whole thing is designed to run on free tiers. That is not a boast about frugality — it is a constraint that keeps the architecture honest and the privacy promises cheap to keep.

What we deliberately did not build

• No call monitoring. There is no administrator screen that shows a live conversation, because building one would betray every person on the platform.
• No recordings and no transcripts. Not for safety, not for training, not for anything.
• No invasive fingerprinting. Guest limits key on an identity our server issues, not on a canvas hash of your device.
• No fake numbers. The online count is real. When it says zero, it is zero.

Where it is going

Kahoo is early. The roadmap is written down honestly, including the parts that are not built yet and the parts that would cost money to run. If you want to know what is coming, the shortest answer is: better matching, better moderation, and mobile.

Getting in touch

Safety issues, bugs, and anything else: the contact page has the addresses. Reports about behaviour are always better filed in the app, because that attaches the session to the case.