Skip to content
kchakhabarehकेखबर

About

What K cha khabar is, and isn’t.

A Nepal news intelligence platform. We pull headlines every few minutes from 35+ Nepali and English publishers, cluster them into stories using multilingual AI, generate bilingual summaries, and surface trending topics — with full ownership transparency on every source. Framing comparison and coverage maps are what we’re building toward.

The name

के छ खबर? It’s the first thing a Nepali asks when they pick up the phone — K cha khabar? What’s the news? What’s going on? The phrase sits somewhere between a greeting and a genuine request for a briefing. That’s exactly what this site is: a daily answer to that question, pulled from every major publisher so you don’t have to ask it twenty times yourself.

The problem

Abundance without aggregation

Nepal has 45+ digital news publishers and no layer above them. The same story is told a dozen times a day with different facts, framings, and emphases. A reader who wants a credible picture of the day ends up visiting five sites in two scripts — or gives up and scrolls Facebook.

The cost falls hardest on the diaspora. More than 1.5 million Nepalis live outside Nepal, and they are both the most engaged and the most poorly served audience for Nepal news. K cha khabar is built for them first, and for engaged in-country readers and researchers second.

Who it's for

Three readers, one dashboard

  • Diaspora

    Nepalis in Australia, the US, the UK and the Gulf who want the day's Nepal news in five minutes, in English or Nepali.

  • In-country

    Politically aware readers in Nepal who already follow two publishers and want to see what the other twenty are saying.

  • Researchers

    Journalists, academics, and NGOs who need structured, reproducible data on how Nepal's media ecosystem is covering a topic.

Today

What works right now

The intelligence layer is live. On top of the raw feed, four features already set us apart from a plain aggregator:

  • AI-clustered stories. Nepali and English articles about the same event are grouped into a single story using multilingual embeddings (BGE-M3). Browse by story on the stories page or see breaking stories as they cluster.
  • Bilingual story summaries. Each story gets an AI-generated summary in both Nepali and English, labelled as AI and citing only contributing articles. No facts are added that no source supports.
  • Trending topics. Named entities — people, places, organisations — are extracted from every article and ranked by velocity. Browse by topic on the topics page.
  • Ownership transparency. Every headline is tagged with its publisher’s ownership type — state-owned, private, independent, or non-profit. Publisher profiles carry the full picture: founded year, headquarters, editorial stance, paywall model, legal contact.

Reading is public and does not require an account. The pipeline — ingestion, embedding, clustering, summarisation, rendering — runs on scheduled jobs outside Nepal. Walk through each stage →

Languages

Nepali and English, at parity

The majority of Nepal’s news is published in Devanagari. Second-generation diaspora and many researchers read English more fluently. Both scripts are treated as first-class: headlines render in their native script, and story summaries are generated in both Nepali and English. Topic labels are bilingual. The language toggle persists across sessions.

Non-goals

What we don't do

  • We do not republish full article bodies. We store headlines, timestamps, and short excerpts, and every cluster links back to the publisher’s page.
  • We do not crawl sites that disallow our User-Agent in robots.txt, or publishers that explicitly prohibit aggregation.
  • We do not host comments or user-submitted content. Moderating Nepal-scale discourse is a separate product.
  • We do not ingest social media in v1. Reddit, X and Facebook signals are deferred.
  • We do not run ads, paywalls, or subscriptions at launch. The goal is trust, not revenue.
  • AI summaries are always labelled as such, cite only contributing articles, and do not assert facts that no source supports.

Coming soon

What's next

Cross-lingual clustering, story summaries, and trending topics are live. The next layer:

  • Framing comparison. Side-by-side views of how different publishers are telling the same story, with factual disagreements called out rather than blended away.
  • Coverage map. For each story, which publishers covered it and which didn’t — so single-source stories don’t masquerade as broadly reported ones.
  • Weekly digest. Top stories, framing highlights, and likely coverage gaps — the primary artefact for the current- affairs podcast this app exists to support.

Further out: a native mobile app, social-signal ingestion (Reddit, X), coverage-bias scoring per publisher, and embeddable story widgets.

The builder

A one-person engineering team

K cha khabar is designed, built and operated by Bishal, an engineer in Melbourne. Every line of ingestion code, every SQL query behind the feed, and every pixel of this page. No team, no investors, no sponsors.

The app exists in support of a weekly Nepali current-affairs podcast co-hosted with Subodh Kharel. That gives it a built-in editorial dogfood loop — every Friday the tool gets stress-tested against the week’s real news.

All infrastructure runs outside Nepal. That is a deliberate regulatory posture.

Takedowns & partnerships

Publishers, rights holders, and collaborators

K cha khabar is a product of Outback Yak and is governed by the same terms and privacy policy as the rest of the Outback Yak portfolio.

For takedown or delisting requests, ownership/editorial metadata corrections, partnerships (data licensing, research collaborations, editorial cooperation), or any other enquiry, email:

[email protected]

We aim to respond within 72 hours.

Next

Start reading, or explore what’s live.

Browse the live feed, read today’s stories, browse topics, or see who we track.

About · K cha khabar