Skip to content
WECORE Cloud logo
Plan a deployment

WECORE Cloud deploys Cloud Server as a governed virtual-server service on OpenStack infrastructure your organization or service provider controls. The commissioning organization defines who the service is for. After deployment, authorized users can create and administer an individual server from the images, sizes, networks, and access options approved for that environment.

What is a Cloud Server?

A Cloud Server is one virtual server on OpenStack infrastructure your organization owns, leases, or operates. An authorized user selects from the catalog defined for the deployment, then manages that server and its software. Available images, sizes, storage, networks, address policy, and access methods depend on the approved catalog and infrastructure configuration.

A deployment may organize its approved sizes into familiar families. The exact vCPU, memory, storage, and network values remain deployment-defined:

  • General purpose, balanced configurations for web services, APIs, development environments, and ordinary internal applications.
  • CPU-focused: configurations intended for sustained processor-heavy work such as CI runners, transcoding, and batch processing.
  • Memory-focused: configurations with a larger memory allocation for databases, caches, and analytical workloads.

Browser access without an inbound session port

When browser access is included in the deployment and supported by the selected image, a terminal or graphical desktop opens in a browser tab. The server connects outward to the configured edge, so the session does not require an inbound port on the server. Each request is authenticated at the service gateway and authorized against the owner of that specific server.

  • Terminal and desktop are independent. The infrastructure team can make either mode available for supported images, and readiness is reported separately.
  • Addressing follows deployment policy. The service supports automatic, required, disabled, or infrastructure-team-managed addressing; a public address is not implied for every server.
  • Access fails closed until configured. Browser sessions depend on the approved image, edge, proxy, and security policy. SSH can remain available according to the deployment's access rules.

What your infrastructure team governs

  • Catalog and access. The team approves images, sizes, networks, key pairs, security groups, quotas, and which users or customer groups may use the service.
  • Network and address policy. Address assignment and cleanup follow the policy chosen for the deployment, with retries and lifecycle reconciliation.
  • Readiness and diagnostics. Durable status markers distinguish terminal and desktop readiness, while fixed diagnostic categories identify the blocker and the responsible team.
  • Storage and lifecycle. The service manages server records and approved volume workflows (with snapshots viewed and deleted under project policy) through the same governed environment.

What authorized users can do after deployment

Authorized users create a server from the approved catalog, administer its operating system and software, attach permitted storage, and follow its status from one project record. Where browser access is configured, they can open the terminal or desktop from a browser. They can delete the server through the governed lifecycle when it is no longer needed.

Who operates the service

WECORE designs, deploys, and operates Cloud Server on the OpenStack environment agreed for the engagement. Your infrastructure team owns catalog, network, access, quota, and lifecycle policy. Users receive the server workflow only after the service and their access have been approved.

Cloud Server gives each authorized user one server to administer while the organization keeps the surrounding infrastructure policy governed.

To plan Cloud Server for your organization or customer offering, Request a briefing or Talk to our team. We will review the intended users, OpenStack environment, catalog, browser-access scope, network policy, and operating responsibilities.