Hello, we are planning to explore Pulumi as a proof of concept to see how it could work for us as platform owners supporting our customers. We have been using Crossplane successfully, especially with Compositions and XRDs, which let us expose simplified resource claims to application teams without requiring them to deal with low-level infrastructure. As we start looking at Pulumi, I am trying to understand what the equivalent patterns are, specifically how Pulumi supports: • higher-level abstractions (similar to Crossplane Compositions) • exposing simplified “platform APIs” to customers • guardrails and policy enforcement • separation between platform admin concerns and customer usage • GitOps flows with ArgoCD/Flux • multi-tenant workflows and opinionated provisioning If anyone knows of good docs, architecture guides, or examples showing how Pulumi can be used to build this kind of platform experience, please share. I would like to start experimenting soon. Thanks!

Hi Aashish. Given that it sounds like you're considering Pulumi for what sounds like a full-fledged IDP, it might be good to talk to a solutions engineer so we can learn more about your project. Is that something you'd be interested in? If so, you can DM me your email address and we can work to get something scheduled.

Hey Josh, thanks for responding! I am definitely open to chatting with a solutions engineer, but before that I was hoping to get my hands dirty and understand the concepts a bit more. Do you happen to have any diagrams, docs, or architectural guides that explain how Pulumi handles these workflows at a high level? Something I can use to play around and quickly get a feel for how Pulumi maps to the kinds of abstractions we build today with Crossplane (Compositions, XRDs, Claims, etc.). Anything that gives a good “flavor” of the Pulumi approach would be super helpful. Thanks again!

Hi @brave-painter-79367 The docs can be found here: https://www.pulumi.com/docs/ And the fundamentals of Pulumi IaC are covered here: https://www.pulumi.com/docs/iac/concepts/ But to save you some time and effort, we would be happy to hop on a call and provide guidance on the specific platform capabilities that address your larger use-case.

Just want to echo Mitch's encouragement to hop on a call. Pulumi is a product with a large surface area. You can use it a ton of different ways. The time spent on a call with a sort of "guided tour" that caters to your specific use case should save you a ton of time.

Yeah, I’m in! A guided tour of Pulumi for our use case sounds super helpful.