Cycloid today unveiled an internal developer platform (IDP) that has been re-engineered for the agentic artificial intelligence (AI) era.

Company CEO Benjamin Brial said the Cycloid Internal Developer Portal & Platform (IDPP) now provides self-service capabilities to both AI agents and human application developers with every action having to be approved using existing policies and workflows to create an audit trail.

The overall goal is to make it possible for platform and DevOps engineering teams to centrally manage what tools and resources are being accessed at a time when the overall pace at which code is being created has exponentially increased, he added. The revamped Cycloid IDPP provides a more opinionated approach toward enabling those teams to govern workflows, noted Brial.

The Cycloid IDPP provides access to a set of reusable blueprints that application developers and AI agents, via a Model Context Protocol (MCP) server, can use to provision infrastructure, deploy services and perform other tasks based on permissions, approvals and policies defined by a platform or DevOps engineering team.

The Cycloid IDPP can be invoked using a Native Runner it provides or integrated with a continuous integration (CI) pipeline or existing IT automation framework such as Ansible. It can be deployed in a self-hosted IT environment or accessed as a software-as-a-service (SaaS) application.

In general, platform and DevOps engineering teams in the agentic AI era are trying to strike a balance between productivity, governance, efficiency, security, resiliency and cost, said Brial. The Cycloid IDPP platform is designed to allow each of those teams to achieve those goals as they best see fit, he added.

It’s not clear how many software engineering teams have adopted some type of IDP that enables developers to construct an application environment within the context of a set of tools and platforms that the organization has decided to standardize on. The challenge is that, historically, each individual team has tended to build their own DevOps platform that over time increases the cost of application development. An IDP promises to make it possible to manage DevOps workflows at higher levels of scale.

At this juncture, it’s only a matter of time before software engineering teams re-visit existing workflows. More code than ever is being created, but the tools used to generate it can be costly to run. Each organization will need to determine to what degree they will want to embrace best platform engineering practices as enabled by an IDP, but it’s apparent that allowing each application development team to maintain an isolated environment isn’t cost effective.

Additionally, there is now more pressure than ever to ensure that compliance mandates are being followed in the wake of a series of attacks against software supply chains.

There is, of course, at this juncture no shortage of options when it comes to IDPs. The issue now is determining which approach is going to meet the least resistance possible from application developers that in many cases continue to jealously guard their prerogatives.

SHARE THIS STORY