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: Red Hat 3scale
providerId: red-hat-3scale
publisherName: Red Hat, Inc.
serviceCategory: API Management
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:
  - API Management
  - Gateway
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps shape for Red Hat 3scale. Pricing is contact-sales, so the
  meter list reflects subscription/term structure rather than usage-based billing.
sources:
  - https://www.redhat.com/en/technologies/jboss-middleware/3scale
notes: No public price list or usage-billing API; FOCUS columns reflect the assumed annual-subscription
  shape, not a fetched billing surface.
billingModel:
  pricingCategory: Subscription
  billingFrequency: Annual
  billingCurrency: USD
  chargeCategories:
    - Purchase
focusColumns:
  ServiceName: Red Hat 3scale API Management
  ServiceCategory: API Management
  ProviderName: Red Hat
  PublisherName: Red Hat, Inc.
  InvoiceIssuerName: Red Hat, Inc.
  BillingCurrency: USD
meters:
  - name: subscription_term
    description: Annual 3scale subscription (sized by deployment scope and call volume)
    unit: contract
    aggregation: sum
    dimensions:
      - deployment_model
      - support_level
      - term_length
principles:
  - name: Visibility
    description: 3scale's own analytics service exposes per-application and per-method call
      counts that customers can use for internal showback against the Red Hat subscription cost.
  - name: Allocation
    description: Allocate the 3scale subscription to the platform team that operates the gateway;
      use 3scale account/application metadata to attribute downstream API spend to consumers.
  - name: Optimization
    description: Right-size deployment topology (single vs multi-tenant, OpenShift-native vs
      hosted), consolidate API portfolios behind a shared 3scale instance, and renegotiate term
      length at renewal.
  - name: Accountability
    description: Platform engineering owns the 3scale subscription; product API teams own their
      consumer plan design.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com