Research / Coverage area 04
Coverage area 04Development & Data Infrastructure
Coverage of the platform layer: compute, data platforms, deployment, observability, and the managed services that stand in for an SRE organization. The leverage question here is staffing, not spend: how few people can responsibly carry a production system, and what they gave up to get there.
What does it now cost — in people, not dollars — to run production-grade infrastructure at small scale?
Sample Data
Three figures from this area's dataset, in the form they publish in.
Illustrative sample — these figures show the structure of the dataset and the form a published finding takes. They are not published findings. Sourced figures publish with the report, each carrying an openable source.
This area is the clearest case of leverage being purchased rather than earned — and that is not automatically a bad trade. It is why the Leverage Index carries a margin-conversion input at 15%: spend that buys away headcount still has to reach the P&L to count.
What We Track
- Dedicated infrastructure FTEs against production system scope
- Managed-service mix and what each one replaced
- Infrastructure cost per engineer and per revenue dollar
- On-call structure at teams under fifteen engineers
- Whether incident review is a practice or a formality
In scope
- Managed compute, database, and data platform services
- Deployment, IaC, and platform-engineering tooling
- Observability and incident response at small team size
- Infrastructure cost per engineer and per unit of revenue
Not covered
- Hyperscaler enterprise contract negotiation
- Model training infrastructure — covered under a separate agenda
Adoption Depth Rubric — 0 to 5
The Leverage Index scores automation and agent adoption depth at 25% of the composite, applied as a 0–5 rubric to each coverage area and then averaged. This is that rubric for this area. A capability scores above 2 only if it is in production, used at least weekly, and displacing or avoiding a named role — not piloted, not licensed-and-idle. See the full inputs and weighting →
Manual deploys, no IaC, no monitoring worth the name.
Managed hosting and database. Deploys are scripted but attended.
Automated pipeline to production. Monitoring exists; alerting is noisy.
Actionable alerting, defined on-call, and incidents that get reviewed.
Engineers ship without a platform gatekeeper. No dedicated SRE was hired.
Unit economics and reliability targets are measured, owned, and acted on.
C.A.S.E. in This Area
The same four-stage method runs in all six coverage areas. Here is what each stage actually does in this one.
Stack detection from public signals, provider status and pricing pages, infrastructure job postings, and disclosed architecture write-ups. Every detection carries its evidence URL.
Cost-saving claims are reconciled against disclosed headcount and margin. Where a company shows infrastructure leverage but no margin improvement, that gap is the finding — it is not smoothed over.
Infrastructure staffing benchmarks by production scope, and the buy-vs-hire model that shows where purchased leverage stops paying.
Inquiry on platform consolidation, managed-versus-hire decisions, and the reliability floor a small team can actually hold.
Sample Insights
Findings in the form we publish them: each one carries a confidence level, and the ones the evidence does not yet support are labeled open rather than quietly dropped.
Companies under fifty people running production systems with under one infrastructure FTE are the norm now, not the exception. The staffing question has genuinely changed.
Purchased leverage stops paying at the point where managed-service spend crosses the loaded cost of the hire it avoided. Most companies do not track the crossing.
Whether thin infrastructure staffing carries a measurable reliability penalty, or simply a concentration-of-knowledge risk that has not yet been priced.
Illustrative sample — these figures show the structure of the dataset and the form a published finding takes. They are not published findings. Sourced figures publish with the report, each carrying an openable source. Research integrity policy →
What Publishes Next
Want this area applied to your decision?
Book an inquiry with the analyst covering it, or commission research on a question this area does not answer yet.