Discussion scope
- Service model
- Design for your customers
- Multi-tenancy
- Isolation and governance
- Self-service
- What to automate
- Platform
- OpenShift or equivalent
- Migration
- Gradual customer transition
Platform engineers · not a sales team
VCD Alternative
Build the next generation
of cloud services.
VCD replacement is only part of the journey. The bigger opportunity is moving from infrastructure delivery to multi-tenant, self-service platforms built for modern service providers.
Multi-tenancy Self-service Service catalog Platform APIs
Red Hat
Premier Partner
100+
Enterprise customers
EU
Europe-first
2017
Founded
The shift
Why providers are rethinking VCD
For many service providers, the pressure is not just about replacing a platform. It is about what the next platform should help the business deliver.
Margins under pressure
Infrastructure-only services are becoming harder to differentiate and defend on price alone.
Customers expect self-service
Buyers increasingly expect easier access, clearer service options, and faster delivery.
Multi-tenancy needs stronger foundations
Isolation, governance, and customer boundaries need to be designed into the platform from the start.
Infrastructure alone is becoming commoditised
The opportunity is to package and deliver higher-value services on top of a managed platform.
The opportunity
Infrastructure to services
The next platform decision should not only ask what replaces VCD. It should ask how your service model evolves.
Today
Infrastructure delivery
- Virtual machines
- Hosting and colocation
- Managed infrastructure
- Manual provisioning
The opportunity
Service-based delivery
- Developer platforms
- Self-service environments
- Multi-tenant workspaces
- Managed OpenShift
- Platform APIs
The discussion
What a platform discussion
focuses on
This discussion is designed to help you step back from tool replacement and think through the right platform direction.
Current operating model
Review how you currently deliver infrastructure, hosting, managed services, or private cloud.
Service packaging
Explore how services should be defined, offered, and consumed by customers.
Multi-tenancy and isolation
Discuss how customer environments should be separated, governed, and operated.
Platform architecture
Clarify the role of OpenShift, SCO, automation, APIs, and operational support.
Clarity
Questions we help answer
01 / Question
How should services be packaged?
02 / Question
What should customers consume through self-service?
03 / Question
What should remain managed?
04 / Question
How should multi-tenancy work?
05 / Question
What platform best supports that model?
06 / Question
How can existing customers migrate gradually?
The approach
A platform approach
for what comes next
For providers looking beyond VCD, the next step usually needs more than a replacement product. It requires the right combination of platform design, supporting technology, implementation, and operational enablement.
Technology
This often includes technologies such as OpenShift and Stakater Cloud Orchestrator, depending on the provider's goals, existing environment, and service model.
Platform design
Define the service model, multi-tenancy boundaries, and the platform architecture that supports them.
Supporting technology
Select and configure the right combination of platforms — including OpenShift and Cloud Orchestrator where appropriate.
Implementation guidance
Structured migration planning that minimises disruption to existing services and customers.
Operational enablement
Day-2 runbooks, automation, and the processes your team needs to operate and evolve the new platform.
Audience
Who this discussion
is for
This discussion is designed for service providers who are thinking beyond infrastructure delivery.
Designed for
- CSPs and MSPs evaluating their next platform
- Infrastructure and cloud service providers
- Platform and infrastructure leaders
- Teams already selling infrastructure or hosting
- Providers looking to expand or modernise their service offerings
- Teams evaluating alternatives to VCD
Get started
Start Platform Discussion
If you are evaluating alternatives to VCD, this is the right time to step back and discuss what your next platform should actually support.
Tell us a little about your current platform priorities and we will arrange a discussion.
Submitted
We'll be in touch.
Your request has been submitted. One of our platform engineers will reach out within one business day to arrange a discussion.
Typical first response · within 1 business day Platform engineers · not a sales team
Questions
Common questions
Is this a VCD migration engagement?
Not in the traditional sense. The focus is on platform strategy — what comes next and how it supports your service model. VCD replacement is part of that conversation, but not the only one.
Do we need OpenShift?
Not necessarily. OpenShift is one option we work with, alongside other Kubernetes distributions. The discussion focuses on what fits your environment and service goals, not a fixed product path.
Can we keep existing VMware workloads?
Yes. A phased approach is the most practical path for most providers. Existing workloads continue running while new platform capabilities are built alongside them.
Is this suitable for MSPs?
Yes. The discussion is specifically designed for providers who deliver services to customers — MSPs, CSPs, and private cloud teams. Multi-tenancy, service packaging, and customer isolation are central topics.
Can we introduce self-service gradually?
Yes. Self-service does not need to be an all-or-nothing transition. The discussion covers how to start with the right primitives and expand as operational confidence grows.
Can existing customers migrate over time?
Yes. Customer migration is a key part of the planning discussion. The goal is to move gradually without disrupting services or forcing customers into abrupt changes.
VCD Alternative
Ready to discuss your next platform move?
Book a platform discussion to review your priorities, service model, and the right direction beyond VCD.