This message was deleted.

yes they are

Hi @bitter-island-28909! could you please point out which section on the pricing page where this isn’t clear? Thanks for sharing the feedback.

@refined-florist-92735 It says a credit represents a resource hour, then cites custom resources, component resources, and stacks, but not provider resources. Then it gives an example: “one stack containing one S3 bucket and one EC2 instance is three Pulumi Credits per hour”. But if you include the default provider, that should be 4 credits/hour. But then, default providers are kind of different (not clear to me if they’re resources or not.) But my question was actually, about explicitly created providers. So I thought I’d ask.

Seems like we should clarify this on the pricing page. I can confirm that we don’t treat “provider” resources any differently. (We don’t have any special cases currently, all resources stored in the stacks checkpoint file are considered the same.)

I understand that special-casing certain types of resources is likely to be extra work for y’all, but I would like to make two suggestions that I think would make pricing a little friendlier: 1. Don’t bill for “component” resources; there shouldn’t be a financial penalty for writing well-structured, highly-factored code. 2. Don’t bill for “provider” resources; I recently had to create just 1-2 resources in each region in each AWS account I manage, and having providers count as resources will almost double my costs for that part of the system in a way that I can’t avoid.