Thoughts about introducing internal developer platforms? The goal of DevOps at the end of the day is to not be a bottle neck and to create pace. The way you create pace is by automating everything so that developers can move at their own pace.  Wouldn't introducing IDPs be a good way to do this?  In an ideal world, DevOps engineers can template out infrastructure modules for common use cases (think containers, static sites, etc.) Developers then can just deploy the needed infrastructure that will setup and run their applications without needing to be exposed to all the intricacies of infrastructure. If this is true, wouldn't IDPs be the best abstraction layer for developers so that they're not forced to be come infrastructure experts? Has anyone here implemented / built out an IDP for your company? If so, how successful has it been?

1.3k views1 Upvote4 Comments

Director of Information Security in Energy and Utilities, 5,001 - 10,000 employees
that's pretty much this way already with fully developed CI/CD processes and YAML templates.
Creator Of The Superyacht CRM in Software, Self-employed
Ever heard of Go Highlevel CRM? Really good platform that allows for automated marketing strategies in a pipeline structure!
CSO in Software, 201 - 500 employees
Have you heard of This is exactly what they provide. 
Director of IT - Architecture, DevOps & QA in Retail, Self-employed
I implemented an opensource IDP ( recently. It was created by Spotify and now is incubated by CNCF with a growth community and several adopters. There are some PaaS solutions, if you don’t want to build an IDP on your own (look here:

My advice: bring developer teams to the table. An IDP it's not just an Ops initiative. The IDP adoption journey will be easy if you embrace other teams just in the beggining.

Content you might like

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
40.7k views131 Upvotes319 Comments

Patch management: to reduce attack surface and avoid system misconfigurations39%

Malware and ransomware prevention: to protect endpoints from social engineering attacks58%

Malware and fileless malware detection and response: to protect against malicious software49%

Threat Hunting: to detect unknown threats that are acting or dormant in your environment and have bypassed the security controls33%

Not planning to change endpoint security strategy9%



Limited environment/Infrastructure resources32%

Inability to quickly identify the root cause of CI/CD pipeline failures45%

Lack of standardized CI/CD pipeline templates across the organization54%

Integrating security tools - inefficient security implementation leading to false positives38%

Poor communication across business and product teams/coordination challenges26%

Cost/resource management26%

Implementation of CI/CD into on-going projects and workflows22%

Internal resistance: training issues, culture, etc.14%

Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.19%

Poorly written unit and acceptance testing9%