# internal developer portal Published articles for internal developer portal. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Developer portal security and governance best practices DevFeed: [Developer portal security and governance best practices]() Original publisher: [Read original article]() Author: Jesse Wang Published: 2026-09-17T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [internal developer portal](), [Security](), [Access Control](), [Automation](), [audit](), [Vulnerabilities](), [Terraform](), [Deployment]() Tags: [access-control](), [auditability](), [automation](), [developer](), [governance](), [hardcoded-credentials](), [internal-developer-portal](), [microservices](), [security](), [security-compliance]() ### AI overview This article presents security and governance practices for internal developer portals. It focuses on role-based access control, automated audit logging, centralized visibility, software catalog governance, and reducing risks from infrastructure drift and workflow sprawl. ### Source excerpt Enhance developer portal security, compliance, and auditability without slowing down engineering teams. See how Harness helps simplify IDP governance. | Blog ## Measuring IDP Success: Metrics Beyond Tracking DevFeed: [Measuring IDP Success: Metrics Beyond Tracking]() Original publisher: [Read original article]() Author: Rashmi Hegde Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [internal developer portal](), [Developer experience](), [code productivity](), [Platform Engineering]() Tags: [developer-experience](), [developer-productivity](), [idp](), [internal-developer-portal](), [platform](), [privacy](), [surveillance]() ### AI overview This guide explains how to measure Internal Developer Portal success with outcome-based metrics that respect developer privacy. It emphasizes ROI and system-health indicators such as deployment frequency and mean time to recovery, while warning that individual activity tracking can erode trust, distort behavior, and undermine adoption. ### Source excerpt Learn how to measure IDP success with meaningful metrics that respect developer privacy. Discover ROI indicators that matter. Explore now. | Blog ## Continuous Delivery Excellence with Harness IDP DevFeed: [Continuous Delivery Excellence with Harness IDP]() Original publisher: [Read original article]() Author: Rashmi Hegde Published: 2026-08-21T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Continuous Delivery (CD)](), [internal developer portal](), [CI/CD](), [Platform Engineering](), [Deployment](), [Automation](), [Orchestration](), [Provisioning]() Tags: [automation](), [ci-cd](), [continuous-delivery](), [deployment](), [developer-velocity](), [idp](), [internal-developer-portal](), [orchestration](), [platform-engineering](), [provisioning](), [self-service](), [tooling]() ### AI overview This article explains how Harness Internal Developer Portal can support continuous delivery through self-service workflows, standardized deployment pipelines, and unified service catalogs. It argues that delivery friction often comes from cognitive overhead, unclear prerequisites, fragmented permissions and configuration, and insufficiently discoverable workflows rather than a lack of pipeline capability. ### Source excerpt Achieve continuous delivery excellence using Harness Internal Developer Portal. Streamline deployments, boost velocity, and empower developers. Learn more. | Blog ## What is the ROI of Spotify's Backstage internal developer portal? DevFeed: [What is the ROI of Spotify's Backstage internal developer portal?]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-30T11:28:26Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [internal developer portal](), [Platform Engineering](), [Open Source](), [Back end](), [Front end]() Tags: [backend](), [backstage](), [cost](), [developer-portal](), [financial](), [frontend](), [internal-developer-portal](), [open-source](), [platform-engineering](), [plugins]() ### AI overview The article examines the return on investment of using Spotify's Backstage to build an internal developer portal. It argues that Backstage's open-source flexibility can obscure substantial development, staffing, customization, plugin, time, and financial costs, and that teams may underestimate the effort required to operate it. ### Source excerpt Implementing Backstage comes with hidden development and financial costs -- learn whether they're worth it in this post. ## Backstage Is Dead. The Platform Engineering World Moved On DevFeed: [Backstage Is Dead. The Platform Engineering World Moved On]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-30T11:26:23Z Content type: opinion Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [Platform Engineering](), [internal developer portal](), [Developer experience](), [React](), [Terraform]() Tags: [backstage](), [developer-experience](), [developer-portal](), [internal-developer-portal](), [kubernetes](), [platform-engineering](), [react](), [terraform]() ### AI overview The article argues that Backstage, while foundational to internal developer portals and platform engineering, no longer fits how many teams work. It highlights production challenges including the need for React expertise, limited data-model flexibility, and the maintenance burden of customization. ### Source excerpt Why Backstage is dead: explore limitations, challenges, and why teams are moving to modern internal developer portal alternatives. ## Using Backstage's C4 Model adaptation to visualize software DevFeed: [Using Backstage's C4 Model adaptation to visualize software]() Original publisher: [Read original article]() Author: Daniel Sinai Published: 2026-07-30T10:43:36Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [internal developer portal](), [Software](), [Architecture & Design](), [Microservices](), [API]() Tags: [api](), [architecture](), [backstage](), [internal-developer-portal](), [microservices](), [software](), [software-catalog]() ### AI overview The article explains how Backstage's adaptation of the C4 model can visualize software through a software catalog. It describes cataloging microservices, deployment resources, deployments, relationships, dependencies, ownership, and lifecycles, and presents a SaaS-based internal developer portal as an alternative implementation approach. ### Source excerpt Using Backstage's C4 Model Adaptation to Visualize Software - Creating a Software Catalog in Port. Read more here. ## Fast-tracking service deployment with Port DevFeed: [Fast-tracking service deployment with Port]() Original publisher: [Read original article]() Author: Yarden Holtzer Weiss Published: 2026-07-30T10:39:13Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Deployment](), [sdlc](), [User Stories](), [code productivity](), [DevOps]() Tags: [cognitive-load](), [deployment](), [devops](), [internal-developer-portal](), [productivity](), [reduce](), [sdlc](), [user-stories]() ### AI overview A practical guide to creating a basic internal developer portal in 4-5 hours. It focuses on streamlining the SDLC by helping developers independently manage deployments, scaffold services, view runtime data, and review deployment history. ### Source excerpt How to create an efficient internal developer portal in just 4-5 hours to streamline SDLC, boost productivity, and enhance developer autonomy. ## Internal Developer Portal: How Do I Get Started? DevFeed: [Internal Developer Portal: How Do I Get Started?]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-30T10:23:42Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Developer experience](), [Platform Engineering](), [dev-tools](), [Microservice](), [Cloud Native Ecosystem](), [.NET MAUI]() Tags: [catalog](), [cloud-native](), [dev-tools](), [developer-experience](), [developer-portal](), [internal-developer-portal](), [jobs](), [microservices](), [onboarding](), [platform](), [platform-engineering](), [user-stories]() ### AI overview This article explains how platform engineering teams can start an internal developer portal by building a focused minimum viable product. It recommends reducing developer complexity, grounding the portal in real use cases and user stories, gathering stakeholder feedback, and improving the portal iteratively. ### Source excerpt You're using more dev tools that solve different problems, and now your breaking the developer experience. Learn the first steps to get started. ## Using Pulumi With an Internal Developer Portal | Port DevFeed: [Using Pulumi With an Internal Developer Portal | Port]() Original publisher: [Read original article]() Author: Mor Paz Published: 2026-07-30T10:17:19Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Infrastructure as code](), [Provisioning](), [GitOps](), [DevOps](), [Architecture & Design]() Tags: [building](), [catalog](), [developer](), [developer-portal](), [developers](), [devops](), [how-to](), [iac](), [infrastructure](), [infrastructure-as-code](), [internal-developer-portal](), [learn](), [platform](), [provisioning](), [resources](), [software](), [software-catalog]() ### AI overview This tutorial explains how internal developer portals can make infrastructure as code easier and safer for developers. It describes using a software catalog and reusable self-service actions to abstract IaC details and provision developer environments, with Pulumi and Port as the example. ### Source excerpt Internal developer portals can close the IaC and developer loop. Let's look at a live example of how to use Pulumi and internal developer portals. ## Set Up Developer Self-service in Your Internal Developer Portal | Port DevFeed: [Set Up Developer Self-service in Your Internal Developer Portal | Port]() Original publisher: [Read original article]() Author: Yonatan Boguslavski Published: 2026-07-30T10:17:19Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Provisioning](), [Terraform](), [AWS Lambda](), [Jenkins](), [REST API](), [GitHub](), [Amazon S3](), [Microservice]() Tags: [api](), [aws](), [aws-lambda](), [catalog](), [cognitive-load](), [configuration](), [developer](), [developer-portal](), [github](), [infrastructure](), [internal-developer-portal](), [jenkins](), [platform-engineering](), [provisioning](), [rest-api](), [s3](), [terraform](), [tooling]() ### AI overview This article explains how to implement developer self-service actions in Port's internal developer portal. It covers provisioning, updating, and deleting software catalog entities and cloud resources, while describing webhook-based execution through tools such as AWS Lambda and REST APIs. ### Source excerpt Port supports many variations of implementing developer self service actions, including allowing for self-service RBAC, TTL and manual approvals. ## When is the right time to adopt an IDP? DevFeed: [When is the right time to adopt an IDP?]() Original publisher: [Read original article]() Author: Trevor Garcia Published: 2026-07-30T10:13:18Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Developer experience](), [DevOps](), [sdlc](), [Product Management](), [Tooling]() Tags: [article](), [best-practices](), [developer](), [developer-experience](), [developer-portal](), [devops](), [engineering](), [idp](), [internal-developer-portal](), [management](), [organizational](), [platform](), [platform-engineering](), [sdlc](), [software-development](), [tech-stack](), [tooling](), [tools]() ### AI overview This article explains when organizations should consider adopting an internal developer portal (IDP). It identifies scaling challenges such as operational overhead, cognitive overload, duplicated tools, unclear ownership, and inconsistent tooling. It also describes how DevOps, platform engineering, and product management practices can support an IDP that improves developer experience, standardizes tooling, and consolidates organizational knowledge. ### Source excerpt Organizations have to consider a lot of details before adopting an IDP, and it can be hard to know when is the right time. ## Why Integrations Are the Core of Platform Engineer Onboarding DevFeed: [Why Integrations Are the Core of Platform Engineer Onboarding]() Original publisher: [Read original article]() Author: Liza Sokol Published: 2026-07-30T10:13:18Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Platform Engineering](), [internal developer portal](), [Orchestration](), [Provisioning](), [GitHub](), [Kubernetes](), [Terraform](), [observability]() Tags: [engineering](), [github](), [integrations](), [internal-developer-portal](), [kubernetes](), [observability](), [onboarding](), [platform](), [platform-engineering](), [provisioning](), [terraform]() ### AI overview The article explains that integrations are the foundation of platform engineering onboarding in Port. Connecting systems such as GitHub, Jira, Kubernetes, Datadog, and Terraform supplies the data needed for software catalogs, self-service workflows, scorecards, standards, observability, and engineering insights. ### Source excerpt Learn why integrations are the foundation of platform engineering onboarding -- and how Port helps teams automate, standardize, and accelerate platform setup. ## Building an Internal Developer Portal for a Serverless Architecture DevFeed: [Building an Internal Developer Portal for a Serverless Architecture]() Original publisher: [Read original article]() Author: Mor Paz Published: 2026-07-30T10:11:28Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Serverless](), [sdlc](), [workflow automation](), [Platform Engineering](), [DevOps](), [CI/CD](), [API](), [dora metrics](), [Amazon Simple Queue Service (SQS)](), [incident](), [Security]() Tags: [api](), [automation](), [catalog](), [ci-cd](), [developer-portal](), [devops](), [dora-metrics](), [incident](), [internal-developer-portal](), [platform-engineering](), [security](), [serverless](), [serverless-architecture](), [workflow-automation]() ### AI overview This article explains how an internal developer portal can support software development in a serverless architecture. It describes software catalogs, self-service actions, workflow automation, APIs, and scorecards for improving developer independence, operational decision-making, security responses, and engineering standards. ### Source excerpt This post covers how to set up and use an internal developer portal to support the software development life cycle in a serverless architecture. ## How to Implement & Track DORA Metrics in Your Organization DevFeed: [How to Implement & Track DORA Metrics in Your Organization]() Original publisher: [Read original article]() Author: Matan Grady Published: 2026-07-30T10:11:28Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [dora metrics](), [internal developer portal](), [Deployment](), [CI/CD](), [Pull Request](), [GitHub](), [GitLab](), [Azure]() Tags: [azure](), [ci-cd](), [deployment](), [developer](), [developer-portal](), [dora-metrics](), [github](), [gitlab](), [guide](), [how-to](), [internal-developer-portal](), [metrics](), [platform](), [pull-requests](), [tools]() ### AI overview This guide explains how to implement and track DORA metrics in an internal developer portal. It covers integrating repository data, creating a deployment blueprint, modeling deployment data, and tracking deployments through pull request or merge request activity. ### Source excerpt Using this guide, you can learn how to implement and track DORA metrics in your internal developer portal. ## Why Appsec Teams Need Internal Developer Portals DevFeed: [Why Appsec Teams Need Internal Developer Portals]() Original publisher: [Read original article]() Author: Yonatan Boguslavski Published: 2026-07-30T10:09:05Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Application Security](), [Platform Engineering](), [sdlc](), [Vulnerabilities](), [Security]() Tags: [application-security](), [cognitive-load](), [dependency](), [developer-portal](), [internal-developer-portal](), [open-source-security](), [platform-engineering](), [security](), [vulnerabilities](), [vulnerability]() ### AI overview The article explains how internal developer portals can help AppSec teams support self-sufficient developers by consolidating vulnerability and misconfiguration data from multiple security tools and software development stages. By providing security information in context through catalogs, self-service remediation actions, and scorecards, portals can reduce cognitive load and dependency on AppSec teams. ### Source excerpt If you want self-sufficient developers working in a "you build it you own it" world, you need an internal developer portal. ## Celebrating Our $100M Funding Round and $800M Valuation DevFeed: [Celebrating Our $100M Funding Round and $800M Valuation]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-30T09:12:22Z Content type: news Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [sdlc](), [Artificial Intelligence](), [Vulnerabilities]() Tags: [agentic](), [agents](), [ai](), [ai-agents](), [ai-coding](), [developer-portal](), [internal-developer-portal](), [sdlc](), [series](), [software-catalog](), [valuation](), [vulnerabilities](), [workflows]() ### AI overview Port announces a $100M Series C funding round at an $800M valuation, bringing its total funding to $158M. The company describes its evolution from an Internal Developer Portal provider into an agentic SDLC platform intended to support AI-led engineering with humans in the loop. The platform is designed to extend AI assistance across software development lifecycle work, including ticket handling, incident self-healing, vulnerability fixes, and standards management. ### Source excerpt Port raises $100M Series C to move engineering from AI-assisted to AI-led, giving teams one platform to build, govern, and operate the Agentic SDLC. ## Top 4 Backstage Alternatives for 2025 DevFeed: [Top 4 Backstage Alternatives for 2025]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-27T10:37:11Z Content type: comparison Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [internal developer portal](), [Open Source](), [Platform Engineering]() Tags: [2025](), [alternatives](), [backstage](), [developer-portal](), [internal-developer-portal](), [open-source](), [platform-engineering]() ### AI overview This article examines Backstage and the challenges organizations may face when using it as an open-source internal developer portal. It presents alternatives as potential ways to address those challenges. ### Source excerpt Backstage, the open source internal developer portal framework, has many challenges. The best alternatives can overcome these problems. ## Building your golden path: Lessons from the trenches DevFeed: [Building your golden path: Lessons from the trenches]() Original publisher: [Read original article]() Author: Pablo Castelo Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [internal developer portal](), [Backstage](), [data]() Tags: [article](), [backstage](), [catalog](), [complexity](), [integrations](), [internal-developer-portal](), [use-cases]() ### AI overview This article shares practical lessons from implementing a golden path through an internal developer portal. It emphasizes that adoption depends more on user experience and accurate catalog data than on technical sophistication, recommending a minimal starting point with a service catalog and a few common-use-case templates. ### Source excerpt Lessons and a "what not to do" compilation for organizations implementing a golden path. It moves beyond the theoretical concept to cover the difficult realities of implementation ## A Quick Migration From Backstage to Port & What You Need to Know DevFeed: [A Quick Migration From Backstage to Port & What You Need to Know]() Original publisher: [Read original article]() Author: Daniel Sinai Published: 2026-07-22T12:04:29Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [migration](), [internal developer portal](), [Backstage](), [data](), [Platform Engineering](), [API](), [Kubernetes]() Tags: [api](), [backstage](), [catalog](), [data](), [developer-portal](), [internal-developer-portal](), [kubernetes](), [migration](), [platform-engineering](), [software]() ### AI overview This article explains how to migrate an internal developer portal and its data from Backstage to Port. It presents an OSS migration tool, describes importing data through the Backstage API, and introduces Port Blueprints for extending the data model and incorporating Kubernetes resources. ### Source excerpt Building an internal developer portal often begins with some experimentation. We will show a quick and handy way to import your data from Backstage to Port. ## Using an Internal Developer Portal For Superior FinOps Visibility DevFeed: [Using an Internal Developer Portal For Superior FinOps Visibility]() Original publisher: [Read original article]() Author: Aidan O'Connor Published: 2026-07-22T12:04:29Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [finops](), [internal developer portal](), [Cloud](), [Developer experience](), [Optimization](), [data]() Tags: [cloud](), [developer-experience](), [developer-portal](), [finops](), [internal-developer-portal](), [optimization](), [platform](), [resource](), [resources](), [tools]() ### AI overview The article explains how an internal developer portal can improve FinOps visibility by combining cloud cost data with development context. It describes how this helps developers, technical leaders, engineering managers, and FinOps teams understand resource ownership, service costs, budgeting, and optimization opportunities. ### Source excerpt Port transforms FinOps by integrating and contextualizing data from multiple sources to optimize cloud costs efficiently. ## Announcing the AWS Exporter | Port DevFeed: [Announcing the AWS Exporter | Port]() Original publisher: [Read original article]() Author: Tal Sabag Published: 2026-07-22T12:04:28Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Amazon Web Services](), [Amazon S3](), [Amazon Simple Queue Service (SQS)](), [AWS IAM]() Tags: [aws](), [catalog](), [cloud](), [configuration](), [developer-portal](), [encryption](), [iam](), [internal-developer-portal](), [queue](), [resource](), [s3](), [serverless](), [software-catalog]() ### AI overview Port's AWS exporter imports live AWS resource data into a software catalog and internal developer portal. It supports more than 500 resource types, maps them to blueprints and relations, and exposes metadata, tags, console links, and resource-specific details such as encryption and access configuration. ### Source excerpt The AWS exporter brings us even closer to realizing our vision of getting everything into the software catalog and the internal developer portal. ## How We Use Our Own Developer Portal DevFeed: [How We Use Our Own Developer Portal]() Original publisher: [Read original article]() Author: Mor Paz Published: 2026-07-22T11:37:29Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Developer experience](), [dogfooding](), [internal developer platform](), [Deployment](), [code productivity](), [observability](), [Microservices](), [dashboards]() Tags: [dashboards](), [deployment](), [developer-experience](), [developer-portal](), [dogfooding](), [internal-developer-platform](), [internal-developer-portal](), [microservices](), [observability](), [productivity]() ### AI overview This article explains how Port uses its own internal developer portal as a form of dogfooding to improve developer experience and productivity. It describes the portal's software catalog and several use cases, with particular focus on deployment tracking and environment locks. ### Source excerpt How we use our internal developer portal for a better developer experience and productivity - specifically for deployment tracking and environment locks ## Meet Engineering 360: Your hub for developer experience DevFeed: [Meet Engineering 360: Your hub for developer experience]() Original publisher: [Read original article]() Author: Roi Talpaz Published: 2026-07-22T11:34:04Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [devex](), [Platform Engineering](), [dora metrics](), [Automation](), [Tech Debt]() Tags: [automation](), [developer-experience](), [developer-tools](), [devex](), [dora-metrics](), [internal-developer-portal](), [platform-engineering](), [tech-debt]() ### AI overview Engineering 360 is presented as a hub for developer experience that combines engineering intelligence, surveys, quantitative metrics such as DORA, and an internal developer portal. It aims to help platform and engineering teams identify friction, prioritize improvements, automate resolutions, and measure outcomes. ### Source excerpt We launched Engineering 360 to help engineering organizations close that loop: to gather insights, prioritize efforts, and turn feedback into visible outcomes. ## Centralize User and Team Data for Automation DevFeed: [Centralize User and Team Data for Automation]() Original publisher: [Read original article]() Author: Jim Armstrong Published: 2026-07-22T11:09:16Z Content type: release Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Automation](), [data](), [migration](), [sdlc](), [Authentication](), [GitHub](), [ai-coding](), [atlassian](), [Slack]() Tags: [ai-coding](), [atlassian](), [authentication](), [automation](), [data](), [developer-portal](), [github](), [internal-developer-portal](), [migration](), [sdlc](), [slack]() ### AI overview Port announces customizable User and Team blueprints that let organizations model their structures, centralize identity and team data from multiple tools, and support automation, ownership tracking, and visibility across the software lifecycle. Existing customers may need to migrate before 1 May 2025. ### Source excerpt You can now use Port Blueprints to organize your user groups and share ownership visibility with teams. [Next page]()