Pulumi Cloud Service or Self-Managed State Backend for Concurrent Team Updates

Goal

Select a Pulumi state backend for a team that updates the same stack concurrently, prioritizing predictable locking behavior and access control. Assumes the current stable Pulumi CLI release.

Constraint

Pulumi Cloud provides server-side state locking, version history, and organization-level access control by default. Self-managed backends using cloud object storage delegate locking and IAM to the underlying provider, and Pulumi does not publish a deterministic error contract or retry backoff for stale or contested locks on those backends.

Questions

• Does Pulumi return a consistent error when a concurrent update detects a stale lock on a self-managed backend?
• Is retry or backoff behavior configurable for contested state locks outside Pulumi Cloud?
• Does the managed backend's locking guarantee outweigh self-managed storage for teams with overlapping stack updates?