This message was deleted.

Platform first for sure. You want to add value to teams first before you have to add a portal experience on top

Mostly agreed with Jordan since the Internal Developer Platform will have more versatility and manoeuvrability for problem solving. The point of platform engineering is problem solving and the platform itself is going to provide more opportunity for that. There are some circumstances where maybe a portal is the decision but I think it would be a more niche case.

A portal may be the first interface people want to use, but a portal is a UI, and UIs really shouldn't include business logic so I think they inherently need a platform 🤔

You can have platform without portal. Portal without platform makes no sense 🙂

We built a platform and still building. We forsee lot of requirements for easy access rather than some admin tasks which eventually lead to our v1 of portal. We iterated over the time and adding lot of value

Always the correct answer - it depends. But from my point of view, if the platform is a product, I would include the portal as part of the MVP (2-3 services addressing common problems + portal + implementation layer). The portal could help with gaining "buy-in" for the platform concept within the organization by adding this DevEx (Developer Experience) aspect from the very beginning. I'm also adding my old explanatory diagram to shed some light on how I understand the portal/service/foundation layer:

Platform first, get the MVP and buy in and then use that experience to build the portal

Late to the conversation but platform if as food as infrastructure as code along with configuration management tools to automate application delivery ( ansible , helm etc) . Portal is more developer friendly version to provide everything as UI. Hopefully that what we are solving with atmosly.com . Pls check this out and let me know your thoughts. Its MVP FOR NOW.