State of KubeCon Atlanta 2025.

2024 Platform engineering predictions

Jenny Salem
Jenny Salem
June 18, 2025
Jenny Salem
Jenny Salem&
June 18, 2025
2024 Platform engineering predictions
Listen to article
00:00 00:00

2023 was all about platform engineering. This movement largely happened thanks to a growing need to make the developer experience smoother and drive more performant software. It was also the year of Internal Developer Portals, which were the most piloted tool in 2023, according to Gartner. 

In this article, we'll explore our predictions for 2024 in platform engineering. 

All Eyes Remain on Developer Experience:

Speaking from our own experience at Port, 2023 saw a lot of companies establish developer experience teams, for the first time in their history. This intense focus on optimizing the Developer Experience (DevEx) is tied to the goal of improving developer and devops productivity.

For years, there has been a lot of focus on measuring developer productivity and this has only grown with shrinking teams and increased tool complexity. However, the emphasis has always been on defining measurements and benchmarking against others. But developers distrust productivity metrics, and the complexity of using different frameworks - of which the number keeps on growing - is high. There is also uncertainty on how tangible these metrics are, and conflicting views on which metrics or frameworks are best to use. 

Our own State of Internal Developer Portals report found that in actual fact, surveys and custom reports trump developer productivity measurement frameworks such as SPACE or DORA. And this gets to the heart of the matter - developer productivity is intrinsically linked to how much an organization is communicating and enabling their developers. 

For years, what has been overlooked is how engineering leaders can help developers become more productive. This is where DevEx comes in; by putting a greater focus on streamlining developer workflow and engaging in feedback with developers on what they need to be productive, developer productivity is likely to increase. Abstracting away complexity from platforms is key to this, and engineering teams will be looking towards developer portals to help. We expect the establishment of more DevEx teams and the integration of Developer Experience as a vital performance metric, closely monitored through surveys and reports.

Developer Portals Should be Managed Using a Product-Centric lens:

One of the most interesting approaches emerging out of 2023 was ‘Platform as a Product’. This is an approach whereby platform engineers adhere to a product management methodology when implementing an internal developer platform. This puts forward the idea that a platform is a fully-fledged product that serves internal customers and requires a thoughtful and user-centric approach in its ongoing development. The trend is driven by the understanding that each organization has its own specific processes and operational nuances.

In 2024, we believe that the same principles will be applied to the implementation of internal developer portals. Platform engineers would start by identifying the real needs of developers and understanding what should be abstracted for them, taking a portal-as-product approach.  It is then recommended to adopt a 'Jobs-To-Be-Done' framework to gather user stories, to plan roadmaps and sprints, evaluate success metrics, and continuously refine the portal, just like a consumer-oriented software offering. 

Evolution of Use Cases in Internal Developer Portals:

As the adoption of Internal Developer Portals  grows in 2024, we're expecting to see an expansion in the use cases covered by the portals. Currently, portals are predominantly utilized as service catalogs, as mentioned by Viktor Farcic in his “best devops tools for 2024”. However, with increasing usage, portals will deliver on the developer self-service promise, including day-2 operations, and adding third party tool data and self-service actions. Other potential use cases include managing costs, handling feature flags, understanding internal APIs, and more. These examples illustrate just the beginning of what’s possible. As adoption widens, the scope of portals will evolve, serving a broader and more complex set of developer needs and organizational requirements.

Expanding Portal Usage Across Roles and Personas:

As the range of use cases for Internal Developer Portals grows, a more diverse set of users will emerge, going beyond developers. Technical support staff, SREs, FinOps and CISOs are all expected to become regular developer portal users. To serve them well, the portal owner, using a product-centric approach, will need to think about how it is personalized per use case. This includes creating custom dashboards and experiences for different teams, as well as paying attention to RBAC to accommodate the unique needs and access requirements of each role.

From Spreadsheets to Automated Processes

Our "State of Internal Developer Portals" survey uncovered that 35% of respondents that believe they are using a developer portal still rely on spreadsheets for managing microservices data. However, as Internal Developer Portals become more standardized in the industry, we anticipate a significant shift. Platform engineers are expected to move away from manual spreadsheet-based reporting and tracking, transitioning to fully automated software catalogs and adding developer self-service actions as the main driver of an improved developer experience. 

Innersource Will Gain Momentum in Software Development:

The shift towards innersource - a methodology that brings an open-source approach to software development- is rapidly gaining momentum. According to Gartner, it's expected that 40% of software engineering organizations will have innersource programs by 2026, but we'll already start witnessing this growth in 2024. Internal Developer Portals will become a catalyst in adopting innersource. They serve as centralized catalogs, offering visibility into developed components and encouraging developers to utilize existing code. Additionally, Internal Developer portals facilitate the initiation of new innersource projects and ensure adherence to best practices in code development. This evolution towards innersource, with the support of portals, is a significant step towards more collaborative and efficient software development.

Tags:
No items found.
{{survey-buttons}}

Get your survey template today

By clicking this button, you agree to our Terms of Use and Privacy Policy
{{survey}}

Download your survey template today

By clicking this button, you agree to our Terms of Use and Privacy Policy
{{roadmap}}

Free Roadmap planner for Platform Engineering teams

  • Set Clear Goals for Your Portal

  • Define Features and Milestones

  • Stay Aligned and Keep Moving Forward

{{rfp}}

Free RFP template for Internal Developer Portal

Creating an RFP for an internal developer portal doesn’t have to be complex. Our template gives you a streamlined path to start strong and ensure you’re covering all the key details.

{{ai_jq}}

Leverage AI to generate optimized JQ commands

test them in real-time, and refine your approach instantly. This powerful tool lets you experiment, troubleshoot, and fine-tune your queries—taking your development workflow to the next level.

{{cta_1}}

Check out Port's pre-populated demo and see what it's all about.

Check live demo

No email required

{{cta_survey}}

Check out the 2025 State of Internal Developer Portals report

See the full report

No email required

{{cta_2}}

Minimize engineering chaos. Port serves as one central platform for all your needs.

Explore Port
{{cta_3}}

Act on every part of your SDLC in Port.

{{cta_4}}

Your team needs the right info at the right time. With Port's software catalog, they'll have it.

{{cta_5}}

Learn more about Port's agentic engineering platform

Read the launch blog

Let’s start
{{cta_6}}

Contact sales for a technical walkthrough of Port

Let’s start
{{cta_7}}

Every team is different. Port lets you design a developer experience that truly fits your org.

{{cta_8}}

As your org grows, so does complexity. Port scales your catalog, orchestration, and workflows seamlessly.

{{cta-demo}}
{{reading-box-backstage-vs-port}}
{{cta-backstage-docs-button}}

Starting with Port is simple, fast, and free.