Customer cloud · storage and networking

Let customers build the complete environment.

Volumes, snapshots, images, private networks, addresses and access rules live beside compute in one project-aware workflow.

Discuss your requirementsCustomer cloud overview
cloud.your-brand.examplebrandOverviewCompute & GPUServicesProjectsUsage & billingAPI keysSupportCompute & GPUProvision approved capacity+ New instanceInstances12 runningGPU hours6 reserved · 84 hKubernetes2 clusters · healthyYour servicesgpu-train-01 · 4× accelerator · runningapi-prod · 3 instances · healthypg-main · managed database · healthyk8s-mlops · 2 clusters · healthyUsage · this month€8,420 · 62% of budget · invoice on the 1st
Storage
Volume & image
Lifecycle beside compute
Network
Private & public
Project-scoped connectivity
Policy
Operator-defined
Eligible classes and ranges
Usage
Metered
Attributed to project and plan
Scope

Infrastructure services that behave like one cloud.

Customers assemble the data and connectivity around workloads without crossing operator-defined boundaries.

Volumes and snapshots

Create, attach, resize and protect data using approved storage classes.

Images

Use operator and tenant images inside governed project access.

Private networks

Create project connectivity and attach workloads consistently.

Addresses and access

Allocate eligible addresses and apply the access model around services.

Operating workflow

Build data and connectivity into the provisioning journey.

Storage and network context stay attached throughout service lifecycle.

  1. 01

    Choose classes

    Select approved storage and network service options.

  2. 02

    Create in project

    Apply tenant, project and location boundaries.

  3. 03

    Attach to workloads

    Connect volumes and networks to eligible services.

  4. 04

    Manage lifecycle

    Resize, snapshot, detach and retire with usage retained.

Two connected responsibilities

Operator control and customer action stay explicit.

Operator responsibility

What infrastructure teams define

  • Storage classes and locations
  • Image eligibility and retention
  • Network ranges and address pools
  • Access and lifecycle policy
Service consumer

What customers manage

  • Volumes and snapshots
  • Project images and networks
  • Workload attachments
  • Usage and lifecycle actions
Operational outcome

What this changes in the working model.

Outcome 01

Complete self-service

Customers build environments without separate requests.

Outcome 02

Project consistency

Compute, data and network share the same ownership context.

Outcome 03

Measured consumption

Supporting services remain visible in usage and billing.

Return to customer cloud overview →
Continue in this section
Partner with us

Complete the cloud workflow around every workload.

We will map storage classes, network services and project policy into the customer experience.

Book a briefingCustomer cloud overview