logo
Harness launches IDP 2.0 to boost developer speed & security

Harness launches IDP 2.0 to boost developer speed & security

Techday NZ12-06-2025
Harness has launched version 2.0 of its Internal Developer Portal (IDP) with a suite of updates designed to improve software delivery speed, quality, security, and the overall developer experience at enterprise scale.
The latest release builds on the Backstage framework, a Cloud Native Computing Foundation project, and rolls out new features directed at large organisations. The update targets issues seen in previous portals, such as managing complexity, providing scalablility, and unifying fragmented developer experiences.
Enterprise-focused enhancements
Key additions in the updated Harness IDP include fine-grained Role-Based Access Control (RBAC), which provides tighter security and compliance. The RBAC system allows platform teams to specify exactly who can read, create, edit, delete, or execute particular services or workflows at a granular level. For companies in regulated sectors such as finance or healthcare, this is an essential tool for governance.
The release notes, "In large organisations, access boundaries must be explicit. IDP now supports entity-level granular Role-Based Access Control (RBAC), so platform teams can define exactly who can read, create, edit, delete, or execute a given service or workflow. For companies in regulated industries, like financial services or healthcare, this level of control is essential for compliance and risk management. Imagine a company whose services require restricted access due to regulatory constraints. With RBAC, only the compliance engineering team can modify those entities, while broader developer groups can view, but not alter, related documentation or dependencies."
The updated portal has also been integrated with real-time Git synchronisation, supporting webhooks for immediate updates to YAML configuration files. This eliminates the need for polling or manual refreshing and supports OAuth and central tokens for flexible authentication across all major Git providers.
Harness explains, "For organisations with large, distributed engineering teams, keeping the developer portal in sync with Git can quickly become a bottleneck. Harness IDP now supports real-time updates via webhooks when YAML config files are updated in Git, eliminating the need for polling or manual refreshes. Teams can also make edits directly in the portal UI and push those changes back however they prefer, either directly or through a pull request. Authentication is flexible, with support for OAuth and central tokens, and it works with all major Git providers."
Usability for large teams
The new release aligns the entity organisation in the Harness-Native Platform Hierarchy, mapping catalog entities and workflows to real-world structures such as project, organisation, or account-level groupings. This enables tailored visibility for teams according to their functional or geographic targets, reducing clutter and the risk of error.
Harness states, "Harness IDP now aligns with our native platform hierarchy, enabling teams to create catalog entities and workflows at the Project, Organisation, or Account level. This mirrors how engineering teams are actually structured - by product line, business unit, or geography - so developers see only what's relevant to their work."
In addition to architectural changes, the user interface of the portal's catalog has been redesigned for greater clarity and efficiency. Developers are now able to filter services based on specific relevance, such as ownership or technology, and view integrated scorecards within the catalog. Metrics include service maturity, security compliance, and readiness for production.
On this point, the company shared the comment, "With this release, the IDP catalog has been redesigned for speed, clarity, and scale. Teams can now filter views based on what matters to them, like services they own or APIs used across the organisation. Scorecards are now built directly into the catalog view, giving developers and platform teams immediate visibility into key metrics like service maturity, security standards alignment, and production readiness. Each entity page clearly shows scope, ownership, and references, making it easier for teams to stay organised and aligned."
Onboarding and automation
The update introduces a guided, form-based approach to creating and managing catalog entities, in addition to continued support for YAML-in-Git workflows. The shift is aimed at easing barriers for engineers unfamiliar with configuration syntax and fostering wider platform adoption. The company remarked, "Catalog entities can now be created and managed directly through the Harness IDP UI using a guided, form-based experience – no YAML required. This removes a major barrier for developers unfamiliar with configuration syntax, making it easier for more teams to get started and contribute. For those who prefer a config-as-code workflow, the traditional YAML-in-Git approach is still fully supported."
For larger-scale organisations that depend on automation, Harness IDP now offers additional APIs allowing automatic catalog entity creation, auto-discovery, CLI integration, and Terraform provider support. Harness noted, "While UI is great for onboarding or making quick updates, large-scale adoption often demands automation. Harness IDP now includes new APIs to create and manage catalog entities, unlocking use cases like auto-discovery, auto-population, CLI integration, and Terraform provider support. The existing Catalog Ingestion API remains unchanged and will continue to function as before."
Backstage plugin compatibility
The IDP continues to extend compatibility with Backstage open-source plugins and supports teams seeking to build bespoke plugins on the framework. The company wrote, "Harness IDP continues to extend the Backstage open-source framework, so teams can keep using the Backstage plugin ecosystem they already know, or build their own custom plugins. Best of both worlds!" "With this major release of Harness IDP, we're redefining what an enterprise-grade internal developer portal can be. Extended from the Backstage framework and supercharged for scale, Harness IDP now delivers real-time Git synchronisation, true org-level hierarchy, API-first extensibility, and the most powerful RBAC system in the category. Whether you're supporting 100s or 1,000s of developers, Harness IDP gives platform teams the structure, speed, and control they need to transform developer experience at the enterprise level – without compromise."
The series of updates are positioned to support organisations looking to scale software delivery without increasing risk or operational overhead for developer and platform teams.
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

