Temporal · FinOps Profile

Temporal Io Finops

FinOps view of Temporal spend. The core Temporal server is open source (MIT) and free to self-host - in that model the cost is your own compute, database (persistence/visibility store), and operations, with no vendor invoice. Temporal Cloud is the managed offering, billed primarily on Actions (the unit of consumption - starting a workflow, recording a heartbeat, sending a signal, timers, retries, and similar billable operations), plus active storage and retained storage, against a plan minimum. Actions are volume-tiered, starting around $50 per million and decreasing with scale. Because Actions map directly to workflow and activity behavior, cost is driven by application design (retry policies, heartbeat frequency, signal/timer volume, history size).

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

It defines 4 billable meters, billed in USD, on a monthly cycle, and pricing category usage-based.

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

Tagged areas include Durable Execution, Workflow Orchestration, Temporal Cloud, Open Source, and FinOps.

Category: Compute and Workflow Orchestration Pricing: Usage-Based Billing: Monthly FOCUS v1.3
Durable ExecutionWorkflow OrchestrationTemporal CloudOpen SourceFinOpsCost ManagementFOCUS

Framework Alignment

Framework
Data Spec

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Temporal Technologies
PricingCategory
Usage-Based
ProviderName
Temporal
PublisherName
Temporal Technologies
ServiceCategory
Compute and Workflow Orchestration
ServiceName
Temporal Cloud

Meters

actions
Unit: actions
Billable Temporal Cloud Actions - workflow starts, signals, queries, heartbeats, timers, retries, and similar operations. Volume-tiered per million.
active_storage
Unit: gigabyte-hours
Active storage of open workflow execution state, billed per GB-hour.
retained_storage
Unit: gigabyte-hours
Retained (closed workflow) storage kept per the namespace retention period, billed per GB-hour.
self_hosted_compute
Unit: hours
Infrastructure cost of running the self-hosted Temporal cluster and its datastores (no Temporal invoice).

Sources