Customer cloud · compute and GPU

Provision approved compute without an operator ticket.

Customers select location, image, machine or accelerator shape, project and network from the catalogue you publish. LayerOne enforces availability, quota and placement policy before creation.

Discuss your requirementsCustomer cloud overview
Scheduler · placementVM · m.large × 4→ Hall AKubernetes · 6 nodes→ Hall AGPU job · 4× accelerator→ Hall BHall A · CPU + GPUHall B · acceleratorsgpugpugpugpugpugpugpu18 nodes · 7 accelerators · placement follows quota and residencyVMS · CONTAINERS · KUBERNETES · GPU · STORAGE · NETWORK — ONE CATALOGUE
Services
VM & GPU
One provisioning model
Choice
Catalogue-led
Approved shapes and locations
Boundary
Quota-enforced
Checked before creation
Lifecycle
Self-service
Create, resize and retire
Scope

A complete provisioning path from catalogue to running service.

The customer makes clear choices while the operator retains control of capacity and placement.

Machine shapes

Choose approved CPU, memory and storage configurations.

Accelerator capacity

Select available GPU services, reservations and locations.

Network placement

Attach the service to approved project networks and access rules.

Lifecycle actions

Start, stop, resize, snapshot and retire within policy.

Operating workflow

From service choice to governed placement.

Each customer selection resolves against real capacity and operator policy.

  1. 01

    Select the offer

    Choose VM or GPU service, shape and commitment.

  2. 02

    Set context

    Assign project, location, image, storage and network.

  3. 03

    Validate

    Check quota, availability and placement policy.

  4. 04

    Provision

    Create the resource and begin lifecycle and metering records.

Two connected responsibilities

Operator control and customer action stay explicit.

Operator responsibility

What stays controlled

  • Available shapes and images
  • Locations and eligible pools
  • Quota and reservation limits
  • Placement and lifecycle policy
Service consumer

What becomes self-service

  • Service and shape selection
  • Project and network choice
  • Approved lifecycle actions
  • Status, credentials and usage
Operational outcome

What this changes in the working model.

Outcome 01

Shorter delivery path

Approved capacity can be provisioned immediately.

Outcome 02

Consistent fulfilment

Portal and API apply the same rules.

Outcome 03

Capacity-aware selling

Catalogue availability reflects the estate the operator runs.

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

Turn compute capacity into a self-service product.

We will map your machine shapes, GPU offers, locations and placement policy into the customer workflow.

Book a briefingCustomer cloud overview