AWS brings vibe coding to the Enterprise with spec-driven Kiro IDE tool
AWS brings vibe coding to the Enterprise with spec-driven Kiro IDE tool

Techday NZ

time18-07-2025

  • Techday NZ

AWS brings vibe coding to the Enterprise with spec-driven Kiro IDE tool

AWS has introduced Kiro, an "agentic IDE" designed to bridge the gap between the excitement of prompt-based prototyping and the practical demands of production software. According to Kiro product lead Nikhil Swaminathan, the tool aims to bring structure, rigour and automation to the modern, AI-powered coding process. Swaminathan describes the appeal of recent AI tools, saying, "Prompt, prompt, prompt, and you have a working application. It's fun and feels like magic. But getting it to production requires more." He outlines the typical stumbling blocks: "What assumptions did the model make when building it? What edge-cases did it cover? How did it handle errors? Requirements are fuzzy and you can't tell if the application meets them." Kiro is designed to solve these problems by introducing what its creators call "spec-driven development." As the team puts it, "Kiro is great at 'vibe coding' but goes way beyond that - Kiro's strength is getting those prototypes into production systems with features such as specs and hooks." Swaminathan explains how it works: "Start with a prompt: 'Add a review system for products.' Kiro translates this into a set of user stories with EARS-style acceptance criteria." He says Kiro then generates artefacts including "a data-flow diagram, TypeScript interfaces, a database schema, and API definitions." The system's approach includes automatically specifying essential features for each user story. Swaminathan writes, "Kiro automatically includes requirements like mobile responsiveness, accessibility, loading states, and tests in the spec." Tasks are then "sequenced correctly and connected to requirements." Importantly, the specs remain in sync as the code evolves. Swaminathan notes, "Developers can author code and ask Kiro to update specs or manually update specs to refresh tasks. This solves the common problem where developers stop updating original artifacts during implementation." To automate repetitive work, Kiro introduces "agent hooks." These are "event-driven automations" that "trigger based on events like file saves or deletions." As Swaminathan puts it, "When you save a React component, hooks update the test file. When you modify API endpoints, hooks refresh README files. When you're ready to commit, security hooks scan for leaked credentials." He describes the benefit: "It's like having an experienced developer catching things you miss or completing boilerplate tasks." These hooks are also collaborative by design. Swaminathan explains, "Once this hook is committed to Git, it enforces the coding standard across my entire team - whenever anyone adds a new component, the agent automatically validates it against the guidelines." Kiro is built on top of Code OSS, meaning it is "compatible with existing VS Code settings and Open VSX plugins." It supports "Model Context Protocol (MCP)," agentic chat, and multiple context providers, including "files, URLs and document uploads." Looking ahead, Swaminathan and AWS VP of Developer Experience & Agents Deepak Singh set out an ambitious vision for Kiro. They write, "We want to tackle the root causes of pain in software development - clarity of design, alignment with requirements, technical debt, code reviews, and knowledge sharing." Kiro is available in a preview release for Mac, Windows and Linux, supporting most programming languages. Swaminathan invites developers to experience its approach: "We invite you to try Kiro and share feedback. We're just getting started, and your input will help shape the future of agentic development." By combining the "magic" of AI-powered coding with structured specs and event-driven automation, Kiro is positioning itself as a tool for developers seeking to move quickly without sacrificing discipline or reliability.

