Harness IDP vs Backstage
Comparison of Harness Internal Developer Portal and Self Managed Backstage including a migration guide
Harness Internal Developer Portal (IDP) extends the popular open source framework Backstage, a Cloud Native Computing Foundation (CNCF) project. This gives us the best of both worlds - a core powered by Backstage philosophy and supported by a rich ecosystem of plugins, with a plethora of additional capabilities that are designed to make Backstage easier to configure, adopt, maintain, and scale for enterprise customers.
This document explains the advantages that Harness IDP provides over self-managed Backstage, offers a comprehensive comparison of feature sets, and outlines a migration guide for customers that are considering a transition from managing their own Backstage instance to Harness IDP.
Harness IDP adds enterprise scale, security and governance to Backstage
Backstage is a great starting point for organizations that want to build an IDP for their teams. Organizations look at success stories, such as Spotify, and want to provide the same benefits to their teams to help them become more efficient and ship high-quality code faster.
However, Backstage lacks several capabilities that are critical for enterprise adoption, including security and governance features such as RBAC and audit trails. These gaps, along with the administrative and operational burden of managing Backstage, make it difficult for enterprises to successfully adopt it to a point where they see the advantages.
Harness IDP improves on the Backstage framework to make it enterprise-friendly and easier to administer, adopt, and scale. Some of the advantages include:
Reduced Operational Burden: Harness IDP alleviates the administrative burden by handling hosting, upgrading, and patching, while providing an intuitive administrative interface. Instead of spending time on managing Backstage infrastructure or writing code to configure the portal, your platform team can focus on delivering value to developers.
Enterprise Scale and Security: After working with platform teams at several enterprises, it is clear that while Backstage is great for teams without stringent requirements for access control or scalability beyond a few hundred developers, its architecture has limitations for enterprises that need a more structured and scalable portal with fine-grained access control. Harness IDP addresses these limitations and provides the ability to organize catalog entities and workflows into a hierarchical structure representing real world organizations, entity-level granular RBAC, and a scalable Git experience that supports tens of thousands of entities.
Enterprise Governance Out-of-the-Box: Harness IDP supports Open Policy Agent (OPA) based policies, audit trails, and integrates with popular secret managers.
Advanced Workflows: Harness IDP workflows are powered by Harness pipelines, which offer sophisticated capabilities such as parallel execution, approval gates, and extensive customization options. The workflows frontend is also advanced and offers a host of customizations including dynamic pickers, conditional inputs and ability to specify dependencies between fields.
Analytics and Insights: Harness IDP includes custom dashboards for key adoption insights, scheduled executive reports, and alerting based on metrics trends, capabilities that would require significant development effort in self-managed Backstage.
Adoption accelerators: Customers can choose to create and manage catalog entities through Git, or just through the UI without needing a YAML in Git. Harness IDP also offers a powerful entity management API which unlocks significant automation potential for auto-discovery, auto-population, and building CLIs or Terraform providers.
We provide a seamless migration path for organizations already running Backstage, ensuring a smooth transition without data loss.
The choice ultimately comes down to build versus buy. While self-managed Backstage feels attractive due to its open source nature, Harness IDP delivers enterprise-grade capabilities with significantly lower total cost of ownership, allowing platform teams to focus on strategic initiatives rather than infrastructure maintenance. Our Ebook What To Consider When Building an IDP using Backstage explores this topic in depth for those interested in a deep dive.
Detailed feature comparison
Catalog
Catalog
Self Managed Backstage
Harness IDP
Notes
Create/Update entities via YAML
Yes
Yes
Create/Update entities via UI
No
Yes
With Harness Git Experience, entities can be updated bidirectionally between UI and YAML.
Custom Data Model
Limited
Roadmap
Automated Discovery
No
Roadmap
Workflows
Workflows
Self Managed Backstage
Harness IDP
Notes
Workflow Groups and Customizable UI
No
Yes
Organize workflows into groups based on use cases. Recommend Golden Paths to developers and make IDP your Self Service Hub
Custom UI Pickers
Yes
Yes
Implemented through the Dynamic Workflow picker framework, providing advanced UI customization capabilities
Pipeline orchestrator
Limited
Yes
Harness IDP integrates the enterprise-grade Harness pipeline orchestrator as a core component, providing significantly enhanced capabilities compared to the Backstage Scaffolder backend.
Custom action/step
Limited
Yes
Scaffolder Actions in Backstage execute in the same environment as the portal itself, creating potential security vulnerabilities. These actions have inherent limitations in functionality, language support, and RBAC implementation. In contrast, Harness Pipelines provide enterprise-grade security, extensive customization options, and comprehensive support for diverse execution requirements.
Isolation of infrastructure for executions
No
Yes
Harness IDP provides dedicated execution infrastructure, isolating workflow executions from the application environment. This prevents infrastructure changes from disrupting ongoing workflow executions, unlike Backstage where Scaffolder tasks share infrastructure with the application itself.
Native integration with Jira/Slack/ServiceNow/etc.
No
Yes
Long running processes as part of the step
No
Yes
Harness Pipelines support long running steps and customizable timeouts.
Support for human interaction during execution
No
Yes
Several types of manual interactions are supported, including approvals that are triggered manually, through Jira or ServiceNow or via other custom triggers.
Define failure Strategy or Conditional executions
Limited
Yes
Scorecards
Scorecards
Self Managed Backstage
Harness IDP
Notes
Service Scorecards
Limited
Yes
Parsing support for file-content based checks
No
Yes
Plugins
Plugins
Self Managed Backstage
Harness IDP
Install and configure plugins
Yes
Yes
Customize Catalog layout using plugins
Yes
Yes
Write custom frontend plugins
Yes
Yes
Write custom backend plugins
Yes
No
Governance and security
Governance and Security
Self Managed Backstage
Harness IDP
Role Based Access Control
No
Yes
Approval gates via Jira/ServiceNow/etc. for workflows
No
Yes
Role Based Access Control
No
Yes
Open Policy Agent based Policies
No
Yes
Audit Trails
No
Yes
Integration with Secret Managers (AWS, GCP, Vault, etc.)
No
Yes
Platform
Platform
Self Managed Backstage
Harness IDP
User and Group Management UI
No
Yes
Ingestion of Users, User Groups and Roles from different sources (LDAP, AD, SCIM, etc.)
Limited
Yes
Single Sign-On
Limited
Yes
Custom Dashboards for Key Adoption Insights
No
Yes
Scheduled executive reports
No
Yes
Alerting based on metrics trends
No
Yes
Project and Org based hierarchy of entities
No
Limited
Miscellaneous
Miscellaneous
Self Managed Backstage
Harness IDP
Customize UI theme colors
Yes
Roadmap
AI assisted onboarding and workflows
No
Roadmap
Availability of Backstage customizations in Harness IDP
All Backstage customizations and their availability in Harness IDP
Self Managed backstage
Harness IDP
Note there are no interfaces for these customizations, and all of these require you to implement it yourself using code
Add or remove plugins
Yes
Yes
Write your own plugins
Yes
Yes
Frontend and Proxy backend only. Custom backends should be hosted by customers internally as a separate service or lambda.
Write your own scaffolder/workflow actions
Yes
No
Scaffolder Action is a backend functionality and runs in the same environment where the IDP executes. Support for custom scaffolder action allows users to get access to the system and execute malicious code in our systems. Scaffolder actions are also limited by what they can do, what programming language to use, how to setup RBAC, etc. Harness Pipelines are already configured to support such enterprise-grade requirements with even more customizations available.
Custom UI pickers in Scaffolder (Field Extensions)
Yes
No
You can use Dynamic Pickers as well as other supported open-source Workflow UI Pickers. If you need support for any other UI picker available in open source, submit a request on canny.
Catalog Dependency graph
Yes
Yes
Custom entity providers
Yes
Roadmap
Custom entity kinds
Limited
Roadmap
Custom catalog processors
Yes
Roadmap
Custom colors and themes
Yes
Roadmap
Search - bring your own index
Yes
No
Search results UI
Yes
No
Custom permissions policy using Backstage permissions framework
Yes
Limited
Extensibility and flexibility
Harness IDP maintains compatibility with the Backstage Plugins marketplace, supporting rapid enablement of additional plugins upon customer request. Our managed plugin deployment approach addresses the majority of extensibility requirements while maintaining system integrity and security.
Our custom plugins framework enables organizations to develop custom frontend plugins that can be deployed via package upload or npm registry integration.
For advanced customizations, Harness IDP provides a comprehensive, secure Ingestion API which enables dynamic entity definition updates without compromising platform security. This is a strategic alternative to Backstage's custom entity providers and custom catalog processors, which require complex TypeScript implementations.
Comprehensive guide: Migrating from Backstage to Harness IDP
Migrating from a self-managed Backstage instance to Harness Internal Developer Portal (IDP) can significantly streamline your developer experience, centralize governance, and unlock advanced capabilities. The migration process will vary in complexity based on the extent of customizations in your current Backstage setup. This guide provides a step-by-step approach to ensure a smooth transition, highlighting key considerations and Harness IDP features that can replace or enhance your existing developer portal.
Note: This guide focuses on the technical migration steps. For a holistic adoption strategy, refer to our Adoption Playbook.
Platform migration
Step 1: Authentication and authorization
Harness IDP leverages the robust Harness Platform authentication and authorization framework. You can seamlessly integrate your existing identity providers (such as LDAP, SSO, or Azure Entra ID) to ingest users and groups, and synchronize roles. This eliminates the need for custom sign-in resolvers and user/group entity providers previously required in Backstage, centralizing identity management and enhancing security.
Step 2: Connectivity via Harness delegate
Unlike Backstage, which operates within your infrastructure, Harness IDP is delivered as a hybrid SaaS offering. To securely connect Harness IDP and its plugins to your internal systems (e.g., source code repositories, infrastructure, services), deploy a Harness Delegate. The delegate acts as a secure proxy, ensuring seamless and controlled access to internal resources without exposing them directly to the cloud.
Step 3: Role-based access control (RBAC)
Harness IDP provides a powerful, integrated RBAC system. If you have been using Backstage’s permissions framework, you can transition to Harness RBAC to manage access policies at scale. Harness RBAC simplifies the assignment of roles and permissions, supporting granular access control across users, teams, and resources.
Step 4: Branding and customization
While full theme customization is not currently supported, Harness IDP offers Home Page Customizations to help you personalize the portal’s appearance and reinforce your organization’s brand identity.
Catalog migration
Step 1: Entity migration
Harness IDP provides an Entity Conversion API to automate the transformation of Backstage entity YAMLs into Harness IDP Catalog YAMLs. You can use the Backstage Locations API to enumerate all entity YAML files, then convert and import them into Harness using the Harness Git Experience. This ensures continuity and consistency in your software catalog.
Step 2: Plugin enablement and migration
Harness IDP features a comprehensive plugin marketplace that enables seamless integration of Backstage plugins into your environment. For organizations with custom plugin requirements, our custom plugins documentation provides detailed implementation guidance. In cases where plugins require backend services or database connectivity, you can leverage the delegate proxy architecture to establish secure communication channels between Harness IDP and your self-hosted backend components.
Step 3: Catalog layout customization
With the Entity Layout Editor, you can tailor the user interface of catalog entity pages. Arrange plugins, widgets, and sidebar navigation to create an optimal experience for your teams.
Step 4: Custom metadata ingestion
If you have developed custom catalog processors in Backstage to enrich entity metadata, Harness IDP offers Catalog Ingestion APIs to programmatically push additional metadata. This enables you to maintain or enhance your metadata enrichment workflows without modifying entity YAML files.
Step 5: Custom entity providers
For scenarios where entities are created directly in the catalog (bypassing YAML files), Harness IDP’s Entities API allows you to create and manage catalog entities programmatically, supporting advanced automation and integration use cases.
Workflow (aka software templates) migration
Step 1: Workflow definition and migration
Harness IDP Workflows extends the Backstage Scaffolder concept, retaining a familiar UI while leveraging Harness Pipelines as the backend. Use the Entity Conversion API to convert Backstage template YAMLs to Harness IDP Workflow YAMLs, enabling you to recreate and enhance your existing workflows.
Step 2: Migrating custom scaffolder actions
If you have implemented custom scaffolder actions in Backstage, Harness IDP allows you to replicate this functionality using the built-in “Run” step in Harness IDP pipelines. This step supports execution of any containerized code (e.g., scripts written in Python, Go, shell, etc.), providing flexibility and extensibility while maintaining proper isolation and security controls.
Step 3: Custom UI pickers
If you have implemented custom UI fields in Backstage, you can leverage workflow dynamic pickers to replicate the behavior of those fields. Harness IDP also supports conditional API requests, further enhancing your custom UI fields.
Last updated
Was this helpful?