> ## Content Index
> Fetch the complete content index at: https://stalin-pereira.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Building an Internal Developer Platform (IDP) with Backstage
- URL: https://stalin-pereira.com/building-an-internal-developer-platform-idp-with-backstage/
- Published: 2025-12-11T10:46:00.000Z
- Updated: 2026-10-16T19:08:12.000Z
- Description: The rise of Internal Developer Platforms (IDP) to reduce cognitive load
- Author: Stalin Pereira
- Tags: DevOps

**DevOps Failed the Developer**

Why 'You build it, you run it' became a nightmare.

## The 'Cognitive Load' Problem

- **The Expectation** — We asked Devs to know Java, AND Terraform, AND Kubernetes, AND AWS networking.
- **The Reality** — They are drowning. They just want to ship code, not manage VPC subnets.
- **The Symptom** — Shadow IT. Developers spinning up insecure resources because 'DevOps is too slow'.

## Enter Platform Engineering

- **The Shift** — Treat your internal platform as a Product. Your developers are the Customers.
- **The Goal** — Golden Paths. The 'Path of Least Resistance' should also be the secure path.

## The Solution: IDP (Backstage)

Spotify's open-source portal is the standard.

- **Unified Portal** — One website where devs can see ALL their services, docs, and pipelines.
- **Service Catalog** — A searchable inventory. 'Who owns the Payment Service? What API version is it on?'

## The 'Click to Create' Magic

- **Templates** — Dev selects 'New Microservice'. They get a repo, CI/CD pipeline, and hello-world code.
- **Standardization** — Every new service uses the approved logging and security libraries automatically.
- **Self-Service** — No Jira ticket to DevOps. It happens in 5 minutes via the IDP.

## Architecture: The Plugin System

- **Aggregator** — Backstage doesn't replace tools (Jenkins, ArgoCD); it aggregates them.
- **Plugins** — Widgets show CI status, Cloud costs, and API docs on one page.

## Why VPs Love This

- **Onboarding Speed** — New hires ship their first code on Day 1, not Week 3.
- **Governance** — You know exactly what software is running where. No more 'Orphaned Instances'.

## The Trap: Building a Frankenstein

- **Warning** — Don't just install Backstage and leave. It requires a dedicated team to maintain.
- **Adoption** — If the platform is harder to use than AWS Console, devs won't use it.

## Summary: Scale the Happy Path

Make doing the right thing the easiest thing.

> Don't hire more DevOps. Build a better platform.

---

Is your DevOps team a bottleneck or an enabler?