AWS brings vibe coding to the Enterpise with spec-driven Kiro IDE tool
AWS brings vibe coding to the Enterpise with spec-driven Kiro IDE tool

Techday NZ

time18-07-2025

  • Techday NZ

AWS brings vibe coding to the Enterpise with spec-driven Kiro IDE tool

AWS has introduced Kiro, an "agentic IDE" designed to bridge the gap between the excitement of prompt-based prototyping and the practical demands of production software. According to Kiro product lead Nikhil Swaminathan, the tool aims to bring structure, rigour and automation to the modern, AI-powered coding process. Swaminathan describes the appeal of recent AI tools, saying, "Prompt, prompt, prompt, and you have a working application. It's fun and feels like magic. But getting it to production requires more." He outlines the typical stumbling blocks: "What assumptions did the model make when building it? What edge-cases did it cover? How did it handle errors? Requirements are fuzzy and you can't tell if the application meets them." Kiro is designed to solve these problems by introducing what its creators call "spec-driven development." As the team puts it, "Kiro is great at 'vibe coding' but goes way beyond that - Kiro's strength is getting those prototypes into production systems with features such as specs and hooks." Swaminathan explains how it works: "Start with a prompt: 'Add a review system for products.' Kiro translates this into a set of user stories with EARS-style acceptance criteria." He says Kiro then generates artefacts including "a data-flow diagram, TypeScript interfaces, a database schema, and API definitions." The system's approach includes automatically specifying essential features for each user story. Swaminathan writes, "Kiro automatically includes requirements like mobile responsiveness, accessibility, loading states, and tests in the spec." Tasks are then "sequenced correctly and connected to requirements." Importantly, the specs remain in sync as the code evolves. Swaminathan notes, "Developers can author code and ask Kiro to update specs or manually update specs to refresh tasks. This solves the common problem where developers stop updating original artifacts during implementation." To automate repetitive work, Kiro introduces "agent hooks." These are "event-driven automations" that "trigger based on events like file saves or deletions." As Swaminathan puts it, "When you save a React component, hooks update the test file. When you modify API endpoints, hooks refresh README files. When you're ready to commit, security hooks scan for leaked credentials." He describes the benefit: "It's like having an experienced developer catching things you miss or completing boilerplate tasks." These hooks are also collaborative by design. Swaminathan explains, "Once this hook is committed to Git, it enforces the coding standard across my entire team - whenever anyone adds a new component, the agent automatically validates it against the guidelines." Kiro is built on top of Code OSS, meaning it is "compatible with existing VS Code settings and Open VSX plugins." It supports "Model Context Protocol (MCP)," agentic chat, and multiple context providers, including "files, URLs and document uploads." Looking ahead, Swaminathan and AWS VP of Developer Experience & Agents Deepak Singh set out an ambitious vision for Kiro. They write, "We want to tackle the root causes of pain in software development - clarity of design, alignment with requirements, technical debt, code reviews, and knowledge sharing." Kiro is available in a preview release for Mac, Windows and Linux, supporting most programming languages. Swaminathan invites developers to experience its approach: "We invite you to try Kiro and share feedback. We're just getting started, and your input will help shape the future of agentic development." By combining the "magic" of AI-powered coding with structured specs and event-driven automation, Kiro is positioning itself as a tool for developers seeking to move quickly without sacrificing discipline or reliability.

