For the people whose
name runs past the
end of the film.

1. 01

   Self declared

   self_declared

   You add the credit to your profile. Visible, claimed, not yet verified. The lowest tier and an honest starting point.
2. 02

   Peer confirmed

   peer_confirmed

   A co-worker on the same project affirms the credit. Two of the same and the badge upgrades.
3. 03

   Production verified

   production_verified

   The producer or a designated production lead attests inside the Projects service. The credit attaches to a real project record.
4. 04

   Payment verified

   payment_verified

   A payout clears to you, for that project, verified against an HMAC-SHA256 signed webhook. The credit is now a film credit you can prove, and Rating BD picks it up on the next sync.

Scroll for full table

01What is Kuhok?

Kuhok is a dignity-first network for the film and television industry, launching first in Bangladesh. It bundles five capabilities into one product: IMDB-style public profiles for every crew role, AI-guided production management for scripts, schedules, contracts, and budgets, cashless payouts that automatically promote credits to payment-verified, Project Family Groups for the people on a shoot, and built-in safety reporting. Kuhok is a KaritKarma product and is live at kuhok.net.

02How is Kuhok different from IMDB, LinkedIn, or Facebook for crew?

IMDB is closed to most working crew. LinkedIn does not understand a call sheet. Facebook is a personal profile with no audit trail and no concept of a payment-verified credit. Kuhok was built around the credit graph itself, so light boys, drivers, and caterers get the same profile structure as a lead actor, at a public root handle like kuhok.net/yourname, and a credit only earns its highest verification level when a real payout clears.

03What does payment-verified credit actually mean?

Every Kuhok credit moves through four WorkProof levels in sequence: self_declared when you add it, peer_confirmed when a co-worker affirms it, production_verified when the producer attests to it, and payment_verified when a payout to that person on that project clears. Payment webhooks are verified with an HMAC-SHA256 signature over timestamp.payload, constant-time comparison, and a 300-second replay window. The credit on your profile reflects the highest level you have actually reached: a film credit you can prove.

04How does Kuhok protect cast and crew from harassment?

Three rails. First, growth is invite-only through invite codes, attribution claims, or Rating BD profile claims, so there is no anonymous-signup attack surface. Second, public profiles do not expose direct messaging from producers to artists, so all collaboration happens inside a Project Family Group with a record. Third, the Safety service accepts reports with severity and evidence URLs, and an admin review queue moves each one through a four-state workflow: open, in_review, closed, escalated.

05Where is Kuhok in production today?

Live at kuhok.net. The platform runs 14 .NET 10 microservices behind a YARP gateway with 19 routes and Darwan RBAC at the route level, a Next.js 16 frontend, PostgreSQL with pgvector for 768-dimension embeddings, Redis, RabbitMQ, S3-compatible object storage for assets, and dual LLM backends: a hosted provider plus a local Ollama runtime.

06How does Kuhok connect to Rating BD?

Kuhok and Rating BD share the same identity and authorization spine (Wenme for auth, Darwan for permissions). The interesting link is bidirectional: when Kuhok verifies a credit through payment, that credit is pushed into Rating's Person and Appearance graph as ground truth through a dedicated gateway route and client library. Rating computes PPS (Person Popularity Score) and pushes it back to display on the Kuhok profile, so casting decisions reference market signal without leaving Kuhok.