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: DataHub providerId: datahub publisherName: Acryl Data, Inc. serviceCategory: Data Catalog 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: - Data Catalog - Data Governance - Open Source - FinOps - FOCUS description: 'FOCUS-aligned FinOps for DataHub: bifurcated billing model. DataHub Core is open source and produces no vendor invoice — cost is the underlying Kafka, Elasticsearch, and SQL infrastructure. DataHub Cloud is a managed subscription from Acryl Data sized by data scale and user count; per-unit prices are not public.' sources: - https://datahub.com/ - https://datahubproject.io/docs/ notes: No public per-unit pricing for DataHub Cloud; Core is OSS. Meters describe likely billable shape (assets cataloged, users, ingestion volume) but cannot be reconciled to a public price. billingModel: pricingCategory: Subscription + Open Source billingFrequency: Annual billingCurrency: USD chargeCategories: - Usage - Purchase - Adjustment focusColumns: ServiceName: DataHub ServiceCategory: Data Catalog ServiceSubcategory: Metadata Management ProviderName: DataHub (Acryl Data) PublisherName: Acryl Data, Inc. InvoiceIssuerName: Acryl Data, Inc. PricingCategory: Subscription BillingCurrency: USD ChargeCategory: Purchase meters: - name: catalog_assets description: Count of metadata entities (datasets, dashboards, ML models, etc.) cataloged in DataHub. Common scaling dimension for the Cloud SKU. unit: asset aggregation: max dimensions: - environment - tenant - asset_type - name: active_users description: Active user count consuming DataHub UI and APIs. unit: seat aggregation: max dimensions: - tenant - role - name: ingestion_events description: Metadata change events written through the emitter / CLI / Actions framework. unit: event aggregation: sum dimensions: - source - tenant - name: storage_gb description: Underlying storage for the metadata graph (Elasticsearch indices, Kafka retention, SQL primary store). Self-hosted operators see this on their cloud bill; Cloud customers see it as part of the subscription. unit: GB-month aggregation: avg dimensions: - backend - tenant principles: - name: Visibility description: For DataHub Core, join Kafka / Elasticsearch / SQL cost from the underlying cloud provider. For DataHub Cloud, use the customer admin console for asset, user, and ingestion counts and join with the Acryl invoice. - name: Allocation description: Tag deployments by team and environment; allocate DataHub Core spend through the cloud provider's tag-driven cost report. For Cloud, attribute the contract by the originating data domain or platform team. - name: Optimization description: Prune unused or stale entities to keep asset counts under contractual ceilings, tune Elasticsearch shard sizing, and reduce ingestion frequency for slow-changing sources. Use scheduled rather than streaming ingestion where freshness allows. - name: Accountability description: Platform / data-engineering teams typically own the DataHub bill; downstream consumers should be assigned ownership of their entities so unused assets can be reaped. maintainers: - FN: Kin Lane email: kin@apievangelist.com