Harness launches AI Test Automation for faster DevOps testing
Harness launches AI Test Automation for faster DevOps testing

Techday NZ

time26-06-2025

  • Techday NZ

Harness launches AI Test Automation for faster DevOps testing

Harness has announced the general availability of its AI Test Automation product, aiming to address the challenges of software testing in fast-paced DevOps environments. According to Harness, the AI Test Automation solution has been developed in response to the increasing strain placed on QA and DevOps teams as organisations speed up feature delivery via AI-generated code. These accelerated product cycles have heightened the demand for faster, more resilient testing approaches, with many organisations still largely reliant on manual processes. Testing bottlenecks The company cited industry statistics showing that although significant investment is made in software QA, around 70 to 80% of organisations continue to use manual testing methods. These approaches, Harness noted, have become key obstacles in automated delivery pipelines, introducing both delays and additional risk by failing to keep pace with changes to software and infrastructure. AI Test Automation incorporates automated, self-healing testing designed to adapt to real-time changes in user interfaces, workflows, and environmental variables. Automated tests are maintained without manual intervention, replacing what the company terms "outdated" test frameworks with a more adaptive approach. Intent-based testing The solution allows users to create tests in natural language with no need for code scripting, using what Harness describes as intent-based test creation. QA and development personnel can type test descriptions, such as "Did the login succeed?", while the AI system generates, validates, and maintains the necessary test cases. Visual testing features and adaptive selectors are advertised as cutting test creation time by up to 90% and reducing test flakiness by up to 70%. Sushil Kumar, Head of Business, AI Test Automation at Harness, said: Traditional testing methods struggled to keep up, it is too manual, fragile, and slow. So we've reimagined testing with AI. Intent-based testing brings greater intelligence and adaptability to automation, and it seamlessly integrates into your delivery pipeline. The platform includes live test authoring, visual testing, and automated assertion generation. Tests may be maintained automatically when UI or workflow changes occur, using AI-generated selectors and Smart Selector technology. Automatic translation of environment variables is designed to enable stable tests to run across different environments without reconfiguration. Efficiency and integration Harness AI Test Automation operates within the company's existing CI/CD pipelines to promote a shift-left testing strategy. The product supports parallel test execution and data-driven workflows at scale, while maintaining security requirements such as SOC 2 Type 2 compliance. For advanced scenarios, users can still leverage custom JavaScript or Puppeteer scripts, combining no-code capabilities with traditional flexibility. The system's automated approach is intended to help organisations optimise their resources. Several customers reported notable benefits in time savings and test coverage. For example, Wasimil, a hotel booking and management platform, reported halving its test maintenance time and doubling its automation coverage. Customer feedback Rohan Gupta, Principal Product Manager at Harness, described the internal usage of the solution: With AI Test Automation, I just literally wrote out and wireframed all the test cases, and in a matter of 15–20 minutes, I was able to knock out one test. Using the templating functionality, we were able to come up from a suite of 0 to 55 tests in the span of 2 and a half weeks. Amrita Majumder, Lead QA Engineer at Siemens Healthineers, shared a similar experience: We could just see in the browser exactly where it went wrong and directly edit that step. That was really fast and quick. Tom, CTO at Wasimil, commented on the impact on product development focus: With AI Test Automation, we could ship features, not just bug fixes. We don't wanna spend 30 to 40% of our engineering resources on fixing bugs because we can't be proud to ship bug fixes to our customers. Right? And they expect features, not bug fixes. Industry positioning Harness states that the AI Test Automation product achieves a fully automated software delivery platform within a single environment, supporting automated build, test, and deployment workflows. The company highlights reported outcomes including faster test creation, reduced maintenance, accelerated release cycles, and improved developer experience in enterprise software environments.

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into a world of global content with local flavor? Download Daily8 app today from your preferred app store and start exploring.
app-storeplay-store