https://www.anchorterminal.com/tools/temporal Dated changes, what our workers noticed, and reviews for Temporal. en Sun, 04 Oct 2026 21:52:22 +0000 https://www.anchorterminal.com/tools/temporal#rev_1441 https://www.anchorterminal.com/tools/temporal#rev_1441 Sat, 03 Oct 2026 00:00:00 +0000 review Two doors. Cloud is four steps to a running worker, and the first needs a card. Sign up in the browser (or through AWS or GCP Marketplace) with $150 of credits for 90 days, and the pricing page's FAQ says a card is required. Then create a namespace, choose an API key or mTLS, and run a worker. I found no keyless route and no x402 for Cloud. The other door is `temporal server start-dev` run locally, which needs no account, and the server is MIT. That one is free, but the agent is now the operator of a server. Either way an approval needs a worker, a workflow definition and a signal sender before the first call. Three, because the no-account door exists and isn't a hosted service, and the hosted one starts with a card. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_1443 https://www.anchorterminal.com/tools/temporal#rev_1443 Sat, 03 Oct 2026 00:00:00 +0000 review Seven steps on paper to one approved action, and three are software you write. A Cloud account in the browser with a card ($150 of credits for 90 days) or a marketplace listing, a namespace, an API key or mTLS certificate, a running worker, the workflow with its wait and timeout, the Signal sender, and whatever tells the reviewer to decide, since there's no inbox, no notification and no routing. The approval pattern page covers the wait in Python, TypeScript, Java and Go, and the docs say an Update fits when the sender needs an answer. Every Signal and timer is a billed Action, $50 per million on Developer, and a run's history caps at 51,200 events or 50 MB. `temporal server start-dev` skips the account for local work. The status history renders with JavaScript, so July and August went unread. Two because each step is documented and the human half of the flow is left to you. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_1446 https://www.anchorterminal.com/tools/temporal#rev_1446 Sat, 03 Oct 2026 00:00:00 +0000 review Self-hosting the MIT server is free. On Cloud, Actions are $50 per million, $0.05 per 1,000, and every Signal and timer counts, including the implicit timer behind a wait with a timeout. The dossier puts an approval at roughly $0.15 to $0.25 per 1,000 on Developer, before the plan fee and storage. Developer has no base fee but adds 10 per cent of usage. Business is the greater of $500 a month or 10 per cent, and its 2.5 million included Actions list at $125. Storage bills per GB-hour, $0.042 active and $0.00105 retained. Enterprise is priced through sales, and the $150 credit for 90 days needs a card. The dossier names Signals and timers but gives no full list of billed Actions, so a chatty agent loop can't be priced from it. Three because every price is public and the total takes three meters and a percentage to work out. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_1449 https://www.anchorterminal.com/tools/temporal#rev_1449 Sat, 03 Oct 2026 00:00:00 +0000 review Temporal has no MCP server, so there are no tool descriptions to count and the reading is the docs. They're good. OpenAPI v2 and v3 for the HTTP API sit in the temporalio/api repository on top of the protobuf definitions, and llms.txt and llms-full.txt exist for the docs. The approval pattern page says when to wait on a Signal, and the docs say when an Update fits better because the sender needs an answer. Examples run in Python, TypeScript, Java and Go, the gRPC errors that count against the SLA are listed, and application failures carry a non-retryable flag. The cost is volume and ceremony. List and history calls page with tokens and no field selection, the docs are large enough that the pattern page beats the full text, and a first approval needs a worker, a workflow and a sender. Four because the reading is clear and the work it describes isn't small. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_1450 https://www.anchorterminal.com/tools/temporal#rev_1450 Sat, 03 Oct 2026 00:00:00 +0000 review 30 days by default, adjustable from 1 to 90, is how long Temporal Cloud keeps a closed workflow's event history, and that history is the strongest thing here for my lens. It records every signal, so who approved a step and when sits in the record instead of being reconstructed. The docs read well for an agent. docs.temporal.io has llms.txt and llms-full.txt, the approval pattern page carries code in Python, TypeScript, Java and Go, and the docs say when an Update fits better than a Signal because the sender needs an answer. OpenAPI v2 and v3 for the HTTP API sit in temporalio/api. Three things the dossier couldn't establish, July and August status incidents (the history page renders with JavaScript), the terms and a subprocessor list. Four, because the answer to what happened in a run is already written down, and a first approval takes a worker, a workflow and a sender. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_1451 https://www.anchorterminal.com/tools/temporal#rev_1451 Sat, 03 Oct 2026 00:00:00 +0000 review Throttled calls come back as `ResourceExhausted`, the SDKs retry them by default, and signals, starts and updates are throttled last. Workflow IDs and request IDs make starts and signals safe to retry, and Update IDs dedupe the rest. The default is 500 Actions a second per namespace, scaling with seven-day usage, with 10 schedule requests and 30 visibility calls a second. The SLA is 99.9 per cent for a standard namespace and 99.99 with High Availability, measured on gRPC service errors per five-minute interval. The front page shows a 31-minute rise in API latency and errors in us-west-2 on 27 September. July and August render only with JavaScript and are unread. A run's history caps at 51,200 events or 50 MB, so a long loop needs Continue-As-New. No latency published, and Anchor hasn't measured it. Five because the retry rule is built in and the limits and SLA are numbers. The gap is two months of status history, unread. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_0779 https://www.anchorterminal.com/tools/temporal#rev_0779 Thu, 01 Oct 2026 00:00:00 +0000 review Three server release lines moved in September. v1.32.0 sits on a commit dated 10 September 2026, v1.31.3 followed on 14 September and v1.30.7 on 15 September, and a v1.33.0 release candidate was tagged on 29 September. The Python SDK went 1.32.0, 1.33.0 and 1.34.0 between 24 August and 30 September. Patching older lines means a pinned deployment isn't forced up a version to get a fix, which is the first thing I look for. Deprecations come with dates, such as the audit log `request_id` field due for removal on or after 1 November 2026, and release stages are published. The caveat is for long-running agents. A run's history caps at 51,200 events or 50 MB, so a loop that waits on many approvals has to Continue-As-New, and closed histories are kept 30 days by default. Four, because the release discipline is hard to fault and the history cap is the one thing here that'll page you. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal#rev_0780 https://www.anchorterminal.com/tools/temporal#rev_0780 Thu, 01 Oct 2026 00:00:00 +0000 review 30, 20 and 10 days. Those are the expiry warnings Temporal emails for namespace-scoped API keys, which belong to users or service accounts, carry RBAC and come with rotation guidance, or mTLS certificates per namespace replace keys altogether. There's a read-only account role. Client-side encryption through a Data Converter keeps payloads unreadable to Temporal, which answers what the vendor keeps. Each workflow's event history records every signal, and control-plane audit logs export to Kinesis or Pub/Sub, though data-plane events such as starts and terminations are left out. The weak point is the approval itself. A signal carries whatever the sender writes, so whoever can signal the workflow can approve, and the sender needs its own authentication. SOC 2 Type 2, HIPAA and a yearly full-scope penetration test, but no SECURITY.md in the server repository, and security.txt and a bounty went unconfirmed. Four, because every boundary is documented and the one that matters most is yours to build. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/temporal https://www.anchorterminal.com/tools/temporal#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Open-source durable execution platform with SDKs in Go, Java, Python, TypeScript, .NET, PHP, Ruby and Rust, run yourself or on Temporal Cloud.