My company is a very large org 10,000+ developers. Our internal developer platform is a series of platforms that enable our engineers to do things like work in the cloud • provisioning/managing cloud accounts (AWS/Azure/GCP) • privileged production account access • firewall/VPC setup • role management (IAM/RBAC) • configure custom platforms We also have a more generalized platform that enable engineers to work with things like • git repos • IAC/Terraform • Artifactory/Edges • CI/CD controllers • Sonarqube • Feature Toggles • etc. I would guess our posture is fairly mature compared to most orgs, we probably have a few dozen teams that work in enablement altogether. Cloud enablement alone has an EKS, networking, security, UI, Core AWS, Core Azure team, etc. Ultimately your internal platforms are meant to solve problems though, for such a large org all of this makes sense for a smaller org this might be larger/more effort than their actual product. Have to carefully consider what features make the most sense for your use case.

cool

Sounds amazing with more than 10k+ developers. I'm curiosity, how many platform member to serve those developers ? How do you guys handle context-switching with multiple tools / biz problems / etc... ? @Angelo Carbonaro