For the people whose
name runs past the
end of the film.
Kuhok gives every crew member, light boys and drivers included, a public profile, a verifiable credit, a contract that gets signed before set, and a payout that clears without a producer's pocket. Built dignity-first in Dhaka.
- Live
- kuhok.net
- Auth
- Wenme + PKCE
- Stack
- .NET 10, Next 16
- Region
- BD-first, global
- SubjectsCast, crew, light boys, drivers
- IdentityIMDB-style, public
- Sign-inWenme OAuth 2.1 + PKCE
- Credit heroPayment-verified WorkProof
- PayoutsLoneSock Pay, HMAC webhooks
- SafetyInvite-only + audited reports
What is Kuhok?
Kuhok is a dignity-first network for film and TV crews. It bundles an IMDB-style identity layer, AI-guided production management, cashless payouts that promote credits to payment-verified, and Project Family Groups built around the shoot, not around the feed.
It is a KaritKarma product, live at kuhok.net. Wenme handles authentication. Darwan handles authorisation at the YARP gateway. LoneSock Pay handles payouts. BitsPath handles messaging. The profile graph, the credit-verification pipeline, the AI-led script breakdown, the contract workflow, and the safety reporting are the Kuhok team's own work.
Built for the people the credits used to forget.
Five functions in one network. Profile, Studio, Pay, Social, Safety. Every interaction has an audit trail. No public DMs. No anonymous accounts. No after-the-fact contracts.
An identity that survives the wrap.
IMDB-style public pages for every crew member, including light boys, drivers, and caterers. Avatar history, banner attribution, portfolio gallery, designations, skills, photographer-credit invitations for off-platform collaborators. Profiles cache on the API edge so cold loads finish before the credits scroll.
AI-guided production management.
Projects, scenes, shots, shooting days, contracts, budgets, calendars. The AI service breaks down a script, drafts a feasibility plan tuned for Dhaka traffic and monsoon, and suggests crew from a 768-dim semantic index. Budget changes broadcast over SignalR so the line producer sees them mid-meeting.
Cashless payouts, payment-verified credits.
LoneSock Pay handles the payout with HMAC-signed webhooks and a five-minute clock-skew tolerance. When a payment clears, the credit on your profile is automatically promoted to payment_verified, the highest WorkProof level. The members tier opens a 5,000 BDT emergency credit line via CityBank.
Project Family Groups, not public DMs.
Auto-created groups bind every project's cast and crew. Posts with multi-image grids, stories with 24-hour TTL, albums with EXIF, an On This Day memory engine. Producers cannot DM artists from a public profile. Every interaction is audited.
Every credit climbs a four-step ladder.
You say it. A peer says it. The producer attests to it. The payout clears. Only the last step earns the highest WorkProof badge, and only that badge is the credit Rating BD pulls into its Person graph as ground truth.
- 01
Self declared
self_declaredYou add the credit to your profile. Visible, claimed, not yet verified. The lowest tier and an honest starting point.
- 02
Peer confirmed
peer_confirmedA co-worker on the same project affirms the credit. Two of the same and the badge upgrades.
- 03
Production verified
production_verifiedThe producer or a designated production lead attests inside the Projects service. The credit attaches to a real project record.
- 04
Payment verified
payment_verifiedA LoneSock Pay payout clears to you, for that project, against an HMAC-signed webhook. The credit is now ground truth, and Rating BD picks it up on the next sync.
Dignity-first is a system, not a slogan.
Four guardrails decide what is possible on Kuhok. Each one is a shipped piece of the platform, not a future intention.
Invite-only growth
Three entry paths: invite code at /join/CODE, attribution claim at /claim/TOKEN, Rating BD profile claim. Anonymous signup is closed. The inviter shows on the join page before the OAuth bounce.
Anti-harassment by design
No direct producer-to-artist messages from a public profile. The Safety service ingests reports with four categories, severity levels, and an open / in_review / closed / escalated workflow with evidence URLs.
Contracts before set
Multi-party signing through draft, pending_crew, signed, rendered to PDF with QuestPDF and stored on MinIO. The producer signs first, the crew signs next, the document is sealed, no after-the-fact edits.
Photographer attribution
Every banner, portfolio image, and post attachment can credit a name, email, or person ID. Off-platform photographers receive a claim invitation. Two-way attribution that pays the credit back to the person who took the picture.
Four surfaces a production team actually uses.
Not a feature list. Four daily-use surfaces, each behind the YARP gateway with Darwan RBAC enforced per HTTP method.
Script intake
01Drop a PDF. Regex scene and character extraction, then a Groq Llama 3.3 70B pass for feasibility. The plan accounts for Dhaka traffic, Eid and Puja windows, and monsoon shoots.
Schedule + call sheets
02Personal calendar with conflict detection, project-day links, and PDF call sheets rendered through QuestPDF. Default availability is Sun to Thu, 9 to 18, Asia/Dhaka.
Rating BD bridge
03Verified Kuhok credits flow into Rating's Person and Appearance graph. PPS scores flow back onto Kuhok profiles. One bidirectional loop, two products, zero re-entry.
Crew suggestions
04Semantic match scores from 0 to 100 over a 768-dim index, background-refreshed every 30 seconds in batches of ten. Cold-start handled by a keyword fallback over ILIKE.
Kuhok vs IMDB vs Facebook vs a spreadsheet.
Productions in Bangladesh triangulate today, a Facebook group for the WhatsApp-adjacent stuff, an IMDB page for the marquee names, and a spreadsheet for the cash. Kuhok holds all of that in one auditable place, with the crew members the other tools forget.
| Capability | Kuhok | IMDB | Spreadsheet | |
|---|---|---|---|---|
| Crew profile system | Public IMDB-style | Restricted to industry pro | Personal profile | Manual |
| Payment-verified credits | ||||
| Contracts before work | ||||
| Anti-harassment protocols | Reports, no audit | |||
| AI script breakdown | ||||
| Cashless payouts | ||||
| Semantic crew search | 768-dim pgvector | Name search only | ||
| Public profile for non-marquee crew | Drivers, light boys, caterers | Marquee only | Personal profile |
Standing on the same shared spine as the rest of KaritKarma.
Wenme for sign-in. Darwan for access control. LoneSock Pay for payouts. BitsPath for messaging. Rating BD for the bidirectional score-and-credit loop. Kuhok focuses on what only it can do.
- 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, and a credit only earns its highest verification level when a real payment clears through LoneSock Pay.
- 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 LoneSock Pay payout to that person on that project clears. Webhook signatures are verified with HMAC-SHA256 and a five-minute clock-skew window. The credit on your profile reflects the highest level you have actually reached.
- 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 across harassment, fraud, safety violation, and discrimination, with severity, evidence URLs, and an open / in_review / closed / escalated workflow.
- 05Where is Kuhok in production today?
- Live at kuhok.net. The platform runs 14 .NET microservices behind a YARP gateway with Darwan RBAC at the route level, a Next.js 16 frontend, PostgreSQL with pgvector, Redis 8, RabbitMQ 4.1, MinIO for assets, and Groq Llama 3.3 70B for completions with Ollama for embeddings. The deployment lives on deploy.kuhok.net under Ubuntu 24.04 and is pushed by an SSH-triggered build, with no inbound deploy webhook per KaritKarma policy.
- 06How does Kuhok connect to Rating BD?
- Kuhok and Rating BD share the same ecosystem (Wenme for auth, Darwan for permissions, LoneSock Pay for payouts, BitsPath for messaging, MinIO for storage). 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. 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.
Your name belongs in the
opening titles, not the end of a WhatsApp thread.
Kuhok is invite-only and live. If you are on a production right now, ask the producer for the join code, or write in. The team adds new units one shoot at a time.