# product-launches Published articles for product-launches. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sign in to Pulumi Cloud with Passkeys DevFeed: [Sign in to Pulumi Cloud with Passkeys]() Original publisher: [Read original article]() Author: Devon Grove Published: 2026-07-13T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Passkeys](), [WebAuthn](), [Security](), [passwords]() Tags: [bitbucket](), [features](), [gitlab](), [google](), [oauth](), [passwords](), [product](), [product-launches](), [security]() ### AI overview Pulumi Cloud now supports passkeys for users who sign in with an email address and password. Passkeys use device-stored public-key credentials and WebAuthn, while identity-provider sign-in flows remain unchanged. ### Source excerpt Pulumi Cloud now supports passkeys for users who sign in with email and password. Select a button, approve with Touch ID, Face ID, Windows Hello, or your hardware key, and you're signed in. A passkey is a public-key credential stored on your device: your phone, your laptop, a hardware key (YubiKey, Google Titan, etc.), or your password manager can all function as the authenticator. When you sign in, your device authenticates you locally and signs a challenge from Pulumi Cloud with the private key. The private key stays on your device -- Pulumi Cloud never sees or stores it. Passkeys are built on the WebAuthn standard, so they're already supported on every major browser and operating system. Who this is for This release applies to users who sign in to Pulumi Cloud with an email address and password. If you sign in through an identity provider (IdP), such as GitHub OAuth, GitLab, Bitbucket, Google, or your organization's SAML SSO, your existing flow is unchanged. Why passkeys Passwords have always been the weakest link in account security. Since they are shared secrets, they are vulnerable to phishing attacks, and every place you type one is a place that can be impersonated or a data store that can be leaked. Passkeys swap that out for a per-site key pair that lives on your device: Phishing-resistant by design. A passkey is bound to the exact origin it was registered for. A look-alike domain can't trigger your authenticator. Synced across your devices. Apple iCloud Keychain, Google Password Manager, 1Password, Dashlane, Bitwarden: most credential managers now sync passkeys end-to-end-encrypted to every device you've signed in on. Discoverable. Pulumi Cloud doesn't need to know which user you are before you authenticate. Just select "Sign in with a passkey" and your device offers the right credential. Nothing to remember. A passkey lives on your device. There's no string to memorize, and no sensitive credential stored by us. Setting up a passkey The next time you sign i ## Introducing pulumi do: Direct Resource Operations for Any Cloud DevFeed: [Introducing pulumi do: Direct Resource Operations for Any Cloud]() Original publisher: [Read original article]() Author: Christian Nunciato Published: 2026-05-22T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Command-line interface](), [Cloud](), [Provisioning](), [Amazon S3](), [Amazon Web Services]() Tags: [ai-agents](), [aws](), [cli](), [command-line](), [features](), [iac](), [infrastructure](), [infrastructure-as-code](), [product](), [product-launches](), [pulumi](), [pulumi-cli](), [s3]() ### AI overview Pulumi introduces pulumi do, a terminal command for direct cloud resource operations. It can create, read, update, delete, and query resources across Pulumi-supported providers without requiring a project, code, or state. The article also describes how pulumi do, Agent accounts, and Pulumi ESC can support ad-hoc infrastructure work and AI agent workflows. ### Source excerpt Infrastructure as code is the right model for production systems. State tracking, drift detection, and repeatable deployments all matter when you're managing real workloads. But sometimes, you also need a quick, one-off interaction with the cloud: create a bucket or a database, look up a VPC, delete a stray resource. Today we're introducing pulumi do, a new command for direct resource operations. With pulumi do, you can create, read, update, delete, and query any cloud resource from the terminal with a single command, across thousands of Pulumi-supported providers -- no project, code, or state required. The problem: Sometimes IaC is more than you need When you're managing production workloads, IaC is the proven solution. Code lets you declare complex systems, state tracking catches drift before it becomes a problem, dependency graphs sequence changes safely, and policy keeps everything in bounds. That full lifecycle, especially with the backing of a platform like Pulumi Cloud, is exactly what you want to build systems that scale. But when you (or your coding agent) need an ad-hoc Postgres database, the simplest path with IaC still takes several steps: make a directory, create a project, configure your credentials, write the code, preview, deploy. It works, but it's not always necessary for what should be a simple operation. pulumi do collapses all of those steps into one, using the same Pulumi providers, resource model, and ecosystem that powers the core Pulumi platform. Resource creation is also only part of the problem. As Joe laid out in The Agentic Infrastructure Era, the real challenge for AI agents isn't with code or CLI commands, it's with everything else: getting a cloud account, resolving credentials, wiring configuration across multiple services. Agent accounts, also released this week, simplify this by letting an agent provision its own ephemeral Pulumi Cloud account, and Pulumi ESC takes care of consolidating credentials across providers. Together, with p ## Durable Digest: December 2025 DevFeed: [Durable Digest: December 2025]() Original publisher: [Read original article]() Author: Temporal Technologies Published: 2025-12-19T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [reliability](), [Availability](), [Replication](), [OpenTelemetry](), [Artificial Intelligence](), [Netflix](), [Ruby](), [Monitoring]() Tags: [2025](), [ai-agents](), [announcements](), [blog-post](), [deployment](), [fraud-detection](), [high-availability](), [how-to](), [netflix](), [openai](), [opentelemetry](), [product-launches]() ### AI overview Temporal's December 2025 Durable Digest reviews major product launches and updates, including Nexus GA, High Availability and replication features, Worker Versioning, SCIM User Management, the Ruby SDK, and an OpenMetrics endpoint. It also highlights OpenAI Agents SDK integration, a Netflix builder spotlight, and resources on AI fraud detection and OpenTelemetry observability. ### Source excerpt It's been a packed year at Temporal. In this issue: major product launches, a builder spotlight from Netflix, and two fresh "How to Temporal" resources ## Replay 2023: Day one DevFeed: [Replay 2023: Day one]() Original publisher: [Read original article]() Author: Rob Holland Published: 2023-09-14T07:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Development](), [event driven](), [Code generation](), [API](), [Kafka](), [Retool](), [ordering](), [stripe]() Tags: [code](), [code-generation](), [community](), [event-driven-architecture](), [http](), [kafka](), [latency](), [launches](), [product-launches](), [retool](), [stripe](), [temporal]() ### AI overview A recap of the first day of Replay 2023 covers Temporal's Durable Execution, product announcements, and customer presentations from Yum! Brands, Twilio, Retool, HashiCorp, and Stripe. The talks describe workflow migration, compliance adoption, DAG execution performance, code generation, and Kafka cluster management. ### Source excerpt Replay 2023 Day 1 highlights: Temporal's Durable Execution, product launches, and insights from Yum! Brands, Twilio, Stripe, Datadog & more.