Skip to content
WECORE Cloud logo
Plan a deployment

Some workloads should remain inside your organization, including regulated data, latency-sensitive systems, and other business-critical assets. Others need room to scale when traffic increases. A hybrid cloud lets you run one consistent platform across locations you control, such as your own data center and infrastructure you lease. WECORE Cloud's hybrid model uses an open, standards-based stack (OpenStack and Ceph) instead of proprietary virtualization, with a white-label WECORE Hub that carries your brand.

How the WECORE Cloud hybrid model works

The hybrid model runs the same cloud platform in two locations you control (for example, your premises and leased infrastructure) with each location managed through WECORE Hub. Because both locations use the same open components, workloads and data move between them without re-platforming: standard Glance images and volume snapshots replace proprietary conversions. You get the same white-label panel experience on both sides, with no compatibility layer between different cloud stacks and no license that locks you in.

WECORE Hub: a white-label control plane

At the center is WECORE Hub, the hosted white-label cloud-management panel that carries your brand, not ours. Depending on the agreed deployment, your teams (or your own customers) can receive self-service provisioning, quotas and role-based access, usage metering and billing, plus the products selected for the service catalog, such as Cloud Server, Kubernetes-as-a-Service, and object or block storage. Organizations and service providers can present the resulting cloud under their own name without building the management layer themselves.

Three ways to plug into the Hub

The delivery pattern is selected during solution design. WECORE can deploy and operate the platform on infrastructure you own or lease, integrate a suitable existing OpenStack environment, or coordinate two customer-controlled locations. The applicable Hub arrangement is defined with your team:

  • Connect your OpenStack. During solution design, we validate the existing environment and define the integration needed to present the selected services in the hosted panel. Workloads do not need to migrate merely to use the management layer.
  • Let us install the suite. WECORE deploys the OpenStack and Ceph stack on your infrastructure and operates the agreed platform responsibilities. You get a private cloud without having to assemble the software stack and operating model alone.
  • Coordinate two locations. Connect your on-premises environment to a second infrastructure location you own or lease. Data placement, isolation, and capacity boundaries are agreed for each location; sensitive workloads can remain in your data center while selected workloads run at the second site.

How the hybrid actually works

Rather than bridging two incompatible clouds, WECORE deploys the same platform in both locations. Because your data center and your second site both run OpenStack and Ceph, identity between them can be linked with Keystone-to-Keystone federation as part of the engagement's design: one set of credentials across both clouds. Each location keeps its own projects, quotas, and resources, and the operating model for coordinating the two is agreed per engagement.

Workloads move between locations using OpenStack's standard tools. Copy a Glance image or volume snapshot between the sites through image export and import, or use RBD mirroring for continuous replication, then launch it as a new instance without redesigning the workload. Keep sensitive workloads on premises, move elastic ones to the second environment, and work with the same platform and workflows on both sides.

Portable storage with Ceph

Both locations use Ceph for software-defined storage. It provides block volumes (RBD) for virtual machines, S3- and Swift-compatible object storage for applications, and a shared file system (CephFS) for workloads. Data is replicated across nodes for durability, without a proprietary storage array or license. Because both locations run Ceph, you can configure cross-site replication between the clusters with RBD mirroring for volumes or RGW multisite for object storage. This keeps your data portable between locations.

Software-based controls in a layered network design

Within the platform, traffic isolation and control are software based, with Neutron security groups providing the first layer of the design.

The upstream layer (including physical connectivity, perimeter protection, and the applicable routing boundary) is provided through your network equipment. We define the exact software functions, integrations, and operating responsibilities with your infrastructure team during solution design.

What the WECORE hybrid model gives your teams

  • Data stays where it must. Keep regulated or sensitive workloads on premises and move only what you choose to the second environment on infrastructure you lease.
  • Open, no lock-in. OpenStack and Ceph are open source, so your architecture, images, and data remain portable without a proprietary format restricting migration.
  • Your brand, your cloud. The white-label Hub lets you (or your customers) use and resell cloud services under your own name.
  • Customer-controlled locations. Each environment runs on infrastructure you own or lease, with isolation, tenancy, and capacity boundaries agreed for the deployment.
  • Managed, if you want it. Let WECORE run the platform end-to-end, or connect the OpenStack you already operate: your call.

You shouldn't have to choose between keeping data close and scaling quickly. A hybrid deployment gives you one open platform across infrastructure you own or lease, under your brand.

Whether you're a bank keeping core systems in-house, a holding company standardizing infrastructure across subsidiaries, or a service provider reselling cloud under your own brand, WECORE Cloud gives you one open platform across both environments. Connect your OpenStack, let us deploy the suite, or coordinate two locations under one engagement: the same platform and workflows on each side.

To plan a hybrid deployment for your organization or customer offering, Request a briefing or Talk to our team. We will review the locations, infrastructure, products, and operating responsibilities on each side.