Harness releases its Internal Developer Portal in public preview, offering enhanced developer self-service and streamlined service management. Powered by Backstage, it features powerful pipelines, robust security measures, and an intuitive software catalog to simplify and accelerate development workflows.
Note: Harness Internal Developer Portal has graduated from Public Preview to GA.
Three months ago, we announced the Beta release of our Internal Developer Portal (IDP) module to elevate the Developer Experience and streamline Platform Engineering practices. Today, we are thrilled to announce the Public Preview release! We couldn't have reached this milestone without the support and invaluable feedback from our early adopters. Thank you for helping us in building the best and most beloved Software Delivery Platform.
At Harness, we understand that success is a collaborative effort. During our Beta release, we joined forces with dozens of our customers, most of whom were dedicated Platform Engineers and DevOps enthusiasts. Together, we aimed to tackle common challenges and make the developer's journey smoother. Some of them built developer Self-Service Flows to improve new service onboarding time by 100x - from weeks to minutes. While many used the Software Catalog to organize their internal software ecosystem and reduce cognitive load for developers. Let’s dive deeper into these use-cases of Harness IDP, what is new and what is about to come.
Expert research analysts like Gartner predict that in a couple of years, 75% of organizations will have a self-service developer portal. We are already witnessing this transformation among our customers. Self-service means that developers spend more time building features for their customers, rather than being blocked on other people and manual processes. It is critical in go-to-market time for newer projects in many companies.
Harness IDP empowers organizations to achieve developer self-service in a number of ways -
In today’s fast growing microservices–based world, a Software Catalog is foundational. Catalog is a core feature of Harness IDP. And that is why instead of reinventing the wheel and the standard, we adopted the most popular and highly scalable catalog out there. Our IDP is powered by the popular CNCF incubating project Backstage.io. The YAML specification for defining software components is extremely flexible and widely adopted in the industry. Catalog also brings the UI to create a single pane of glass for every software component. Here’s what our customers love about the software catalog -
Platform Engineers work very hard to establish best practices within their org, but lack tools of enforcement. They fail to measure if their internal services are keeping up with them. Whether these are DevOps standards or just development best practices, it’s important for developers to be aware of them and how to take actions. Here are couple of use-cases that Harness IDP Scorecards helps you solve -
Throughout our journey from Beta to Public Preview, we have prioritized rapid customer feedback and implementation, addressing requests within days at times. We are committed to evolving our IDP with a rapid pace. Here are some of the features that we have added since Beta -
This doesn’t include dozens of bug fixes and system improvements! All our technical documentation can be found on developer.harness.io including tutorials and release notes.
Our journey with IDP is far from over and we are innovating at a rapid scale. Here is a small list of what is coming next in Harness IDP -
Our roadmap is based on all the feedback we have received so far but is not set in stone. YOU can influence the roadmap today, by signing up to try Harness IDP.
We invite you to explore our Internal Developer Portal (IDP) and experience the future of Platform Engineering. Check out more details about the product on harness.io and request for a demo. If you have any questions or want to share your thoughts, feel free to directly email us at idp-interest@harness.io.
Learn more about the breadth and depth of technology factors you’ll need to consider when thinking about improving your developer experience.