Multi-Tenancy
Isolated environments with resource quotas and cost allocation
One platform, hundreds of tenants, zero crosstalk
Hard isolation at the network, identity, and resource layers. Per-tenant quotas, policy enforcement, and cost allocation. Built for internal platform teams, agencies, and holding companies.
Overview
VxCloud multi-tenancy provides hard isolation between tenants at the network, compute, identity, and data layers — not just logical separation in a shared schema. Each tenant gets its own network namespace, compute quotas, storage namespace, identity realm, and audit stream. Cross-tenant access requires explicit policy grants; default is no visibility.
Platform teams use multi-tenancy to give internal business units self-service cloud capabilities without cross-contamination. Agencies and system integrators use it to isolate client environments. Holding companies use it for per-subsidiary governance. Per-tenant quotas cap compute, storage, and network spend; budget alerts notify stakeholders before limits are reached; chargeback and showback reports allocate costs precisely.
What's included
Production-grade capabilities, ready to enable in your workspace.
Hard network isolation
Dedicated network namespace per tenant. No implicit east-west connectivity unless explicitly policy-granted.
Per-tenant quotas
Compute, storage, network, API rate — caps enforceable per tenant to prevent noisy-neighbor and runaway spend.
Cost allocation
Per-tenant cost tracking with configurable chargeback or showback. Exports to your FinOps platform or invoicing system.
Tenant-scoped policies
Global platform policies with tenant-level overrides. Strict tenants can enforce stricter baselines.
Isolated audit streams
Each tenant has a dedicated audit stream. Tenant admins see their tenant's events without seeing others.
Bulk tenant operations
Provisioning, policy rollout, and archival across tenants via API. Manage 500 tenants like one.
Business outcomes
Measurable impact teams see when they adopt multi-tenancy.
Network isolation by default
Cross-tenant connectivity requires explicit policy grants. Accidental data leakage between tenants is architecturally prevented.
Cost allocation granularity
Costs are tagged to the tenant, project, environment, and resource. Chargeback reports are line-item accurate.
Tenants per platform instance
Reference customers run 500+ tenants on a single VxCloud platform without management overhead scaling linearly.
Bulk tenant management
Provision, policy-push, and audit across tenants via API. Automate what would be hundreds of manual workspace changes.
How customers use it
Real scenarios from VxCloud customers across regulated industries and fast-moving teams.
Enterprise platform team serving 80 internal business units
Each business unit gets an isolated tenant with quotas. Platform team administers all 80 via API; no manual per-tenant work.
Agency managing cloud infrastructure for 40 clients
Per-client tenants with hard isolation. Client access is scoped to their tenant; agency admins retain cross-tenant visibility for support.
Holding company with 12 portfolio subsidiaries
Per-subsidiary tenants with consolidated billing at the holdco level but isolated operations. Subsidiaries run independently.
University providing cloud access to 200 research labs
Per-lab tenants with grant-specific quotas and budget alerts. Labs self-serve; central IT maintains governance through policy.
Frequently asked questions
Still have questions? Our enterprise team answers within one business day.
Default is hard-isolated namespaces on shared compute (secure, cost-efficient). Enterprise customers can opt for dedicated compute nodes per tenant for additional isolation — useful for regulated workloads or strict noisy-neighbor concerns.
Related enterprise capabilities
Ready to move forward with Multi-Tenancy?
Talk to our enterprise team — we'll scope your requirements, map the right capabilities, and build a rollout plan tailored to your organization.