https://development.tldrecap.tech/presenters/matar-peles/ Recent content in Matar Peles on TLDRecap ⏮️ https://development.tldrecap.tech/images/tldrecap_logo.jpg https://development.tldrecap.tech/images/tldrecap_logo.jpg Hugo en Mon, 13 Apr 2026 16:36:03 -0700 https://development.tldrecap.tech/posts/2026/backstagecon-europe/ai-powered-developer-portal/ Mon, 13 Apr 2026 16:36:03 -0700 https://development.tldrecap.tech/posts/2026/backstagecon-europe/ai-powered-developer-portal/ <p><strong>Presenters</strong></p> <div> <ul> <li> <a href="https://development.tldrecap.tech/presenters/matar-peles">Matar Peles</a> </li></ul> </div> <p><strong>Source</strong></p> <div> <ul> <li> <a href="https://development.tldrecap.tech/sources/backstagecon-europe-2026">BackstageCon Europe 2026</a> </li></ul> </div> <h1 id="from-quarters-to-minutes-building-a-production-ready-idp-with-ai-">From Quarters to Minutes: Building a Production-Ready IDP with AI 🚀</h1> <p>How long does it take to build a Minimum Viable Product (MVP) for an Internal Developer Portal (IDP)? If you ask most platform engineers, you will hear a range of answers: <strong>one month</strong>, <strong>six months</strong>, or even <strong>a full year</strong>.</p> <p><strong>Matan Peles</strong>, Field CTO at <strong>Port.io</strong>, has seen this struggle firsthand while working with giants like <strong>GitHub</strong>, <strong>PwC</strong>, and <strong>CyberArk</strong>. He argues that if you do not approach the problem correctly, building a portal can consume quarters of your roadmap.</p>