Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

Yes sure <@U0563CE17GS>.
In *Platform as a Service*, various engineering teams such as Cloud, DevOps, System Engineering, and Security operate autonomously. Think of it like delegating tasks – when there's a need, like deploying resources or setting up a cloud component, we engage the specialised team responsible. It's like raising a ticket; they take care of the rest. They handle the work, address any queries we might have, and eventually close the ticket.
On the other hand, in *Platform as a Product*, the focus is on empowering our end-users and developers. Instead of delivering a service, we provide them with a self-serve platform or product. Users have more control over their actions, thanks to customization by our Platform teams. We determine what should be automated and what needs manual attention. This approach benefits both our Platform Engineering team and our users. For instance, when creating resources, our platform/product prompts users for configurations adds predefined settings when necessary, and efficiently gets everything set up. This streamlined process involves just a couple of clicks, and the automation takes care of the rest – minimising friction and enhancing the experience for everyone involved.
This is my understanding of *Platform as a Product* &amp; *Platform as a Service* however I'm open to your input in case I have missed out on any aspect.

We had started operating as PaaS and are now moving to Platform as product. PaaS wasn’t sustainable 

Hi <@U03LMPR7HPV>,
That's wonderful! Could you please share the tools and factors you considered during the process? We are currently in the evaluation phase, and your insights would be incredibly valuable to us.

<@U05LQKVJAKF> - sorry just seeing this.
The first thing we did was enforce governance. Write up standards for important platform patterns (tag all resources to establish resources, standardize these tags, AMI usage, containerization, etc). This helps reduce proliferation of “bad habits”, address security gaps, contain cost across the enterprise

This first step was to clean up the existing chaos.
Next is creating the dev portal like you mention. We have evaluated Backstage and Port, but have not finalized on it yet.
For self service also, focus on what are your user’s biggest pain points? Is it onboarding new services? adding new resources? just seeing what capabilities are available (service catalog) and how to use them?
Prioritize based on what is the biggest money/time/effort suck and implement that first. Get user feedback, rinse and repeat

Hope I understood your question right and this helps