Is anyone out there fully "self hosting" pulumi on a medium/large team? It's hard for me to leave AWS CDK / CloudFormation, because for free we've gotten: 1. A UI to browse our stacks (at one point I tried making an OSS UI for Pulumi) a. With a delete button (love that button) 2. State locking 3. Rollbacks if a stack update fails 4. So much eng effort from AWS concentrated into their construct library 5. Unlimited collaborators and RBAC 6. Integration with a secrets vault (secrets manager and param store) 7. It's the "blessed" tool by AWS so a. aws support is 🔥 -- so many great tips/fixes for $100/mo b. they pour effort into AWS CDK; amazing high-level APIs 8. Stack outputs and tags are supported--storing/accessing configs on Pulumi has limitations/gotchas 9. Not having an automation api has been okay, we've had success creating CLI tools based on cdk--we just call

cdk deploy

in a subprocess I used to complain that CF was slow, but it's gotten a lot better over the years. Now the long wait times are for unavoidable things like waiting for an RDS instance to spin up. I once used Pulumi with the S3 backend for an internal use case: creating and updating ~100 GitHub repos. Would have easily cost us $20k+/yr for those repos to sit there and exist if we'd been using Pulumi cloud. (considering that branch protection rules, environments, configs, etc. all count as resources)

Hey Eric, Thanks for the feedback. We have several customers who need to self-host for different reasons. They are medium and large teams. If you have any questions regarding the consumption for your projects, I highly recommend to reach out to our sales team. They are the best to work things out with the customer and the customer success in mind. Happy to connect you, if you want. PS: Our AWS CDK support is since last year GA. Maybe it is from interest if you want to consume the construct library but with the advantages of Pulumi: https://www.pulumi.com/blog/aws-cdk-on-pulumi-1.0/