Dapr · FinOps Profile

Dapr Finops

FOCUS-aligned FinOps for Dapr: there is no vendor invoice for upstream Dapr itself. Cost emerges from the underlying compute (sidecar CPU/memory), state store, message broker, and any commercial managed Dapr distribution the operator chooses (Diagrid Catalyst, Azure Container Apps Dapr extension, etc.). FinOps reporting for Dapr workloads should attach to the cloud provider that hosts the sidecars rather than to Dapr itself.

Dapr Finops is the FinOps profile for Dapr on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a per-invoice cycle, and pricing category open source / self-hosted.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Distributed Systems, Microservices, Open Source, FinOps, and FOCUS.

Category: Developer Tools Pricing: Open Source / Self-Hosted Billing: Per-Invoice FOCUS v1.3
Distributed SystemsMicroservicesOpen SourceFinOpsFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

Usage

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
PricingCategory
Open Source
ProviderName
Dapr (CNCF)
PublisherName
Cloud Native Computing Foundation
ServiceCategory
Developer Tools
ServiceName
Dapr
ServiceSubcategory
Distributed Application Runtime

Meters

sidecar_compute_hours
Unit: instance-hour
CPU/memory hours consumed by Dapr sidecars (daprd) running alongside application workloads. Charged by the underlying compute provider, not by Dapr.
state_store_operations
Unit: request
Reads/writes to the configured state store backend (Redis, Cosmos DB, DynamoDB, etc.). Billed by the state-store provider.
pubsub_messages
Unit: message
Messages published or delivered through the configured pub/sub broker (Kafka, RabbitMQ, Service Bus, etc.). Billed by the broker provider.
data_egress
Unit: GB
Network egress between Dapr sidecars and external state/broker/binding endpoints.

Sources