Hatchet · FinOps Profile

Hatchet Finops

FinOps framework definition for Hatchet Cloud, the managed orchestration service for background tasks, AI agents, and durable workflows. The primary billable unit is the task run; Hatchet Cloud meters task runs per month against an included allowance per plan (e.g. 100K runs free on the Developer tier, with $10 per additional million). Self-hosted Hatchet deployments have no Hatchet-side billable surface; cost lives in the underlying Postgres, compute, and (optional) RabbitMQ infrastructure.

Hatchet Finops is the FinOps profile for Hatchet 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 9 FOCUS columns for cost-allocation reporting.

Tagged areas include Task Queue, Workflow Engine, Durable Execution, Background Tasks, and FinOps.

Category: Developer Tools / Orchestration Pricing: Usage-Based Billing: Monthly FOCUS v1.3
Task QueueWorkflow EngineDurable ExecutionBackground TasksFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseTaxCreditAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Hatchet
PricingCategory
Usage-Based
PricingUnit
task-run
ProviderName
Hatchet
PublisherName
Hatchet
ServiceCategory
Developer Tools / Orchestration
ServiceName
Hatchet Cloud

Meters

task_runs
Unit: task_run
Count of executed task runs. Hatchet Cloud's primary billable unit. A task run is one invocation of a registered task, including durable workflow steps and AI agent tool calls.
workflow_runs
Unit: workflow_run
Count of top-level workflow run instances, useful for tracking orchestration density independent of fan-out.
active_workers
Unit: worker
Concurrent worker processes connected to the orchestration engine. Workers run on customer infrastructure; this meter tracks concurrency, not Hatchet-side compute.
retained_history_days
Unit: day
Number of days of task and workflow run history retained. Plans cap retention at 3 (Team) or 7 (Scale) days; Enterprise can negotiate longer windows.