Temporal: durable orchestration is not procurement authority

External-source research synthesis, not an OfferSignal client result. Based on the retained October 2026 research and source-specific dates.

The problem is a workflow that cannot safely stop

An industrial order can cross enterprise resource planning (ERP), product-lifecycle management (PLM), manufacturing execution (MES), customer relationship management (CRM), suppliers and human approvers. A crash, delayed response or partially completed payment can leave the team unsure what happened. Temporal addresses that execution problem: developers write workflows, activities call external services, and the Temporal Service records event history so workers can replay and resume after failure. Retries, timeouts, durable timers, messages and compensation patterns cover waiting and recovery. 1 2

That is a control layer, not an autonomous purchasing agent. Temporal does not provide product master data, computer-aided design interpretation, cost models, supplier truth, legal terms or quote authority. A human approval is an application step defined by the customer; the platform does not invent the authority behind it. 2 3

What the named evidence shows

The clearest production case is Vinted. The marketplace first rewrote a lower-risk refund and invalidation flow, ran old and new paths side by side with feature flags, and then expanded Temporal across payments. Its provider-published case reports 10–12 million Workflows and Activities per day in payments, with open-source Temporal self-hosted on premises for the core platform and Temporal Cloud used for greenfield Amazon Web Services services. Vinted reports cleaner code, built-in retries and locking, and lower infrastructure cost from self-hosting, but no controlled before-and-after return-on-investment denominator. 5

A Vinted engineering article describes a separate Vespa search-infrastructure operation that grew from roughly 100 to more than 1,000 nodes. A Go workflow drains traffic, upgrades and restarts nodes, checks health, schedules upgrades twice monthly, provisions nodes, reports to Slack and lets teams trigger restarts through a bot. Manual intervention became an outlier, the article says, but it gives no hours, cost or failure-rate baseline. 6

Other figures are reported scale, not audited customer outcomes. A FINOS article says Will Bank processes over 2 million invoices, without a stated period or before-and-after denominator. Temporal’s Series C announcement reported more than 2,500 Cloud customers, 183,000 weekly active open-source developers and 7 million unique clusters in the preceding 18 months. Its Series E announcement reported more than 4,300 paying customers, 1.9 trillion billable actions in August and 43 million open-source installs. 9 11

An illustrative RFQ-to-order use

For an illustrative custom-fabrication business, Temporal could ingest an RFQ, preserve revisions and units, call PLM and ERP checks, fan out supplier or plant capacity checks, wait for engineering and commercial review, and coordinate reservation, production, shipping, invoicing and reconciliation. This is an illustrative application, not a reported Temporal deployment.

The workflow needs canonical entities, material and tolerance requirements, released drawings, current capacity, price validity, customer terms and permitted substitutions. The engineer remains authoritative for technical fit; commercial owners approve a binding offer and purchase order; a named finance owner controls payment. Temporal can record these transitions and route exceptions, but it cannot make missing evidence authoritative.

Failure boundaries must be tested

Activities execute at least once, so external side effects need an idempotency key or deduplication. Otherwise a retry can double-charge, duplicate an order or repeat a machine action. Workflow code must remain deterministic; versioning and replay tests protect long-running executions during releases. Temporal’s documentation stresses that workflow durability does not guarantee dependency availability. 7

A first test should kill workers, interrupt network access, overload a downstream service and verify failover and backlog recovery. Add validation for stale prices, incompatible materials, missing revisions and capacity conflicts before side effects. Measure duplicate actions, exception rate, recovery latency, review time and cost per completed workflow—not merely whether a demo resumes after a crash.

Cost, evolution and decision

The core server is MIT-licensed open source; Cloud is the hosted commercial layer. The retained pricing page lists $150 in credits for 90 days, then $0.042 per gigabyte-hour of active storage and $0.00105 per gigabyte-hour of retained storage, with support at 10% of usage. Business starts at $500 per month or 10% of usage and includes 2.5 million Actions, 2.5 gigabytes of active storage and 100 gigabytes retained; Enterprise is contact-sales. Self-hosting avoids a licence fee but requires database operations, high availability, security, observability, backups, capacity and on-call ownership. 12

Temporal grew from foundations associated with AWS Simple Workflow, Microsoft Durable Task and Uber Cadence. Its founders describe earlier iterations and initially weak developer adoption before the programming model improved; Cadence had more than 100 internal Uber use cases. Current AI documentation adds stateful agents, tool calls, model pipelines, MCP and human approval patterns, but the retained evidence does not show that Temporal autonomously discovers suppliers, negotiates, approves spend or guarantees model accuracy. 3 8

Temporal is a strong candidate for an engineering-capable buyer that needs durable, auditable orchestration. It is not a ready-made industrial RFQ, CPQ, catalogue, procurement or supplier-discovery product. Start with one low-risk workflow, keep authority with named owners, and choose Cloud or self-hosting only after measuring the real integration and operating cost.

Sources and next reading

• Temporal Cloud — hosted console; an account may be required.
• Temporal open-source server — public MIT-licensed repository; self-hosting requires customer infrastructure and operations.
• Temporal AI documentation and cookbook — public documentation and runnable integration guidance.
• Temporal pricing — public pricing; Cloud purchase or account required for production use.
• Temporal e-commerce demo — public demo entry; implementation and infrastructure remain the customer’s responsibility.

Explore OfferSignal · Focused Business & AI Workshop · All research

References