Pulumi Cloud is the hosted state, secrets and automation service behind the open-source Pulumi CLI, billed in credits and per managed resource. Pages here cover running Pulumi on a self-managed backend instead.
Keeping the open-source Pulumi CLI and leaving Pulumi Cloud: choosing S3, Azure Blob, GCS, MinIO or PostgreSQL as the backend, moving stacks with pulumi stack migrate, choosing a new secrets provider, and replacing locking, history and access control the service gave you.
Cost of ownership by component: Pulumi Cloud editions, credits and hourly per-resource billing against a self-managed backend's storage, secrets provider, CI runner time and the engineering work to replace drift detection, policies and audit trails.
For teams that need Pulumi state inside their own network: self-hosted Pulumi Cloud, available only on the Enterprise edition, against a DIY backend on object storage or PostgreSQL, compared on features, recovery from partial failures, audit and who supports it.
Getting stacks, state and configuration out of Pulumi Cloud: pulumi stack migrate to another backend, stack export for a JSON copy, what happens to encrypted secrets, and what does not move, such as deployment settings, policies and team permissions.
Scheduled drift detection and remediation is a Pulumi Cloud Pro and Enterprise feature. On a DIY backend you run preview and refresh from CI instead. This page covers scheduling, alerting, handling detected drift and the limits of that approach.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.