# developer portal Published articles for 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. ## 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. ## Announcing the Appwrite OAuth2 server: Turn your project into an identity provider DevFeed: [Announcing the Appwrite OAuth2 server: Turn your project into an identity provider]() Original publisher: [Read original article]() Author: Matej Bačo Published: 2026-09-04T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [OAuth 2.0](), [OpenID connect (OIDC)](), [Authorization](), [API](), [internal developer portal]() Tags: [announcements](), [api](), [authorization](), [developer-portal](), [github](), [oauth](), [oauth2](), [oidc](), [openid-connect](), [product](), [sdks]() ### AI overview Appwrite announces an OAuth2 server that lets projects act as OAuth 2.1 and OpenID Connect providers. Other applications can register as clients, obtain user-approved scoped access to APIs, and use standard authorization and token flows. ### Source excerpt Your Appwrite project can now act as an OAuth 2.1 and OpenID Connect provider, so other apps can offer Sign in with your product and request scoped access to your APIs. ## Track Cursor and Copilot Adoption with a Live Port Dashboard DevFeed: [Track Cursor and Copilot Adoption with a Live Port Dashboard]() Original publisher: [Read original article]() Author: John Crowley Published: 2026-08-10T11:31:18Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [cursor](), [GitHub Copilot](), [Pull Request](), [GitHub](), [Automation](), [Artificial Intelligence]() Tags: [ai](), [automation](), [copilot](), [cursor](), [developer-portal](), [github](), [pull-request]() ### AI overview A Port walkthrough shows how to build a live dashboard for Cursor and GitHub Copilot adoption, costs, usage, and delivery impact. ### Source excerpt See who actually uses Cursor and Copilot, what it costs, and how it changes delivery, with a live adoption dashboard in Port. ## 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. ## 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. ## 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. ## 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. ## 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. ## How to set up an Internal Developer Platform: An implementation guide DevFeed: [How to set up an Internal Developer Platform: An implementation guide]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [internal developer platform](), [internal developer portal](), [Automation](), [Back end](), [Orchestration](), [Backstage](), [Front end](), [Infrastructure as code]() Tags: [automation](), [backend](), [backstage](), [building](), [developer](), [developer-portal](), [infrastructure-as-code](), [internal-developer-platform](), [orchestration]() ### AI overview A practical eight-week guide to building an Internal Developer Platform using a four-phase, MVP-first approach. It covers choosing an initial team, implementing developer self-service, demonstrating value, and avoiding common adoption failures. ### Source excerpt A practical 8-week guide to building your Internal Developer Platform (IDP) MVP. Discover the 4-phase framework for developer self-service, how to pick your first team, and expert tips to ensure successful platform adoption. ## 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. ## Port's internal deployment pipeline DevFeed: [Port's internal deployment pipeline]() Original publisher: [Read original article]() Author: Matan Heled Published: 2026-07-22T12:04:29Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Deployment](), [GitHub](), [Kubernetes](), [Microservice](), [Amazon Web Services]() Tags: [aws](), [complexity](), [deployment](), [developer-portal](), [github](), [kubernetes](), [platform](), [reduce]() ### AI overview The article explains how Port's platform team built an internal deployment pipeline using Port's developer portal and self-service actions. The approach lets developers trigger deployments directly from the portal while reducing operational tickets and standardizing procedures. ### Source excerpt Port enhances developer operations by simplifying self-service deployment, streamlining pipeline complexity, and improving log visibility. ## 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 internal developer portals improve incident management DevFeed: [How internal developer portals improve incident management]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-22T11:46:50Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [incident management](), [Platform Engineering](), [sdlc](), [Monitoring]() Tags: [developer](), [developer-portal](), [incident-management](), [metrics](), [monitoring](), [on-call](), [platform-engineering](), [real-time](), [sdlc]() ### AI overview This article explains how internal developer portals can strengthen incident management by bringing service ownership, dependencies, monitoring information, infrastructure health metrics, and operational actions into one place. It emphasizes better context, autonomy, and efficiency for on-call engineers, including self-service playbooks for incident remediation. ### Source excerpt Boost your incident management program: Upgrade from tools to a developer portal for better context, autonomy, and effectiveness. ## 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 ## Integrate Your Catalog: Port MCP Server Launch DevFeed: [Integrate Your Catalog: Port MCP Server Launch]() Original publisher: [Read original article]() Author: Jim Armstrong Published: 2026-07-22T11:12:50Z Content type: release Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [MCP Server](), [Model Context Protocol](), [internal developer portal](), [AI Development](), [Authorization](), [cursor](), [vs-code](), [Claude]() Tags: [agents](), [ai-agents](), [claude](), [cursor](), [developer-portal](), [ide](), [mcp](), [mcp-server](), [model-context-protocol](), [model-context-protocol-server](), [security](), [software-development]() ### AI overview Port announces an MCP server that connects its software catalog and AI agents with tools such as Cursor, VS Code, and Claude. Users can query live catalog information and perform actions such as creating entities and scorecards through natural-language interactions, subject to role-based access controls. ### Source excerpt Port's MCP server enables tools that developers and other users rely on daily to communicate directly with Port using natural language. [Next page]()