Deployment models

API, branch console, CSV/SFTP, or dedicated.

Same audit trail. Same governance. Same score. The integration path matches how your institution actually lends today — modern fintech, legacy branch, regulated bank.

Request demo →Pricing

Choose a path

Four ways to deploy

Console-first

For pilot lenders and branches that need review screens before any API integration.

CSV

CSV / SFTP

Batch scoring for MFIs, SACCO federations and existing legacy systems.

API

API SaaS

Real-time scoring, webhooks, policy versioning and usage monitoring.

Dedicated / sovereign

In-country or private deployment for regulated institutions and data-residency needs.

SLA

Production-grade

99.9% uptime, sub-500ms p95 scoring, HMAC-signed events.

Pilot path

6-week pilot: discovery → sandbox → backtest → shadow → decision.

A path that grows with you

1PilotStart console- or CSV-first to prove value with a cohort — no heavy integration.
2IntegrateMove to the API and webhooks as your origination workflow matures.
3ScaleGraduate to dedicated or sovereign deployment for residency and scale.

Deployment options

Match the integration to how your institution lends today.

The same audit trail, the same governance, the same score — whichever surface you adopt. Most pilots start on API SaaS or Branch console; CSV / SFTP fits MFIs running on legacy systems; dedicated deployment exists for banks with data-residency requirements.

Fintechs, digital lenders, integrators

API SaaS

Ready when: Same-day sandbox; production keys within 5 working days of pilot agreement.

SLA shape: 99.9% uptime · sub-500ms p95 scoring · webhook retries with HMAC signature.

Branches without API capability today

Branch console

Ready when: Lender staff log in to the portal; submit an applicant; get back the same decision payload.

SLA shape: No infra on your side. Same audit row as the API path.

MFIs, SACCO federations, legacy lenders

CSV / SFTP batch

Ready when: Drop a tape, get a scored tape back. Per-row reasons + validation errors.

SLA shape: Same-day for tapes under 10k rows; overnight for portfolio-wide runs.

Regulated banks needing data residency

Dedicated deployment

Ready when: Single-tenant infrastructure in-country. Same API surface; isolated database.

SLA shape: Contract-driven SLA. Quarterly compliance reviews. Full audit-log export.

Africa-scale readiness

Prepare the platform before entering a new market.

Expansion needs more than hosting. Each country needs representative data, localized user experience, regulator-aware controls, and explainable AI that remains decision support for the lender.

Representative data

Blend repayment history, cashflow, rent, bill payments, mobile-money, utilities and BNPL signals so readiness does not depend on one fragile input.

Fairness and explainability

Test for disparate impact, tune thresholds by market, and ship every readiness score with clear reason codes, confidence and model version.

Human review

Duruj recommends; the lender decides. Loan officers and risk committees can override, correct inputs and document the rationale.

Local language and currency

Prepare for Amharic, Swahili, Hausa, French and local financial terminology, with currency-aware workflows and country-specific user guidance.

Compliance controls

Run market-by-market privacy impact reviews, data-residency checks, encryption policies, access logs and revocation flows before launch.

Provider-ready APIs

Normalize bank, wallet, SACCO, insurer and utility fields into a shared schema, with sandbox data and SDK paths for partner teams.

Multi-tenant deployment

Isolate tenants, countries, scoring policy, compliance modules and data stores so each market can meet local rules without forking the platform.

Consumer coaching

Pair readiness insights with practical next steps: smooth cashflow, keep documents current, highlight on-time payments and build verified behavior.

Pilot path

A 6-week pilot, methodology disclosed.

Week 1: Discovery — portfolio shape, signal availability, success metrics.
Week 2: Sandbox + policy configuration — your weights, your thresholds, your approval routing.
Week 3–4: Backtest on your historical loans — AUC, KS, calibration table per score band.
Week 5: Shadow scoring on live applications — no decision impact, observe-only.
Week 6: Decision review with the credit committee — pilot results, deployment plan.

We do not publish a specific default-reduction percentage until at least three pilot institutions produce verified, methodology-disclosed evidence.

Start a pilot conversation →View pricing

Pick the right deployment.

Tell us your constraints — residency, scale, integration maturity — and we'll map the path.

Request demo Explore products