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

<@U02AT958V50> happy to jump on a call to discuss this, but generally orgs use pulumi's individual accounts if there's no desire to share the state.

it's free for individuals, so they can spin up workflows to their hearts content

cool. Might do that once I get the final steps running with helm.
Having a local dev workflow involved in logging into pulumi vs just running in local context might be problematic, but not sure yet. Sounds like for local test/ephemeral environments I still need to use remote state primarily to keep it simple right?