For service providers
Offer dedicated OpenStack and Ceph clouds on infrastructure you control, with a defined service catalog and an operational model agreed with WECORE.
Commission the platform to turn your bare-metal, storage, and network capacity into dedicated cloud services for your customers.
Offer dedicated OpenStack and Ceph clouds on infrastructure you control, with a defined service catalog and an operational model agreed with WECORE.
Your customers receive an isolated cloud environment where their teams can create virtual machines, networks, volumes, images, and project access.
A documented architecture, hardware and network requirements, tenant isolation, capacity controls, monitoring, upgrades, and an escalation path.
We assess your infrastructure, design and deploy the OpenStack and Ceph stack, validate the service with your team, and provide the agreed ongoing operations.
We design and deploy the agreed compute, identity, image, storage, and networking services on infrastructure the provider controls.
Talk to our team →We integrate replicated block, image, and shared-filesystem storage where those capabilities are included in the agreed architecture.
Talk to our team →We configure the initial projects, quotas, image catalog, tenant access, native APIs, and handover documentation agreed with your team.
Talk to our team →OpenStack and Ceph provide the infrastructure layer without a proprietary per-VM licensing model.
Your infrastructure team retains the administrative access and ownership agreed for the deployment, while WECORE coordinates platform operations and upgrades.
Offer dedicated cloud environments under your service catalog, policies, and customer relationship, with tenant isolation built into the architecture.
The proposal reflects the agreed architecture, capacity, integrations, and operational scope for the deployment.
We assess, design, deploy, validate, and hand over the service with your team against the agreed architecture and acceptance criteria.
We monitor platform health, coordinate upgrades, and work incidents according to the responsibility boundary agreed with your team.
Virtual-machine capacity, server groups, quotas, and native APIs
Tenant networks, addresses, security groups, routers, and load balancing
Persistent volumes and snapshots backed by software-defined storage
A governed catalog for approved operating-system images and templates
Projects, roles, tenant isolation, and API authentication
Native APIs and a web interface for the services included in the catalog
Versioned infrastructure templates where they are included in the engagement
Replicated storage interfaces selected for the agreed architecture
| Product | Best for | Infrastructure | Storage | Billing |
|---|---|---|---|---|
| Dedicated Cloud Dedicated cloud |
For your customers: dedicated IaaS, regulated workloads, development platforms, and customer cloud services | Dedicated infrastructure for one customer | Ceph topology defined for the deployment | Tailored per deployment |
| Cloud Server | General compute, web apps, burst workloads, databases | Governed VMs on your OpenStack infrastructure | Deployment-defined block storage | Usage metering defined per deployment |
| HPC platform | Scientific compute, simulations, research, batch jobs | Managed HPC platform | Project storage defined for the deployment | Defined per deployment |
Dedicated Cloud is an engagement to design, deploy, and operate an OpenStack and Ceph cloud on infrastructure the service provider controls. The exact topology, integrations, access model, and operational scope are defined with the provider before deployment.
It is a service for datacenters and cloud providers that want to offer dedicated cloud services. Organizations may consume the resulting cloud, but the service provider commissions and operates the customer relationship.
Customers receive an isolated cloud environment with agreed controls for virtual machines, networks, volumes, images, projects, and access. The provider defines the service catalog and customer policies.
The engagement defines administrative access, architecture documentation, runbooks, monitoring, escalation, and a responsibility matrix. Your team retains infrastructure ownership and the access required for its agreed responsibilities.
Pricing is tailored to each deployment and reflects the architecture, capacity, integrations, support level, and operational responsibility agreed with the provider.
We validate the agreed identity, image, compute, networking, storage, access, and tenant-control paths with your team before handover. The acceptance criteria are defined in the engagement.
WECORE designs, deploys, validates, and operates the agreed software platform. The provider owns or leases the hardware and network, defines the service catalog, and owns the customer relationship. The exact responsibility matrix is part of the engagement.
Ceph can provide replicated software-defined storage for block volumes, images, and shared filesystems. The interfaces, topology, and replication policy are selected for the agreed architecture and validated before handover.
This engagement is being built and is not yet generally available. The page describes Dedicated Cloud as it will be delivered; talk to our team to plan a provider deployment ahead of release.