
Multi-tenant Platform & Billing
Run multiple financial institutions from one platform.
Run a network of independent lenders on one managed platform: each institution in its own isolated tenant, with its own apps, users and plan, billed and monitored from one place.
- Kesho Bora Microfinance
- Active · Growth plan
- Tenants on the platform
- 23 · each isolated
- Modules · Kesho Bora
- 9 of 12 enabled
One control plane for the whole platform
Ustawi runs this as a managed platform — tenants are provisioned and configured with the Ustawi team. From one place the operator sees every institution on the platform: how many tenants are active, how many users, monthly recurring revenue, which provisioning is pending, and where billing needs attention — the live state of the network, not a spreadsheet.
| Institution | Plan | Users | Apps | Status | Billing |
|---|---|---|---|---|---|
| Kesho Bora Microfinance | Growth | 18 | 9 | Active | Paid |
| Kilimo Bora SACCOS | Growth | 16 | 8 | Active | Paid |
| Haraka Credit Ltd | Starter | 4 | 6 | Setup | Pending |
This is the operator's view; tenants are provisioned with the Ustawi team.
From a spreadsheet to one platform
Drag the slider: the same tenants, tracked in a spreadsheet versus run on Ustawi.
| Kesho Bora | Growth? | 450,000 | paid? |
| Kilimo Bora | Growth | INV-1043 | ask finance |
| Upendo Finance | Enterprise | #REF! | overdue? |
| Haraka Credit | — | — | apps?? |
Platform architecture
One platform, but every tenant is configured differently — its own enabled apps, its own users, its own plan. The architecture makes the per-tenant differences plain: no two institutions have to run the same set of apps.
- Loan Origination
- Collections
- General Ledger
- Compliance
- Loan Origination
- VICOBA / VSLA
- General Ledger
- Staff Admin
- Check-off Lending
- Collections
- General Ledger
- Compliance
Each tenant runs a different set of apps, with its own users and plan.
The tenant directory
Every institution on the platform in one list — type, plan, users, enabled apps, lifecycle status, billing state and last activity. This is the operator's view across the whole network; filters narrow it by status, plan, type or billing.
| Institution | Type | Plan | Users | Apps | Status | Billing | Last activity |
|---|---|---|---|---|---|---|---|
| Kesho Bora Microfinance | Microfinance | Growth | 18 | 9 | Active | Paid | 19 Sep · 09:42 |
| Kilimo Bora SACCOS | SACCO | Growth | 16 | 8 | Active | Paid | 19 Sep · 09:38 |
| Haraka Credit Ltd | Digital lender | Starter | 4 | 6 | Setup | Pending | 19 Sep · 09:20 |
| Upendo Finance Trust | Microfinance | Enterprise | 184 | 12 | Past Due | Overdue | 18 Sep · 16:10 |
| Jitegemee Cooperative SACCOS | SACCO | Growth | 12 | 9 | Trial | Trial | 17 Sep · 11:02 |
| Kanda ya Ziwa SACCOS Union | Umbrella association | Enterprise | 96 | 11 | Suspended | Suspended | 12 Sep · 08:55 |
Status chips span the full tenant lifecycle: Setup, Trial, Active, Past Due, Suspended, Cancelled.
One tenant, described in full
Open a single institution and see its whole environment on the platform — plan, status, users, branches, borrowers, enabled apps and billing. Users appear here, inside the tenant: user and role management stays within each tenant, which is part of how tenants stay isolated from one another.
There is no cross-tenant user management; each tenant's users stay within it.
Configure each institution's Ustawi environment
Every tenant runs its own set of apps. The switchboard turns each capability on or off for an institution, drawn from the same module catalogue a customer sees in the real onboarding wizard. Modules are capabilities available on every plan — they do not change the price.
- ✓Core LendingCore — always on
- ✓Group / Solidarity Lending
- ✓Salary Check-off Lending
- ✓Collateral & Guarantors
- —VICOBA / VSLA
- ✓Sales / CRM
- —Borrower Self-Service
- ✓Compliance & Client Protection
- —Insurance Intermediation
- ✓Data Import / Migration
- ✓Integrations Hub
- ✓Subscription Billing
Modules are capabilities on every plan — enabling one does not change the price.
The tenant lifecycle
Every institution moves through the same clear lifecycle on the platform, from setup to cancellation. The operator can see where each tenant sits at a glance.
Provisioning is underway — the tenant environment is being stood up with the Ustawi team.
Live on a 14-day free trial before a plan is confirmed.
On a paid plan and operating normally, invoices settled.
An invoice is overdue — the account needs attention.
Access is paused, typically after an unresolved billing issue.
The subscription has ended — followed by offboarding and data export.
All six states are real platform states.
Tenant offboarding
When an institution leaves, offboarding is a controlled sequence, not a scramble. The subscription is cancelled, access is wound down, the institution's data is exported and provided, the environment is deactivated, and the offboarding is recorded. Data handling follows the applicable agreement and Privacy Policy.
Retention and deletion follow the applicable agreement & Privacy Policy.
Billing for every tenant, in one place
The subscription & billing model
Billing is simple and the same as /pricing. There are three fixed plans, priced by seats and branches, plus SMS overage. Modules are not priced — every plan can enable any module. Every tenant starts on a 14-day free trial, and there is no per-loan charge.
Plans and prices match the Ustawi pricing page.
The billing control center
Billing across every tenant in one place — monthly recurring revenue, how many invoices went out this month, and which are paid, pending, failed or overdue. Invoice amounts follow the real plan prices, so a Growth tenant invoice is TSh 450,000.
| Tenant | Invoice | Amount | Due | Status |
|---|---|---|---|---|
| Kesho Bora Microfinance | INV-1042 | TSh 450,000 | 01 Sep 2026 | Paid |
| Kilimo Bora SACCOS | INV-1043 | TSh 450,000 | 01 Sep 2026 | Paid |
| Baraka Microcredit | INV-1044 | TSh 150,000 | 01 Sep 2026 | Pending |
| Upendo Finance Trust | INV-1045 | TSh 1,200,000 | 01 Sep 2026 | Overdue |
| Mshikamano SACCOS | INV-1046 | TSh 450,000 | 01 Sep 2026 | Failed |
Invoice amounts match the real plan prices.
Invoice & payment history, per tenant
Each institution has its own billing history — the invoices raised month by month and whether they were paid. Here is Kesho Bora Microfinance on the Growth plan, at TSh 450,000 a month.
| Period | Invoice | Amount | Status | |
|---|---|---|---|---|
| September 2026 | INV-1042 | TSh 450,000 | Paid | View invoice → |
| August 2026 | INV-1019 | TSh 450,000 | Paid | View invoice → |
| July 2026 | INV-0996 | TSh 450,000 | Paid | View invoice → |
Every tenant inside its own boundary
Tenant data isolation
Each institution's data is isolated so it operates within its own boundary — its own borrowers, loans, reports and configuration. User and role management stays within each tenant; there is no cross-tenant user management. Tenant isolation is a distinct control from ordinary access control, and it works alongside the roles and capabilities in Staff Admin & Security.
Data does not cross the boundary between tenants.
How isolation and staff access work together
Tenant isolation sets the boundary; Staff Admin & Security controls who can do what inside it. Within each tenant, a staff identity carries a role and its capabilities, signs in from a trusted device, and every action runs through those checks and into the audit trail.
Governance across the platform
Running many institutions on one platform only works if the controls are clear. These are the ones that keep a multi-tenant operation orderly and accountable.
Each institution's data sits in its own boundary, isolated from other tenants.
Tenants are provisioned and configured with the Ustawi team, capturing the basics — not created ad hoc.
Who can do what inside each tenant is governed by Staff Admin & Security — roles, capabilities and scope.
Platform and tenant events are recorded, so activity can be reviewed and followed up.
Invoices and payment status are kept per tenant, so commercials are documented, not informal.
Describes platform controls, not a universal regulatory guarantee.
Run your lending network from one platform.
Usage, activity and platform health
Usage & adoption, per tenant
For each institution the operator can see how much of the platform is actually being used — active users, loan applications, disbursements, collections and how many apps are live — with a simple month-on-month trend.
| Metric | August | September | Trend |
|---|---|---|---|
| Active users | 15 | 16 | ▲ Up |
| Loan applications | 1,102 | 1,284 | ▲ Up |
| Disbursements | 612 | 684 | ▲ Up |
| Collections | 4,410 | 4,821 | ▲ Up |
Platform activity & audit
A cross-tenant activity feed records what happens across the platform — a user added here, an app enabled there, an invoice paid, a tenant going live. Each event names the tenant, so the operator can review and follow up.
| Time | Tenant | Event | Status |
|---|---|---|---|
| 19 Sep · 09:42 | Kesho Bora Microfinance | Added user | Done |
| 19 Sep · 09:38 | Kilimo Bora SACCOS | Enabled Collections & Delinquency | Done |
| 19 Sep · 09:31 | Kesho Bora Microfinance | Invoice INV-1042 paid | Done |
| 19 Sep · 09:20 | Haraka Credit Ltd | Tenant environment created | Done |
| 19 Sep · 09:14 | Kilimo Bora SACCOS | Role updated | Info |
Platform health monitoring
The operator can see the health of the platform's core services at a glance — so an issue is visible early, before it becomes a support call from a tenant.
Connected Ustawi apps
The platform is what the individual Ustawi apps run inside. Each tenant enables the apps it needs, and each app operates within that tenant's isolated boundary.
The lending each tenant runs inside its own environment.
Explore app →Per-tenant collections, scoped to each institution.
Explore app →Each tenant keeps its own books and postings.
Explore app →User and role management, per tenant — the isolation backbone.
Explore app →Compliance controls enabled per tenant as needed.
Explore app →Payment, SMS and fiscalization connectors per tenant.
Explore app →Who this platform is for
This app is for the organization running many institutions on Ustawi — not for a single lender, who simply uses the Ustawi apps directly. If you run one institution, you do not need this control plane.
Run a whole network of independent lenders from one control plane, each in its own environment.
Offer Ustawi under your own programme to multiple institutions — each provisioned as its own tenant. (Supported.)
Bring several member institutions onto one platform while keeping their books and users apart.
Give affiliated SACCOs and MFIs a shared platform with per-institution isolation and billing.
Operate distinct lending entities as separate tenants with their own apps and commercials.
Single lender vs platform operator
Two very different roles. A single lender simply uses Ustawi. A platform operator runs a network of lenders on Ustawi. This app is the operator model — the control plane over many tenants.
| Single lender | Platform operator (this app) | |
|---|---|---|
| How they use Ustawi | Uses the Ustawi apps directly | Runs many tenants on the platform |
| Institutions | One institution | Many institutions, side by side |
| Users | Its own staff and roles | Each tenant manages its own users |
| Applications | Its own enabled apps | Apps configured per tenant |
| Data | Its own data | Isolated boundaries between tenants |
| Billing | Its own subscription | Manages each tenant's commercials |
Getting live
How a new institution is onboarded
Bringing a new institution onto the platform is a managed onboarding — done with the Ustawi team, not a self-serve wizard. It captures the basics, creates the tenant, switches on the apps, sets up the administrator, assigns a plan on a free trial, and goes live.

Tap a stage to stop on it. Hover pauses the animation.
Provisioning captures basics only — no data-region or environment selector. Setup is done with the Ustawi team.
See Multi-tenant Platform & Billing in a live demo
Request a DemoFrequently asked questions
A tenant is a single institution's own isolated Ustawi environment — its own data, users, enabled apps and billing — running alongside other tenants on one platform.