Why a platform

Building an Internal Developer Platform is a shared journey, for humans and agents

Por que uma plataforma

Construir uma Internal Developer Platform é uma jornada compartilhada, para humanos e agentes

Developer friction

Who absorbs the complexity today?

Fricção para o dev

Quem absorve a complexidade hoje?

Developer friction · Our starting point

Infrastructure teams look after the infrastructure, and whoever has an idea still has to ask another team

Asking for infrastructure today

  • Request: to another team
  • Knowledge: documented, not self-service
Fricção para o dev · Nosso ponto de partida

Times de infraestrutura cuidam da infra, e quem tem uma ideia ainda precisa pedir a outro time

Pedir infraestrutura hoje

  • Pedido: a outro time
  • Conhecimento: documentado, não self-service
Developer friction · Who absorbs the complexity

Today people absorb the complexity one ticket at a time; a platform absorbs it once, as self-service

Who absorbs the complexity

  • Today: infra teams, one ticket at a time
  • Platform: once, as self-service
Fricção para o dev · Quem absorve a complexidade

Hoje pessoas absorvem a complexidade um ticket por vez; a plataforma a absorve uma vez, como self-service

Quem absorve a complexidade

  • Hoje: times de infra, um ticket por vez
  • Plataforma: uma vez, como self-service
Developer friction · The empathy gap

A powerful platform that is hard to use is not adopted: what is missing is empathy, not an API

The empathy gap

  • Symptom: powerful but hard to use
  • Question: how does it feel to use?
Fricção para o dev · A falta de empatia

Plataforma poderosa e difícil de usar não é adotada: falta empatia, não API

A falta de empatia

  • Sintoma: poderosa, mas difícil de usar
  • Pergunta: como é usar?
AI needs a platform

Why has AI not paid off yet?

A IA precisa de plataforma

Por que a IA ainda não deu retorno?

AI needs a platform · Throughput is not return

AI sped up writing code, but the return has not come yet for most

Since adopting AI, organizations report

  • Throughput: 38% ship 2x or more
  • Return: only 8% call it transformative

Source: State of AI in Platform Engineering, Vol. 2 (2026), pp. 20-22

A IA precisa de plataforma · Throughput não é retorno

A IA acelerou a escrita de código, mas o retorno ainda não veio para a maioria

Desde que adotaram IA, as organizações relatam

  • Throughput: 38% entregam 2x ou mais
  • Retorno: só 8% o chamam de transformador

Fonte: State of AI in Platform Engineering, Vol. 2 (2026), pp. 20-22

AI needs a platform · The blocker

The obstacle is not the model, it is the platform around it

Main blockers to scaling AI

  • #1 Platform readiness: cited by 27%
  • #4 Model capability: cited by 11%

Source: State of AI in Platform Engineering, Vol. 2 (2026), p. 24

A IA precisa de plataforma · O obstáculo

O obstáculo não é o modelo, é a plataforma ao redor dele

Principais obstáculos para escalar a IA

  • #1 Prontidão da plataforma: citada por 27%
  • #4 Capacidade do modelo: citada por 11%

Fonte: State of AI in Platform Engineering, Vol. 2 (2026), p. 24

AI needs a platform · Maturity pays in steps

Agents without rebuilding the platform yield little; rebuilding the platform yields four times more

Share that at least doubled throughput

  • Agents added (Level 1 → 2): 30% → 36%
  • Platform rebuilt (Level 2 → 3): 36% → 60%

Source: State of AI in Platform Engineering, Vol. 2 (2026), pp. 18, 21

A IA precisa de plataforma · A maturidade paga em degraus

Agentes sem reconstruir a plataforma rendem pouco; reconstruir a plataforma rende quatro vezes mais

Parcela que ao menos dobrou o throughput

  • Agentes adicionados (Level 1 → 2): 30% → 36%
  • Plataforma reconstruída (Level 2 → 3): 36% → 60%

Fonte: State of AI in Platform Engineering, Vol. 2 (2026), pp. 18, 21

AI needs a platform · AI amplifies what exists

AI amplifies the system that already exists: with a weak platform, the effect disappears

AI amplifies what exists

  • Weak platform: no effect
  • Quality platform: strong effect

Source: DORA State of AI-assisted Software Development (2025), p. 71

A IA precisa de plataforma · A IA amplifica o que existe

A IA amplifica o sistema que já existe: com plataforma fraca, o efeito some

A IA amplifica o que existe

  • Plataforma fraca: sem efeito
  • Plataforma de qualidade: efeito forte

Fonte: DORA State of AI-assisted Software Development (2025), p. 71

Platform as a product

Who is the platform for?

Plataforma como produto

Para quem é a plataforma?

Platform as a product · Developers are the customers

Treat the platform as a product: the developer is a customer, not someone who opens tickets

Developers are the customers

  • Self-service, not ticket queues
  • Enablement, not enforcement
Plataforma como produto · O dev é o cliente

Tratar a plataforma como produto: o dev é cliente, não quem abre ticket

O dev é o cliente

  • Self-service, não fila de tickets
  • Habilitar, não impor
References

Sources

Referências

Fontes

References · 1/6

The ROI of AI-assisted Software Development

