Skip to main content
Platform-provided resource. Datum operates this resource; you typically reference or read it rather than create it. See Platform resources.
API resource reference for Service, part of the platform service catalog. See Platform resources for the full catalog. To read or inspect, see Reading resources.
This resource is part of the v1alpha1 API and is subject to change. Fields and behavior may change in future releases.

Identity

Overview

A Service is the platform-owned identity record for a managed capability a provider offers on Datum Cloud. It holds everything consumer-facing: the canonical name, display name, description, owning producer project, and lifecycle phase. Runtime concerns such as deployments, images, endpoints, and routing stay in the provider’s own repository; this resource is identity only. The canonical identifier is spec.serviceName, a reverse-DNS name (for example, compute.miloapis.com) that appears on invoices, in the portal, and in every downstream reference. Once a service is Published, serviceName is locked: breaking changes ship as a new Service with a new serviceName and a coordinated migration rather than a silent mutation. Use a Service to register a capability so downstream governance resources (such as MeterDefinition and MonitoredResourceType) and consumers (quota, marketplace, entitlements) can reference it.

Spec fields

Status fields (read-only)

Usage

Run datumctl explain services.services.miloapis.com --recursive to see the full, live field tree for this resource.
Last modified on July 2, 2026