The itch that started it
I kept ending up in the same spot: something would happen — a hot take, a weird news story, a trending debate — and I'd have nowhere that felt right to talk about it. Group chats die fast. Twitter/X feels like shouting into a stadium. Facebook feels like your relatives are watching. Reddit is great, but it's not built for us specifically — the way we talk, the things we care about, the language we switch in and out of.
So I did what a lot of us do when something doesn't exist yet: I got annoyed enough to build it myself.
That's Sajha. Sajha means "shared" or "common" — and that's really the whole pitch. One shared front page. Everyone's takes. No filters, no performing.
What I was trying to build
Not another feed. Feeds are for scrolling past things. I wanted threads — actual conversations, with actual disagreement, that don't die after four replies.
The core mechanic I kept coming back to was voting, but I didn't want a boring upvote/downvote. I wanted something that matched how we already talk. So: Flame it if a take is fire, Cool it if it needs to sit down. Same mechanic Reddit popularized, different language — ours.
The build
Stack-wise, I kept it deliberately boring where it didn't matter and careful where it did:
WordPress as the core CMS/backend — not the trendiest choice for a "forum" product, but it's fast to iterate on, has a mature plugin ecosystem for auth/comments/moderation tooling, and meant I wasn't reinventing account systems and page management from scratch.
A custom theme built around communities, threads, and the flame/cool voting system — this is where most of the actual product work went. Vote counts, community subscriptions, trending logic, all custom.
Kept the frontend fast and minimal — no bloated JS, no dark patterns, no infinite auto-refresh feed designed to trap you.
The hardest part wasn't the code. It was deciding what not to build in v1. I cut a notification system, a full DM/messaging feature, and karma/reputation scoring — all things that seemed core but weren't actually needed to test the real question: will people show up and talk?
What I learned building alone
Ship the mechanic, not the polish. Flame/Cool needed to work and feel good before anything else mattered. Everything else was secondary.
Naming things matters more than I expected. Calling it "Flame it / Cool it" instead of "upvote/downvote" changed how the whole product felt — it stopped feeling like a Reddit clone and started feeling like its own thing.
Writing your own Terms of Service, Privacy Policy, and Community Guidelines is genuinely a lot of work that nobody warns you about before you launch a community platform. Legal/trust groundwork ate more time than I expected.
Where it's at now
Sajha is live at sajha.xyz. It's early — communities are just forming, threads are just starting — which honestly is the fun part. Every platform that ended up mattering had a moment where it was just a handful of people posting into the void, hoping someone would answer.
Why I'm posting this here
I'm not trying to make this a big launch post. I just wanted to talk through the actual build with people who'd get it — the tradeoffs, the stack choices, the "why did I cut that feature" decisions.
If you're into community platforms, forum mechanics, or just want to see what a solo-built Reddit-style platform looks like from the inside — I'd genuinely love feedback. And if you've got a hot take that's been sitting in your drafts with nowhere to go — that's exactly what Sajha's for. Come say it.
sajha.xyz — say it, don't stay quiet.
Top comments (0)