DORA and Google Cloud · 2026

  • About: A framework to compute the return on AI in software delivery, built on the findings of the DORA 2025 report, with a calculator of example assumptions.
  • For this talk: It names the platform's role in the agentic era: "a platform that treats the developer—or any builder—as the user, minimizing the cognitive load required to move code from an agent's prompt to a production environment" (p. 40).
Referências · 1/6

The ROI of AI-assisted Software Development

DORA and Google Cloud · 2026

  • Sobre: Um framework para calcular o retorno da IA na entrega de software, apoiado nos achados do relatório DORA 2025, com uma calculadora de premissas de exemplo.
  • Para esta palestra: Nomeia o papel da plataforma na era agêntica: "a platform that treats the developer—or any builder—as the user, minimizing the cognitive load required to move code from an agent's prompt to a production environment" (p. 40).

https://dora.dev/ai/roi/report/

References · 2/6

The Platform Engineering Illusion

David Iyanu Jonathan · 2026

  • About: An opinion piece: internal developer platforms fail because they are run as tooling initiatives when they are a product discipline.
  • For this talk: "A technology platform is infrastructure with an API. A developer platform is a product with users." Its figures are the author's own account and stay off the screen.
Referências · 2/6

The Platform Engineering Illusion

David Iyanu Jonathan · 2026

  • Sobre: Um artigo de opinião: as plataformas internas falham porque são tocadas como iniciativas de ferramentas quando são uma disciplina de produto.
  • Para esta palestra: "A technology platform is infrastructure with an API. A developer platform is a product with users." Os números são o relato do próprio autor e ficam fora da tela.

https://platformengineering.com/features/the-platform-engineering-illusion-why-most-internal-developer-platforms-fail-before-developers-ever-use-them/

References · 3/6

The empathy gap: Why your platform needs UX, not just APIs

Tatiana Mikhaleva · 2026

  • About: An opinion piece: platforms invest in infrastructure and forget the person who uses it, and adoption stays low.
  • For this talk: "A backend engineer should not need deep Kubernetes knowledge to get a URL for their service."
Referências · 3/6

The empathy gap: Why your platform needs UX, not just APIs

Tatiana Mikhaleva · 2026

  • Sobre: Um artigo de opinião: as plataformas investem na infraestrutura e esquecem quem a usa, e a adoção fica baixa.
  • Para esta palestra: "A backend engineer should not need deep Kubernetes knowledge to get a URL for their service."

https://platformengineering.org/blog/the-empathy-gap-why-your-platform-needs-ux-not-just-apis

References · 4/6

State of AI in Platform Engineering, Volume 2

Sam Barlien, Luca Galante and Florian Lipp (Weave Intelligence) · 2026

  • About: A survey of 350 practitioners, April to August 2026, on how organizations adopt AI in platform engineering; maturity levels and gains are self-reported.
  • For this talk: "Throughput is not return" (p. 22): 38% ship at least twice as much since adopting AI, only 8% call the return transformative, and platform readiness is the first blocker (p. 24).
Referências · 4/6

State of AI in Platform Engineering, Volume 2

Sam Barlien, Luca Galante and Florian Lipp (Weave Intelligence) · 2026

  • Sobre: Uma pesquisa com 350 profissionais, de abril a agosto de 2026, sobre como as organizações adotam IA em platform engineering; os níveis de maturidade e os ganhos são autorrelatados.
  • Para esta palestra: "Throughput is not return" (p. 22): 38% entregam pelo menos o dobro desde que adotaram IA, só 8% chamam o retorno de transformador, e a prontidão da plataforma é o primeiro obstáculo (p. 24).

https://weaveintelligence.io/research/state-of-ai-in-platform-engineering-2026

References · 5/6

State of AI-assisted Software Development 2025

DORA and Google Cloud · 2025

  • About: DORA's 2025 report, a survey of 4,867 technology professionals on AI in software delivery.
  • For this talk: "AI adoption has a negligible effect on organizational performance when platform quality is low, but when platform quality is high, the effect is strong and positive" (p. 71).
Referências · 5/6

State of AI-assisted Software Development 2025

DORA and Google Cloud · 2025

  • Sobre: O relatório DORA de 2025, uma pesquisa com 4.867 profissionais de tecnologia sobre IA na entrega de software.
  • Para esta palestra: "AI adoption has a negligible effect on organizational performance when platform quality is low, but when platform quality is high, the effect is strong and positive" (p. 71).

https://dora.dev/dora-report-2025/

References · 6/6

Platform as a Product

Abby Bangser, Daniel Bryant, Colin Humphreys and Cat Morris · 2025

  • About: An O'Reilly report: a platform is a product, with users, a value proposition, a feedback loop and a focus on adoption, not an infrastructure project with a delivery date.
  • For this talk: "The model is based on enablement rather than enforcement and self-service rather than ticket queues" (p. 3). The four authors work for Syntasso, the company behind Kratix.
Referências · 6/6

Platform as a Product

Abby Bangser, Daniel Bryant, Colin Humphreys and Cat Morris · 2025

  • Sobre: Um relatório da O'Reilly: plataforma é produto, com usuários, proposta de valor, ciclo de feedback e foco em adoção, não um projeto de infraestrutura com data de entrega.
  • Para esta palestra: "The model is based on enablement rather than enforcement and self-service rather than ticket queues" (p. 3). Os quatro autores trabalham na Syntasso, a empresa por trás do Kratix.

https://www.syntasso.io/platform-as-a-product-oreilly-report