Temporal Technologies

09/01/2026

Agent Workflow histories can get noisy fast.

Learn how to label Activities, Workflows, and Timers in Temporal so agent steps are easier to scan and debug in the Temporal UI: https://temporal.io/blog/label-your-agent-steps

08/31/2026

In December 2024, Temporal Cloud landed on Google Cloud Marketplace. Since then, we've deepened our partnership with Google Cloud across Google ADK, the Google Gen AI SDK, and Serverless Workers for Cloud Run.

Today we're sharing two updates:

1. Our Google Gen AI SDK integration is now in Public Preview. Developers building with Gemini can now get Temporal's durability built in automatically.
2. Temporal Cloud is now available on Google Cloud Marketplace with pay-as-you-go pricing, allowing developers to start building in minutes, with consolidated billing and the ability to offset existing spend commitments.

To celebrate, we're offering $1,000 in credits for new sign-ups. Read more: https://temporal.io/blog/temporal-expands-google-cloud-partnership-with-pay-as-you-go-pricing

08/30/2026

Daily AI agent use is up 70.8%. Stress levels are down 44.6%. Do we sense a connection?

Our latest survey of 554 engineering teams is a lot to unpack but here’s the brief: We expected to find at least some panic, but instead we found calm. A majority of respondents are more optimistic about their job prospects than a year ago (77.5%), and only about a quarter of their companies (27%) are pausing or stopping hiring.

In the write-in responses, a significant number of engineers rejected the idea that AI agents even factor into their stress levels. There are plenty of other things to stress about.

We asked them to complete this sentence: “From what I’m seeing, everyone just needs to __.”

Top answer: “Chill.”

Read the report:

We surveyed 550 engineers about how often they use AI agents, what they use them for, where deployments break down, and how the shift affects their work.

08/27/2026

We asked 554 engineers and engineering leaders 45 questions about their AI agent use:

91.1% say AI agents “improved” or “revolutionized” their work
85.5% trust the outputs at least somewhat
41.1% encounter agent issues at least daily

Plus, 44.6% are less stressed than 1 year ago.

Read the report → https://temporal.io/reports/state-of-development-2026

08/26/2026

Temporal Cloud’s billing store had roughly a year of headroom left.

The team moved to ClickHouse, validated it with shadow traffic, and gained 3–5 years of projected runway while cutting steady-state cost by about 70%. Read more: https://temporal.io/blog/migrating-temporal-clouds-billing-store-to-clickhouse

08/25/2026

Who’s on your team?

Our new report, The State of Development 2026, is out today. Read what 554 engineers had to say: https://temporal.io/reports/state-of-development-2026

08/24/2026

Temporal made the Lenny 100!

That puts us among the 100 companies Lenny Rachitsky would most want to join today, based on talent density, the ambition of the problems we're solving, and the potential upside.

See the list:

A list of the top 100 companies Lenny would most want to join (if he was looking for a job today)—companies with the highest talent density, tackling the most ambitious problems, and with the biggest upside.

08/21/2026

Stephen Montague spent two months screen-sharing to ship one cloud-to-edge integration. A year later, he rebuilt the pattern with Temporal using an egress-only proxy that can receive configuration changes without inbound ports or redeploys.

Read the story:
https://temporal.io/blog/i-spent-two-months-screen-sharing-to-ship-one-integration-so-i-rebuilt-it-on-temporal

08/20/2026

👋 San Francisco! This month’s Durable AI meetup is all about agent context. We'll dive into all the tools and infrastructure that give AI agents the right information, at the right time, reliably.

Say you'll be there: https://luma.com/durable-ai-august

08/19/2026

Data passed between Activities is recorded in Event History and visible in the Temporal UI, so for a bank handling customer PII, a clean multi-Activity design would expose it.

Guest author Houman Kargaran keeps the PII scan, classification, and storage inside one Activity instead. Raw text never crosses a boundary; only a file ID does. The Workflow's structure becomes the security guarantee.

Read the full blog: https://temporal.io/blog/using-activity-isolation-as-a-security-boundary