Self-Service Infrastructure
Model where development teams can provision and manage infrastructure autonomously through automated interfaces, without depending on operations tickets.
seed#self-service#infrastructure#automation#platform#provisioning
What it is
Self-service infrastructure allows developers to create, modify, and destroy infrastructure resources without opening tickets or waiting for an operations team. The platform provides controlled interfaces with automatic guardrails.
Models
| Model | Mechanism | Example | Best for |
|---|---|---|---|
| Templates | Catalog of pre-approved configurations | Backstage Software Templates | Teams creating new services |
| GitOps | PR to infra repo → automatic deployment | ArgoCD + Terraform | Teams with Git experience |
| Portal | Web UI with forms | Backstage, Port, Humanitec | Teams preferring visual interfaces |
| CLI | Commands to provision | platform create service --type=api | Developers preferring the terminal |
Guardrails
Self-service doesn't mean no control:
- Cost policies (limits per team)
- Automatic compliance (encryption, mandatory tags)
- Approvals for high-cost resources
- Automatic TTL for temporary environments
Benefits
- Eliminate operations bottlenecks
- Reduce provisioning time from days to minutes
- Standardize configurations
- Empower development teams
Why it matters
Self-service infrastructure eliminates the bottleneck of tickets to platform teams. When developers can provision what they need through controlled interfaces, delivery velocity increases without sacrificing governance.
References
- Platform Engineering — Community.
- Humanitec Platform Orchestrator — Humanitec, 2024. Platform orchestrator for self-service infrastructure.
- Software Templates — Backstage — Backstage, 2024. Templates as a self-service mechanism.