# internal developer portal A centralized self-service interface that gives an organization's developers resources, tools, documentation, and information to build, integrate, deploy, and manage software. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build a unified CI/CD control plane with Red Hat Developer Hub DevFeed: [Build a unified CI/CD control plane with Red Hat Developer Hub]() Original publisher: [Read original article]() Author: Rishabh Singh Published: 2026-09-17T13:16:44Z Content type: tutorial Language: en Sources: [Red Hat Developer]() Topics: [internal developer portal](), [Backstage](), [argo-cd](), [CI/CD](), [Platform Engineering]() Tags: [argo-cd](), [backstage](), [ci-cd](), [cognitive-load](), [developer-portal](), [developer-productivity](), [guide](), [how-to](), [onboarding](), [openshift](), [platform](), [platform-engineering]() ### AI overview This guide explains how platform engineers can deploy and configure Red Hat Developer Hub as a unified developer portal for Red Hat OpenShift, Argo CD, Tekton, Quay, and related deployment information. It describes aggregating pipeline runs, deployment health, and container image tags in one view, along with software templates for self-service project bootstrapping. ### Source excerpt If your engineering teams waste time context-switching between Red Hat OpenShift, Argo CD, Tekton, and Quay, your platform needs a unified developer portal. The post Build a unified CI/CD control plane with Red Hat Developer Hub appeared first on Red Hat Developer. ## 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 ## Platform Engineering in the Age of AI DevFeed: [Platform Engineering in the Age of AI]() Original publisher: [Read original article]() Author: Nicole Morgan Published: 2026-09-16T20:28:57.610955Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [Platform Engineering](), [Artificial Intelligence](), [AI Agent](), [internal developer portal](), [API](), [Deployment](), [sdlc]() Tags: [agent](), [ai](), [api](), [deployment](), [developer-experience](), [engineering](), [metrics](), [platform](), [sdlc]() ### AI overview This commentary examines how platform engineering is adapting as AI coding tools and agents become part of software delivery. It discusses the build-versus-provide decisions facing platform teams, how agents may consume internal developer platforms through APIs, the need for guardrails, and the challenge of measuring the results of AI investment. ### Source excerpt 94% of engineering leaders say their AI metrics are missing. Here's how platform engineering is changing to close that gap. | Blog ## Red Hat Developer Hub: Preventing compliance violations with AI coding agents DevFeed: [Red Hat Developer Hub: Preventing compliance violations with AI coding agents]() Original publisher: [Read original article]() Author: Evan Shortiss, Ben Wilcock Published: 2026-09-15T13:17:13Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [internal developer portal](), [AI-assisted coding](), [Backstage](), [Claude Code](), [Command-line interface](), [Model Context Protocol](), [Security]() Tags: [ai-coding-agents](), [ai-inference](), [backstage](), [catalog](), [claude-code](), [cli](), [developer](), [developer-productivity](), [developer-tools](), [mcp](), [platform-engineering](), [security]() ### AI overview This tutorial demonstrates how an AI coding agent connected to Red Hat Developer Hub can query a Backstage software catalog, TechDocs, and software templates before making architectural decisions. Using a simulated insurance-company catalog, the demo shows how this context can help avoid PCI-DSS compliance violations, resolve governance conflicts, and create a traceable decision record. ### Source excerpt AI coding agents can generate entire services, reason about architectures, and scaffold applications in minutes. But ask one to build a service for your organization and you'll quickly notice the gap: it doesn't know your rules. It doesn't know which messaging broker your compliance team mandates, which services already exist in adjacent domains, or which project template is the golden path for your team. The post Red Hat Developer Hub: Preventing compliance violations with AI coding agents appeared first on Red Hat Developer. ## Red Hat Developer Hub software template authoring with rhdh-templates DevFeed: [Red Hat Developer Hub software template authoring with rhdh-templates]() Original publisher: [Read original article]() Author: Kashish Mittal Published: 2026-09-07T07:01:32Z Content type: tutorial Language: en Sources: [Red Hat Developer]() Topics: [Backstage](), [internal developer portal](), [Nunjucks](), [AI-assisted coding](), [YAML]() Tags: [ai-coding-agents](), [artificial-intelligence](), [backstage](), [developer-portal](), [developer-productivity](), [developer-tools](), [platform-engineering](), [quick-start](), [red-hat](), [software-templates](), [terminal](), [validation]() ### AI overview This tutorial introduces the rhdh-templates skill for building Red Hat Developer Hub and Backstage software templates with an AI coding assistant. It covers Nunjucks conventions, YAML schema checking, reference templates, local offline validation, repository templatization, and optional testing against a Red Hat Developer Hub instance. ### Source excerpt If you are a platform engineer or developer building Red Hat Developer Hub software templates, you know the friction of wrestling with Nunjucks syntax, guessing location.yaml placements, and discovering errors only after rendering in your developer portal. While AI coding agents handle generic YAML, they lack Red Hat Developer Hub and Backstage-specific conventions. The post Red Hat Developer Hub software template authoring with rhdh-templates appeared first on Red Hat Developer. ## 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 Does Xirp Do? Key Features, Use Cases, and Alternatives DevFeed: [What Does Xirp Do? Key Features, Use Cases, and Alternatives]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-08-18T14:34:23Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [AI-assisted coding](), [codex](), [Claude Code](), [macOS](), [internal developer portal](), [Backstage](), [MCP](), [sdlc](), [Command-line interface](), [Code]() Tags: [agentic](), [ai-coding-agents](), [backstage](), [claude-code](), [codex](), [coding-agents](), [gemini](), [macos](), [mcp](), [sdlc](), [software-catalog]() ### AI overview Xirp is Spotify's macOS desktop app for running Claude Code, Codex, and Gemini in parallel persistent terminal sessions. It provides isolated git worktrees, preserves session context when switching agents, and can connect to Spotify Portal so agents receive software catalog context through MCP. ### Source excerpt Xirp is Spotify's app for running AI coding agents in parallel sessions. What it does, when to use it, and the main alternatives. ## Top 10 developer productivity tools DevFeed: [Top 10 developer productivity tools]() Original publisher: [Read original article]() Author: Jenna Danoy Published: 2026-07-30T11:29:15Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [developer-productivity](), [Developer experience](), [DevOps](), [internal developer portal](), [Software Engineering]() Tags: [cognitive-load](), [collaboration](), [developer-productivity](), [devops](), [efficiency]() ### AI overview This article presents a list of developer productivity tools intended to help engineering teams ship faster, reduce friction, and improve collaboration. It discusses tool sprawl, developer experience, cognitive load, software engineering intelligence, developer surveys, and governance or task management. ### Source excerpt Explore developer productivity tools that help teams ship faster, reduce friction, and improve collaboration across engineering workflows. ## 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. ## Managing standards in a developer portal - a how-to guide DevFeed: [Managing standards in a developer portal - a how-to guide]() Original publisher: [Read original article]() Author: Jenny Salem Published: 2026-07-30T10:23:42Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Automation](), [site-reliability-engineering](), [incident management](), [Microservice](), [API]() Tags: [automation](), [developer](), [developer-portal](), [engineering](), [guide](), [how-to](), [incident-management](), [production](), [software](), [sre](), [standards](), [technical]() ### AI overview This how-to guide explains how internal developer portals can manage production-readiness standards. It describes reliability criteria, definition-of-done checklists, standards compliance across deployment stages, and the use of automation and self-service to balance engineering checks with development speed. ### Source excerpt Production readiness varies across engineering teams, but generally, it's a process defining reliability criteria for software in production. ## 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. ## Port Product Updates: December 2023 DevFeed: [Port Product Updates: December 2023]() Original publisher: [Read original article]() Author: Dudi Elhadad Published: 2026-07-30T10:15:06Z Content type: release Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [dashboards](), [Kubernetes](), [Developer experience](), [configuration](), [API](), [Terraform](), [incident management]() Tags: [api](), [community](), [config](), [dashboards](), [developer-experience](), [incident-management](), [kubernetes](), [product](), [release](), [release-notes](), [terraform](), [updates]() ### AI overview Port's December 2023 product updates introduce engineering scorecard and initiative dashboards, improvements to Kubernetes integration management and visualization, an action-run history widget, new ServiceNow and Terraform Cloud integrations, and a dynamic "Me" table filter. ### Source excerpt 2023 was a breakout year for Port, and these release notes mark the end of a year that was spent making Port better, together with our community. ## 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. ## Add API visualizations in Port with Swagger UI | Port DevFeed: [Add API visualizations in Port with Swagger UI | Port]() Original publisher: [Read original article]() Author: Dudi Elhadad Published: 2026-07-30T10:09:05Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [OpenAPI Specification](), [Markdown](), [Microservice](), [dev-tools]() Tags: [api](), [developer-portal](), [documentation](), [integration](), [markdown](), [openapi-specification](), [software-catalog](), [visualization]() ### AI overview Port adds visualization features to its software catalog and developer portal, including Markdown documentation, OpenAPI specifications rendered with Swagger UI, and embedded URLs. These features centralize documentation, API discovery, monitoring dashboards, and other developer tools in context, reducing search and context switching. ### Source excerpt Here are the visualization features we just added: Markdown documentation visualization, Open API - swagger and embedded URLs. ## 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. [Next page]()