No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

There are a number of ways to structure this. Stacks and projects are purposely flexible in this way. Based on the way you’re talking about it, if the idea is that each customer is using the same template, you could have a stack per customer. Then, as you update your Pulumi program (on a per-stage basis), you could update each customer’s stack based on that template.

In the `&lt;org&gt;/&lt;project&gt;/&lt;stack&gt;`  naming scheme, the `org` refers to the Pulumi organization that owns that stack. So your company for example or yourself as an individual.

Thanks. So to understand it better how do you suggest naming my stack so it reflects provided directory structure?

If you haven’t already, I’d suggest reading <https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/> which gives some ideas