Datacenter operations · service catalogue

Turn infrastructure into products customers can buy.

Define the services, locations, shapes, commitments and prices that turn physical capacity into a consistent operator-owned cloud catalogue.

Discuss your requirementsDatacenter operations overview
Hall AHall BEdge sitesites · clusters · nodes · accelerators · storage · networkOperator console · control planeINVENTORYCATALOGUETENANTSMETERINGBILLINGCatalogueGPU · H-class · per hourVM · m.large · per monthManaged KubernetesTenantsOrg · Nordlicht Labsquota 40%Org · Meridian AGquota 25%Org · Public sectorquota 10%
Input
Approved capacity
Eligible pools and locations
Product
Operator-defined
Shapes, terms and policy
Channel
Portal & API
One catalogue everywhere
Commercial
Plan-linked
Metering and price attached
Scope

A catalogue that connects product promises to real capacity.

Every offer carries the technical constraints and commercial rules needed to fulfil it consistently.

Service definitions

Describe VMs, GPU capacity, Kubernetes, storage and network as orderable products.

Location availability

Choose which sites and pools can fulfil each catalogue offer.

Audience and quota

Control which tenants can see an offer and how much they can consume.

Plans and pricing

Attach commitments, units and commercial plans to the service definition.

Operating workflow

Publish once. Fulfil consistently.

The same definition drives the portal, API, placement and commercial record.

  1. 01

    Select capacity

    Choose eligible resource pools and service locations.

  2. 02

    Define the offer

    Set shapes, options, limits and lifecycle behavior.

  3. 03

    Attach the plan

    Connect the product to pricing and metering units.

  4. 04

    Publish

    Expose the offer to approved tenants through portal and API.

Two connected responsibilities

Operator control and customer action stay explicit.

Operator responsibility

What product teams define

  • Service names and configurations
  • Eligible locations and pools
  • Tenant visibility and quotas
  • Plans, units and commitments
Service consumer

What customers receive

  • A clear service selection
  • Known location and configuration
  • Immediate eligibility feedback
  • Consistent portal and API behavior
Operational outcome

What this changes in the working model.

Outcome 01

Product consistency

Sales, portal and fulfilment work from one service definition.

Outcome 02

Faster catalogue change

Update offers without rebuilding the customer experience.

Outcome 03

Commercial traceability

Every provisioned resource retains its product and plan context.

Return to datacenter operations overview →
Continue in this section
Partner with us

Design the cloud catalogue around your estate.

Bring the services and commitments you want to sell. We will map them to capacity, policy and metering.

Book a briefingDatacenter operations overview