In my quick read, I didn't see a way not to use the service.

"If this is your first time running pulumi new or most other pulumi commands, you will be prompted to log in to the Pulumi service. The Pulumi CLI works in tandem with the Pulumi service in order to deliver a reliable experience."[0]

[0] https://www.pulumi.com/docs/get-started/kubernetes/create-pr...

I think Pulimi is similar to terraform in that you can use multiple backends for state management, of which their "service" is one[0]. Meaning you could use the CLI backed by an S3 bucket for free.

[0]: https://www.pulumi.com/docs/intro/concepts/state/#backends

Looks like Pulimi, unlike terraform, doesn't provide a means of locking for concurrent access if you use the self-managed state.

On its way? [0] Not sure how to tell if / when this PR makes it into 3.0

[0] https://github.com/pulumi/pulumi/pull/2697

Looks like this feature may have made it into v2.23.0, behind an env var: https://github.com/pulumi/pulumi/blob/v2.23.0/CHANGELOG.md#i...

Nice!