The Ticket Queue That Ate Engineering Velocity
At this fast-growing SaaS company with engineering teams expected to ship continuously, the same bottleneck was quietly destroying delivery speed. Developers who needed a new environment, a test database, a deployment pipeline, or an updated access policy had to raise a ticket. Then wait. The infrastructure team was small, responsive, and completely overwhelmed.
The numbers told a clear story: engineers were spending 60% of their time on infrastructure requests rather than product work. Environment provisioning took anywhere from two days to two weeks depending on queue depth. Complex deployments required manual sign-off at three separate stages. Security reviews were done by one person who was already stretched across multiple teams.
The instinct was to hire more infrastructure engineers. But adding people to a broken process rarely fixes the process, it just gives you a larger, more expensive bottleneck. The real fix was removing the bottleneck entirely.
"We weren't slow because our engineers weren't talented. We were slow because every environment request, every pipeline change, every access review went through the same two people. It was a structural problem, not a skills problem."
, VP of Engineering (anonymised)
Build the Platform, Not Just the Tooling
The concept of an Internal Developer Platform gets oversimplified. Most organisations interpret it as "install Backstage and add some service catalogue entries." That interpretation misses the point entirely. A platform is not a tool, it's an opinionated set of workflows that encode your organisation's standards into self-service actions. The goal is to make doing things the right way the easiest way.
We started with a three-week discovery phase across both engineering organisations. Not to audit tools, there were plenty of tools already, but to map every interaction that required a human intermediary. Every ticket category, every Slack DM to the platform team, every approval workflow that blocked a deployment. That map became the backlog for the platform build.
The outcome was an IDP built on Backstage, with Crossplane for infrastructure provisioning, ArgoCD for GitOps delivery, and OPA for automated policy enforcement. The platform didn't replace the infrastructure team, it multiplied them. Every golden path they defined meant hundreds of future requests that never needed to touch a human.
Golden Paths with Backstage
Backstage served as the developer portal, a single pane of glass for service ownership, documentation, and self-service actions. We built software templates for the most common request types: new microservice scaffolding, environment provisioning, database creation, pipeline setup. Each template was opinionated by design: it came pre-configured with the company's security baseline, observability stack, and cost tagging standards.
The templates weren't restrictive, developers could fork them and customise. But the defaults were good enough that most teams used them as-is, which meant every new service started production-ready rather than needing a subsequent hardening pass. The act of choosing a template became the act of applying policy.
Self-Service Environments in Under 15 Minutes
Environment provisioning was the single highest-friction item in the original backlog. Developers needed environments for feature branches, integration testing, performance testing, and QA handoffs. Each request involved specifying requirements, waiting for approval, waiting for provisioning, and often discovering that the environment didn't quite match what was needed, triggering another cycle.
With Crossplane compositions backed by the Backstage software templates, environment provisioning became a form submission. Developers selected an environment type (feature, staging, performance), specified the services they needed, and clicked deploy. Crossplane handled the cloud resource creation, network configuration, and secret injection. The entire process took under 15 minutes, compared to the previous median of 4.5 days.
Environments were also automatically scoped: feature branch environments spun down after 24 hours of inactivity, preventing the sprawl of abandoned resources that had previously been a significant cost driver. Engineers got an automatic notification before teardown with a one-click extension if they still needed it.
Security Without the Ceremony
Automated security gates replaced the single-reviewer bottleneck. OPA policies enforced the organisation's security baseline at the point of deployment, no exceptions, no workarounds, no queue. Policies checked for common misconfigurations: public S3 buckets, missing encryption at rest, overprivileged IAM roles, containers running as root.
When a policy failed, the developer got an immediate, actionable message, not a ticket back from security, but a specific description of the violation and a link to the golden path template that would resolve it. Most issues were fixed in minutes rather than days, and many teams found that adopting the platform templates eliminated the class of violation entirely.
The security team didn't lose oversight, they gained leverage. Instead of reviewing individual requests, they wrote policies that applied everywhere at once. One security engineer could now enforce standards across a hundred deployments simultaneously, and the audit trail was automatic. Compliance evidence that previously required manual collation now generated itself.
"The shift wasn't just operational, it was cultural. Teams stopped thinking of infrastructure as something they requested and started thinking of it as something they owned. That ownership changed how they designed their services from the very first line of code."
, Head of Platform Engineering (anonymised)
Results After 90 Days
Ninety days after the platform launched, the improvement across both organisations was measurable and substantial:
- Deployment frequency: 4x increase across all product teams
- Time spent on infrastructure requests: 60% → 20% of engineering time
- Environment provisioning time: 4.5 days → under 15 minutes
- Security policy violations reaching production: down 79%
- Infrastructure ticket volume: down 85%
- Abandoned environment cost: reduced by 40% through automatic teardown
- Platform adoption: 100% of product teams using golden paths within 90 days