Company Portfolio
For institutions and partners
This page covers strategy, the product, day-to-day workflows, governance, and how a pilot is set up. It is a trust platform. It is not a credit bureau.
Executive summary
TumiTrust is portable trust infrastructure for emerging markets.
People build a record once and can use it in more than one place.
| Question | Answer |
|---|---|
| What is it? | A trust platform. Community validation and verified activity become a lookup you can explain at decision time. |
| Who is it for? | Individuals (Trust CV), partners who send activity, and institutions such as insurers, employers, and programmes. |
| What you get | A report you can read: structured JSON, a PDF, the main drivers, where the evidence came from, and screening if you need it. |
| What it is not | A credit bureau, a loan system, or a score with no explanation. |
| How you start | A sandbox API and the institution workspace. A pilot usually runs 14 to 30 days, with the measures agreed up front. |
Partners send verified events into the network. Your team runs a lookup for a specific context when you need to decide. The workflow is the same network, and you can audit it.
The problem
The same friction shows up when a decision is due:
- Evidence is split up. Repayment history, rental records, employment, and community trade sit in different systems.
- Thin files get a default no. People with little formal paperwork are turned down instead of assessed.
- Verification is manual. Teams chase documents, and decisions wait.
- One score does not fit every decision. Lending, hiring, insurance, and rental are not the same question.
- The audit trail is thin. "We checked" is not the same as a record of what was used and why.
That shows up as lost customers, fraud, missed business, and people who are economically active but hard to document.
Our approach
Portable trust
A record built in one place can be used later by another institution. It is not stuck with a single employer, landlord, or programme.
Ubuntu
Ubuntu means "I am because we are." Trust here is something people confirm about each other. Communities record what they know. Institutions use that record only with consent, and they can see where it came from. This is not a social feed.
Portable Trust Infrastructure (PTI)
PTI is one network with two jobs:
- Partners send events. Verified activity goes into the network.
- Institutions look it up. They run a lookup for the context that matches the decision.
Deep dive: Why PTI · PTI whitepaper
Three doors, one network
| Door | Who | Primary job | Console |
|---|---|---|---|
| Member | Individuals | Build Trust CV, earn badges, share portable proof | Mobile & web |
| Trust producer | Partners, platforms, co-ops | Ingest verified activity; enable trust contexts | Partner hub & connectors |
| Institution | Lenders, insurers, employers, programs | Run trust lookups; issue badges; audit decisions | Institution hub |
Same PTI network. Different entry points. One brand.
Three trust pillars
Credibility compounds from three signal classes, all consented and context-scoped:
| Pillar | What it is | Example |
|---|---|---|
| Institutional badges | Verified claims issued by entitled institutions | Employment badge, tenancy badge, program completion |
| Community endorsements | Attestations from people who know the subject | Trade partner, group leader, professional reference |
| Consented evidence | User-shared documents and summaries | ID verification, income summary, training certificate |
Together they produce a portable, multi-context trust profile, not a single opaque number.
20+ trust contexts
TumiTrust documents 20+ trust contexts: 10 primary life areas plus 10 lens cross-cutting views on one portable map.
| Layer | Count | Examples |
|---|---|---|
| Primary | 10 | lending, rental, employment, insurance, merchant, agricultural, … |
| Lens | 10 | risk_compliance, education, civic, digital_platform, utilities, … |
Why contexts matter: the same person can be reliable in one life area and early-stage in another. Decisions should use the context that matches the decision: lending lookup for credit, employment lookup for hiring, risk_compliance lens when screening is in scope.
Enable only the contexts your contract covers. Same APIs throughout.
Full catalogue: Trust context catalogue
Product surfaces
Individuals, build & share
- Trust CV: portable profile across contexts
- Endorsements & circles: community validation with purpose-built governance
- Verification: document and identity workflows where entitled
- Shareable proof: trust reports and Verify QR for third-party confirmation
Trust producers, generate signals
- Partner hub: context enablement, connector configuration, Pulse monitoring
- Ingest channels: webhook, API, and CSV per enabled context
- Event catalogue: structured
TrustEventtypes mapped to contexts - TCU metering: transparent compute units for ingest and processing
Guide: For partners · Partner integration
Institutions, verify & decide
| Studio | Purpose |
|---|---|
| Lookup Studio | Directory search → context-scoped trust lookup → structured output |
| Insights Studio | Trends, cohort views, operational intelligence |
| Compliance Center | Screening workflows, audit trails, policy alignment |
Plus Trust platform API for embedded decision flows: search → generate → poll → webhook.
Guide: For institutions · Trust platform API
Workflow 1. Trust lookup
Goal: verify before you decide, with explainability and audit.
| Step | What happens |
|---|---|
| 1 | Search directory, native member, PTI-ID, or subject not yet on TumiTrust |
| 2 | Generate context-aware trust lookup (contexts[]) |
| 3 | Receive structured JSON + PDF, confidence band, ranked drivers, coverage gaps |
| 4 | Explain: provenance on every driver; never an opaque automated verdict alone |
| 5 | Verify: optional Verify QR for tamper-evident public confirmation |
| 6 | Decide: your policy, your outcome; we supply infrastructure |
Outcome: faster verification, consistent process, defensible audit trail.
Workflow 2. Badge issuance
Institutions become verifiers: issuing structured badges that strengthen portable trust across the network:
- Employment & work verification
- Tenancy & rental reliability
- Education & training completion
- Program participation & civic eligibility
Badges become portable proof: visible in the subject's Trust CV and available in subsequent lookups by entitled institutions.
Workflow 3. Screening & risk
TumiTrust Screening is a dedicated product for list checks (sanctions, PEP, UN Security Council lists), usable for KYC and onboarding even before a full trust report. See Screening services.
When your trust workflow includes risk assessment, add the risk_compliance lens alongside primary contexts:
- Sanctions & watchlist screening
- PEP where configured
- Identity consistency checks
- Structured screening dossier attached to trust intelligence export
Screening supplements trust lookups, it does not replace your compliance program.
Guides: Screening services · Risk & compliance
Infrastructure architecture
TumiTrust is infrastructure for portable trust, modular layers, network effects between producers and consumers, and a clear path from integration to institution decisions.
Full architecture reference: Architecture guide
Platform stack
PTI layer
Producer → consumer network
Every producer makes the network more valuable for every consumer. The same institution can play both roles over time.
What happens when you integrate
When your institution connects to TumiTrust, the platform follows a structured path from integration through intelligence to your final decision.
Technical confidence
Technology and operations leaders typically evaluate platform fit against these principles:
| Principle | What it means for you |
|---|---|
| Separation of concerns | Clear product boundaries between ingest, intelligence, and institution workflows |
| Observable operations | Latency, throughput, and error rates published via status and SLAs |
| Reliable delivery | Hosted infrastructure with documented availability and recovery commitments |
| API-first | Same contract for hub UI and embedded integrations |
Architecture reference: Architecture guide · Security architecture
Governance
Enterprise buyers need controlled access and explainable outcomes:
- Consent & purpose limitation: data used for stated trust workflows
- Minimization & retention: policies aligned to contract and jurisdiction
- Portability: subjects can build and carry proof across contexts
- Provenance: drivers trace to signals, events, and verification steps
- Audit trails: lookups, report generation, and screening actions logged
We do not replace your legal compliance program, we enable auditable workflows aligned to it.
Full framework: Trust governance · Explainability guide
Security
| Area | Posture |
|---|---|
| Authentication | Organization API keys, role-based hub access, sandbox isolation |
| Encryption | TLS in transit; encrypted storage for sensitive fields |
| Tenancy | Institution-scoped data boundaries |
| Audit | Structured logs for lookups, ingest, and admin actions |
| Resilience | DR and backup posture documented for institutional review |
Full guide: Security architecture
Commercial model
Pricing varies by volume, contexts, residency, and support tier, view plans and configure billing in your institution hub.
Typical commercial levers:
| Lever | Drives |
|---|---|
| Lookup / report volume | Core consumption metering |
| Contexts enabled | Which primaries and lenses are active |
| Screening packs | Sanctions, PEP, identity modules |
| Partner TCU | Ingest and compute for producers |
| Seats & roles | Institution hub users |
| SLA & support | Response times, dedicated contact |
| Residency | Data handling and sovereign options |
Business doc: Partner integration
Pilot program
14–30 day structured pilot
A bounded pilot with clear milestones and an executive readout at the end.
| Phase | Timeline | Activities |
|---|---|---|
| Scope | Week 1 | Use case, KPIs, context selection, sandbox credentials |
| Configure | Week 1–2 | Directory test, sample lookup, workflow enablement |
| Cohort | Week 2–3 | Live lookups on defined cohort; partner or CSV ingest if needed |
| Readout | Week 3–4 | Baseline vs pilot comparison, rollout recommendation |
KPIs to pick (choose 3–5)
| Metric | What it proves |
|---|---|
| Decision speed | Verification turnaround vs manual baseline |
| Thin-file quality | Approval quality on under-documented cohort |
| Fraud / loss signals | Early warning on inconsistent identity or behavior |
| Inclusion lift | Fair access without reckless risk |
| Operational cost | Staff time saved on document chasing |
| Conversion / churn | Business outcome on onboarding funnel |
Deliverables at pilot end
- Executive summary with baseline comparison
- Integration roadmap (dashboard-first, API, or hybrid)
- Governance and compliance checklist status
- Go-live recommendation with volume assumptions
Create sandbox API keys in API & trust signals to begin the pilot.
Why institutions choose TumiTrust
| Differentiator | Benefit |
|---|---|
| Trust platform, not bureau | Explainable drivers, your policy, your decision |
| Multi-context accuracy | Right signal for lending, hiring, insurance, rental, not one generic score |
| Three-door network | Members build proof; partners feed signals; you consume at decision time |
| Ubuntu-native design | Community validation meets institutional audit requirements |
| Programmable infrastructure | Operations teams use the hub; developers integrate via API |
| Governance by default | Consent, provenance, retention, documented, not bolted on |
| Global openness | Emerging-market depth; open to partners and institutions worldwide |
What we are not
- Not a credit bureau: we do not sell opaque consumer credit products
- Not a decision engine for your desk: institutions make their own choices
- Not a loan company. We do not originate loans or hold deposits.
- Not a social network: endorsements serve decisions, not engagement metrics
- Explainable by design: structured indicators and provenance, not decorative automation
Next steps
| Audience | Start here |
|---|---|
| Executive / strategy | Why PTI → this portfolio → pilot conversation |
| Risk / compliance | Trust governance → Risk & compliance |
| Technical leads | Architecture guide → Trust platform API |
| Partnerships | Partner integration → For partners |
Ready to evaluate? Register on tumitrust.com, create sandbox API keys under API & trust signals: and run a pilot scoped to one use case, three KPIs, and a 30-day readout.