Skip to content
Case Studies

Architecture, customers,
real numbers.

Two published case studies. Every metric is sourced from the product repository or a named live customer. No invented growth charts, no inflated deployments.

2
Published case studies
NewsForge, Kuhok
848
Go tests in NewsForge
All-Go rebuild, 8 services
14
Microservices in Kuhok
.NET 10 behind YARP + Darwan
10
NewsForge channels
CMS plus social publish targets
What is the KaritKarma case studies index

A short, honest reference for how products ship on this platform.

The KaritKarma case studies index lists every product whose architecture and customer status we are prepared to defend in a technical briefing. Two studies are published today: NewsForge for autonomous newsroom operations, and Kuhok for the dignity-first film network.

Each case study is grounded in the product repository at the date of publication. Live-customer claims are named only with permission, pilot and production-ready states are labelled separately from named-live states, and superseded claims are corrected rather than quietly kept. If a metric is dated, it carries the date.

The two studies

One platform. Two very different products.

01/ NewsForge

How NewsForge Synthesizes One Original Story from Many Sources

All-Go newsroom platform. Vector-embedding clustering of duplicate coverage, LLM synthesis behind an n-gram originality guard, mandatory human editorial review, and publishing to 10 CMS and social channels.

Read the NewsForge case study
6
Lifecycle States
10
Publishing Channels
8
Services
848
Go Tests
02/ Kuhok

14 Microservices Powering the Bangladesh Film Industry Credit Graph

14 .NET microservices behind a payment-verified credits ladder for Bangladesh film and television. YARP gateway with Darwan RBAC per route, Rating BD bidirectional bridge.

Read the Kuhok case study
14
Microservices
10
AI Endpoints
4
WorkProof Steps
Rating BD
Bridge Integration

What we do not publish

Honesty bar for case studies.

We refuse a few categories of claim that have become standard in SaaS marketing. Each one is here so a buyer knows what to expect (and what to verify) before signing.

Architecture diagrams sourced from the live repository
Instead of: Architecture diagrams drawn for the case study with no code reference
Test counts and microservice counts taken from the source tree on a dated commit
Instead of: Round-number metrics with no traceable source
Named customers only with written permission
Instead of: Anonymous logos or stock-image customer collages
Latency budgets with stage-by-stage breakdown
Instead of: Latency claims with no stage attribution
Pilot, beta, and production-ready states labelled separately
Instead of: Pilot deployments cited as production wins

Frequently asked

Case studies, asked plainly.

Six answers we have written down so a briefing call does not spend ten minutes on definitions.

What case studies does KaritKarma publish?
KaritKarma publishes two technical case studies that cover two different verticals. (1) NewsForge, the AI synthesis newsroom, is an all-Go platform (Go 1.26, PostgreSQL 18 with pgvector, NATS JetStream) that clusters multi-source coverage, synthesizes one original article per story, and publishes to 10 CMS and social channels after human editorial approval. (2) Kuhok, the dignity-first network for cast and crew, runs 14 .NET microservices behind a YARP gateway with Darwan RBAC enforced per route and is live at kuhok.net. Each case study documents the architecture, the integrations, and the shipped customer status.
Are KaritKarma case study customers real production deployments?
Customer status varies and we label each case honestly. Kuhok is live at kuhok.net. NewsForge's first generation ran the Bengali-first portal khoboria.com as its founding deployment; the platform has since been rebuilt as an all-Go stack, deployed at newsforge.news, with first-tenant onboarding in progress, so we do not present khoboria as a current-stack customer. We do not promote pilot deployments to general availability claims and we name customers only with explicit permission.
Which KaritKarma platform services do the case study products integrate?
The integration surface differs per product, and we state it exactly. Kuhok integrates Wenme for OAuth sign-in through a dedicated identity adapter, Darwan for route-level authorization across its services, and a bidirectional Rating BD bridge for talent verification. NewsForge validates Wenme-issued OAuth 2.1 JWTs, authorizes through Darwan, and ships a media client built to store assets by reference in Foveio, KaritKarma's media layer, with per-channel renditions (live as Foveio launches). We publish the integration surface rather than papering over it.
How long does it take to ship a product on the KaritKarma platform?
Platform reuse is the lever where it applies. Kuhok shipped 14 microservices behind a YARP gateway with a Next.js 16 frontend by inheriting Wenme identity and Darwan route authorization instead of building them. NewsForge's all-Go rebuild ships 8 services with 848 Go test functions, a synthesize-once, localize-on-demand pipeline, and 10 publishing connectors registered at boot.
Can I see the source data behind a case study claim?
Yes. Every numerical claim on a case study page (test counts, microservice counts, latency budgets, connector counts) is sourced from the product repository at the date of publication. Counts that depend on a live system (uptime, customer counts, publish volumes) are dated and are refreshed when we update the case. If you need a verifiable reference before signing a contract, we walk the architecture and the relevant repository views in a 30-minute technical briefing.
Where do KaritKarma case study products run?
All KaritKarma-operated infrastructure runs on hardware physically owned inside Bangladesh, in a Tier-3 data center on AS 64005 as an APNIC member. NewsForge runs on KaritKarma infrastructure at newsforge.news. Kuhok runs on KaritKarma infrastructure and serves kuhok.net.

Build With Us

Your product could be next.

The same platform services that power these products are available for your next build. Shared auth, authorization, communications, and storage. You keep the domain logic.

Talk to UsView All Products