hi
@few-postman-20852
Can definitely appreciate the question. We definitely hear this feedback.
The foundational logic here is that Pulumi does not differentiate the purpose of a resource when it’s counted as a billable item. There is overhead to us to track and manage every item, whether it’s a stack/stack reference/provider which to customers may seem “free” or even an autoscaling group with 100 huge instances in it (which obviously would have a huge cost) - to pulumi they all look the same, it’s an object inside the resource graph that needs to be tracked and managed.
While you’re right that this will grow linearly, our thought process has always been that it’s also predictable. However, we do recognise that some orgs and workloads might have more of these resources than others.
One thing that we do also recognise is that this may drive your usage of Pulumi into a way that doesn’t follow best practices. We are consistently having conversations internally about how to effectively manage this, and I’ll feed that information back to the team.
In addition to this, we’d be happy to have a conversation with you about your individual usage to see if we can help here. Please feel free to reach out to me personally lbriggs<at>
pulumi.com and I will facilitate a conversation with someone from the account team