What developers want from internal developer portals
summary
Cortex claims a single system of record by automatically ingesting data from 50 integrations (GitHub, Datadog, Workday, Okta) and exposes it via Cortex Query Language to answer concrete risks — e.g., list tier‑one services affected by a bad Log4j version with no owner and no recent deploys. It adds automated scorecards, a Cookie‑Cutter‑based scaffolder, and a one‑click deploy that triggers GitHub Actions to prove self‑serve workflows increase adoption.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:24Why now
- 3:55Quality vs velocity
- 7:38Three components of an IDP
- 8:40Finding information
- 9:37Making informed decisions
- 10:26System of Record
- 13:09Catalogs
- 13:20Query language
- 13:56Prioritize action
- 14:42Scorecards
- 15:24Reporting
- 16:07Selfservice
- 17:06Actions
- 18:07Plugins
- 18:54Continuous Improvement
related talks
06mSponsored Keynote: Designing Self-Service Platforms that Engineers Actually Use
24mElevating Developer Efficiency with Developer Portal
39mDoing more with internal developer portals
37mTransforming DevEx with Internal Developer Portals
15mDeveloper portal
25mThe Developer Portal: Open the Gate to Productivity 🚀
11mBuilding Scalable Developer Platforms
27mDeveloper Platform Consoles Should Be Dumb