CONCEPT Cited by 1 source
Self-service infrastructure¶
The discipline of enabling engineers to provision, configure, and tear down infrastructure environments without manual ops intervention — while maintaining central governance, cost attribution, and security controls.
Definition¶
Self-service infrastructure shifts the provisioning burden from platform/ops teams to the engineers who need the resources, mediated by a governed platform layer. The key tension: engineers need speed and autonomy; organisations need governance, cost control, and security.
Structural Properties¶
- Template-governed — provisioning paths are pre-vetted and hardened; engineers choose from a catalog, not raw IaC
- Identity-aware — every resource is attributed to an owner with purpose metadata
- Lifecycle-managed — resources have TTLs, expiration notifications, and automatic cleanup
- Observable — every provisioning action is transparent, auditable, and attributable
- Multi-tenant safe — isolation between provisioned environments prevents interference
Failure Modes of Shared Environments (That Self-Service Solves)¶
- Coordination overhead at scale — multiple engineers in one environment interfere during critical demos
- Platform-limit contention — shared catalogs/instances hit hard limits
- Cost attribution opacity — ownership unclear as usage increases
- Observability gaps — tracing what happened, when, and why requires manual investigation
Known Instances¶
| System | Scale | Approach |
|---|---|---|
| systems/databricks-fevm | 5,000+ users, 2,600+ deployments | Use-case-based provisioning via Databricks Apps + Terraform + MCP |
| Stripe Projects | Agent-provisioned accounts | CLI-driven account+service provisioning for AI agents |
Seen In¶
- sources/2026-07-23-databricks-self-serve-infrastructure-vending-machine — FEVM handles the full lifecycle (provision → use → expire → cleanup) for 5,000+ field engineers across 3 clouds