KAWI Control Plane

Metro ICT's control-plane technology for multi-tenant SaaS operations.

KAWI gives Metro ICT a repeatable operating platform for provisioning, governing, recovering, and auditing SaaS tenant operations across providers, servers, and customer workspaces.

What KAWI is

KAWI is the control plane behind Metro ICT delivery. It coordinates tenant lifecycle, provider registration, server operations, routing actions, backups, restore workflows, runtime controls, and audit visibility.

Tenant lifecycle

Create, suspend, resume, recover, and govern tenants through explicit operational flows.

Provider operations

Register providers, servers, execution nodes, and operating boundaries without coupling tenants to informal scripts.

Operational auditability

Expose action history, tenant state, and service events for support, governance, and technical diligence.

What it governs

KAWI governs the operational layer beneath applications. It is Odoo-first, application-agnostic, and designed for provider-grade SaaS operations.

Provisioning

Tenant creation, workspace setup, provider attachment, and lifecycle state.

Recovery

Backup readiness, restore operations, database cloning, and service restart paths.

Runtime control

Service actions, domain and routing operations, and tenant-scoped governance.

What it does not try to be

KAWI is not the company, not a generic website builder, and not a replacement for the applications customers use. It is the control layer that makes serious SaaS operations repeatable.

Not the company brand

Metro ICT remains the company. KAWI is Metro ICT's named platform technology.

Not the application

Applications connect to the control plane; they do not carry every operational responsibility themselves.

Not manual infrastructure

The operating model favors authenticated API workflows, traceability, and controlled execution.

Why control-plane discipline matters

As SaaS operations scale, teams need less improvisation and more governed execution. The control plane creates a consistent boundary between business workflows and infrastructure actions.