specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
provider: CloudEvents
providerId: cloudevents
publisherName: Cloud Native Computing Foundation
serviceCategory: Open Source Specification
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - FinOps
  - FOCUS
  - Cloud Native
  - Open Source
  - CNCF
notes: CloudEvents is a free CNCF Graduated specification. There is no invoice, no usage meter, no commercial
  surface to allocate. The shape below preserves the FinOps Framework structure but flags the artifact
  as informational only — the meaningful FinOps surface is on the platforms that implement CloudEvents
  (EventBridge, Event Grid, Eventarc, etc.).
description: CloudEvents itself is a free, open-source CNCF specification with no commercial cost surface.
  FinOps observation should focus on the platforms that emit or receive CloudEvents.
sources:
  - https://cloudevents.io/
  - https://github.com/cloudevents/spec
billingModel:
  pricingCategory: Free / Open Source
  billingFrequency: not applicable
  billingCurrency: USD
  chargeCategories: []
focusColumns:
  ServiceName: CloudEvents
  ServiceCategory: Open Source Specification
  ProviderName: CloudEvents
  PublisherName: Cloud Native Computing Foundation
  PricingCategory: Free
  BillingCurrency: USD
meters:
  - name: not_applicable
    description: CloudEvents has no billable meters. Track consumption on the implementing platform (EventBridge,
      Event Grid, Eventarc, NATS, Kafka, etc.).
    unit: varies
    aggregation: sum
principles:
  - name: Visibility
    description: Observe CloudEvents traffic on the implementing platform's billing and metering surface;
      CloudEvents itself produces no spend.
  - name: Allocation
    description: Tag the implementing platform's resources (event buses, subscriptions, brokers) to teams
      consuming or producing CloudEvents.
  - name: Optimization
    description: Right-size payload sizes and event fan-out on the implementing platform; CloudEvents structure
      itself is overhead-light by design.
  - name: Accountability
    description: Ownership flows to the team operating the implementing event platform, not CloudEvents
      itself.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com