Overview
What Metro ICT sells, where KAWI fits, and who the platform serves.
Read moreDocumentation
This documentation structure gives buyers, operators, customers, partners, and diligence reviewers a clear path through the platform model.
What Metro ICT sells, where KAWI fits, and who the platform serves.
Read moreControl-plane architecture, application boundaries, provider relationships, and execution model.
Read moreAuthentication, isolation, auditability, control boundaries, and recovery discipline.
Read moreTenant provisioning, provider operations, routing, backup, restore, suspend, and resume workflows.
Read moreCustomer-facing workspace lifecycle, access model, tenant state, and support paths.
Read moreImplementation partner model for Odoo operators, MSPs, infrastructure partners, and resellers.
Read moreArchitecture, security, recovery, operating controls, and deployment evidence for enterprise review.
Read moreAuthenticated KAWI API surfaces for tenant, provider, analytics, billing, and operational workflows.
The diligence package should collect architecture diagrams, security model, isolation design, backup and recovery model, operating workflow examples, and deployment references in one place.