Skip to content
UMVANGAZI HOLDINGS
Security Start a conversation
Discuss a demonstration

Technology demonstrations

Proof should be touchable.

A capability claim becomes stronger when a client can inspect how it behaves. This catalogue separates presentation, interactive software and restricted labs so evidence can be experienced without collapsing the security boundary around it.

10registered evidence objects D0 – D4risk based classifications 3trust zones kept distinct
  1. Investigate
  2. Experiment
  3. Demonstrate
  4. Validate
  5. Hand over

Evidence today.
Stronger decisions tomorrow.

Evidence console

Public proof catalogue

Not yet public 01 / 10
Ikusasalethu Courier Working product 01 / 10

D2 ยท Logistics Platform

Ikusasalethu Courier

A courier operations platform covering bookings, bulk uploads, pricing, SMS notifications, proof of delivery, invoicing and credit notes.

Responsibility
Build
Maturity
Working product
Execution
Dedicated demo origin

What this proves

Shows a complete delivery lifecycle, from booking to proof of delivery to PDF invoice, running as one governed application.

Responsible organisationUmvangazi Technologies Related capabilityCustom Software Development Execution boundaryA Django application with its own backend and database. It runs only as a separate deployment on the demo origin with synthetic data and reset capability.

Evidence catalogue

Every demonstration exposes an action and a relationship.

Open what is available. Inspect why controlled work is not public. Follow the responsible company or the capability behind the evidence.

View all demonstrations

Ikusasalethu CRM

A customer relationship platform with role based access, contact and company records, CSV import and export, configurable settings and a REST API.

Umvangazi Technologies
SaaS Development

Ikusasalethu Marketplace

A multi supplier marketplace with web and Flutter mobile storefronts, a supplier portal, order lifecycle, payments, XML data exchange, backup recovery and system health monitoring.

Umvangazi Technologies
Mobile Application Development

Execution classification

Risk determines where proof is allowed to live.

D0 can stay inside the corporate experience. D1 and D2 require isolated execution. D3 and D4 remain restricted. The classification changes the deployment, permissions and access model.

Inspect the trust architecture
D0 Public by designPresentation only Static or local interaction with no external execution environment. Execution boundaryCorporate application D1 Security approval requiredBrowser interactive Isolated client side demonstration with a restricted browser permission model. Execution boundaryDedicated demo origin D2 Security and data approval requiredApplication demo Backend enabled demonstration deployed behind a separate origin, policy and runtime boundary. Execution boundaryDedicated application runtime D3 No anonymous executionSecurity lab Restricted adversarial or intentionally vulnerable environment that is never treated as ordinary public code. Execution boundaryRestricted lab D4 Explicit access onlyRestricted research Non public research environment that requires explicit access and operational approval. Execution boundaryRestricted research zone

Proof principle

Show the capability. Preserve the boundary.

01 ResearchWhere the question and evidence begin.02 CapabilityWhat the group can responsibly deliver.03 BoundaryWhat protects the proof while it runs.04 ConversationMove from evidence into a real client problem.

Demonstration engagement

Do not ask us only what we can build. Ask what we can show.

Where a safe demonstration exists, use it. Where the work is restricted, we can discuss the controlled evidence path appropriate to the engagement.

Discuss a demonstration