Isolated Cloud Environments for Every Team
Give each customer or team their own secure namespace — with compute, networking, storage, and billing.
Lightweight Multi-Tenancy
Namespace as a Service is a lighter alternative to full KaaS. Each tenant gets an isolated Project (Kubernetes namespace) within a shared cluster, but with complete isolation of networking, resources, and access. Hierarchy: Organization → Project. Each Project = a separate Kubernetes namespace with the format {organization}-{project} (e.g., acme-prod). Own network CIDR block. NetworkPolicies — zero cross-project traffic. Keycloak RBAC — each user sees only their own namespace.
What's in Each Namespace
VMs & Containers
Run KubeVirt VMs and containers side by side in the same namespace.
VPC Networking
Own subnet per project via Kube-OVN with floating IPs and load balancers.
Resource Quotas
CPU, memory, storage, and EIP count limits enforced per namespace.
Per-Project Billing
Built-in billing system tracks usage and charges per project.
Role-Based Access
Admin, Resource Manager, and Viewer roles per project via Keycloak RBAC.
Network Isolation
NetworkPolicies guarantee zero cross-project traffic at the network level.
Ideal For
Managed Service Providers
Separate namespaces for each client on shared infrastructure — cost-effective multi-tenancy.
Enterprise Teams
Separate namespaces for Dev, Staging, and Production environments with resource isolation.
Universities & Research
Namespace per research team or project with quota-controlled resources.
SaaS Providers
Namespace per customer tier — isolate workloads while sharing infrastructure.