See your users' tomorrow, today. Four products, one API, three SDKs. Transaction history and app events in — forward-looking scores and life-event predictions out. Every score signed by the Courtroom. Every audit replayable. Sub-200ms verdicts.
Three industries live today — each with its own integration path, model set, and compliance posture. More land as partners onboard.
Each product runs as a hosted endpoint with an OpenAPI 3.1 spec, three SDKs, and a documented model card. Costs are metered per call; budgets are enforced at the partner level.
See your users' tomorrow, today.
Cohort trajectories, churn prediction, life-event detection — marriage, childbirth, job change, relocation. Months ahead. Signal-graded by domain (financial / behavioural / professional / family).
The category map your dashboard hides.
Category-level monthly forecasts. Discretionary-vs-essential split. Seasonality-adjusted baselines. Inflation-adjusted comparisons across geographies.
Headroom, sensitivity, propensity — by category.
Per-user discretionary headroom. Price sensitivity by basket. Propensity-to-purchase scores by category and price tier. Forward-looking, not lookback.
Explainable verdicts. Feature weights attached.
Explainable credit risk analysis with counterfactuals. Lending scores backed by 8 alternative-data sources. Card / UPI fraud verdicts targeting sub-200ms — each one signed by the Courtroom (Proposer, Defender, Judge).
Mukodi is built RBI-first, SEBI-aware, IRDAI-friendly, DPDP-strict. Every API call signs a Courtroom verdict, hash-chains the audit row, and respects the §13 self-serve erasure cascade. You don't bolt on compliance after integration; we ship it.
A typical partner integration runs on these four checkpoints. Each ships with a public runbook, a dedicated regulatory operator, and a 24h-ack SLA on every escalation.
Sandbox keys provisioned. Postman collection ready. First call against the categorizer in 5 minutes.
Production credentials issued after compliance review. Webhook signing keys exchanged. First model promoted off shadow.
Two products in production. Cost-budget enforced. Audit-chain replay validated by your security team.
Quarterly review with our regulatory operator. Model promotion process documented for your DPIA.
A lender could cut its underwriting decision cycle from days to minutes, with feature-weight-explained scores designed to stand up to an RBI question list. Illustrative scenario, not a customer quote.
Every partner has a cost-budget set at the portal. Soft-warn at 80%, clean pause at 100%. No surprise bills. Volume tiers are public; enterprise contracts are custom.
If your question isn't here, email [email protected] — we'll add it to the public list.
Mukodi is a hosted, fully-managed inference plane — a proprietary Nilfee asset, like any frontier model. Your traffic is served from our own vLLM cluster on Apache 2.0 / MIT foundation weights; no Llama, GPT, or Claude in the path, and no partner data leaves our VPC. You do not run or maintain weights. Instead you get a replayable HMAC-signed audit chain (exportable on regulator request), a per-tenant cost meter with WARN/STOP, and a contractual latency + DPDP-cascade SLA. The lock-in answer isn't 'take the weights' — it's 'every decision is verifiable and portable as evidence.'
Tabular models — sub-200ms target. Courtroom-signed decisions — sub-300ms target. Document VLM — under-4s target (Tier-3 ingest, document-grade). Voice STT/TTS — under-800ms first-token target. These are design targets, not benchmarked p99 figures.
Every signed verdict has its top feature-weight attribution stored alongside the decision in the audit chain. Counterfactuals are computed on-demand and cached for 24 hours.
Yes — per-tenant cost meter set at the partner-portal level. Monthly cap, soft-warn at 80%, clean pause at 100%. No surprise bills.
No. Audit chain stores feature hashes + signed verdicts only. PII never crosses the inference boundary — request-side and response-side both. UIDAI Aadhaar redaction gates everything ingressing.
Built-in. The DPDP §12 erasure cascade reaches 30+ internal tables plus your partner-side webhook within the DPDP-prescribed window.
Request API access and we'll provision sandbox keys within one business day. Compliance review is parallel; production keys land on day seven.