Most organizations are stuck at Level 1 or 2 of automation maturity — running scripts manually or maintaining fragile CI/CD pipelines. Here is a framework to assess where you are and plan the path forward.
The Five Levels
Level 1: Ad-Hoc Scripts
Characteristics:
- Bash scripts on individual machines
- No version control
- Knowledge lives in people’s heads
- “Works on my machine” is the deployment strategy
Typical problems: Inconsistent environments, long recovery times, key-person dependency.
Level 2: Scripted Automation
Characteristics:
- Scripts in version control
- Basic CI/CD pipelines
- Some configuration management (Ansible, Puppet, Chef)
- Manual approvals and deployments
Typical problems: Script sprawl, no testing for automation code, partial coverage.
Level 3: Infrastructure as Code
Characteristics:
- All infrastructure defined in code (Terraform, Pulumi, CloudFormation)
- Ansible Automation Platform for configuration management
- Automated testing of infrastructure changes
- GitOps workflows for deployments
- Environment parity (dev = staging = production)
Typical problems: Drift detection, state management complexity, team skill gaps.
Level 4: Self-Service Platform
Characteristics:
- Internal Developer Platform (IDP) abstracts infrastructure
- Developers provision resources through self-service portals
- Policy-as-code enforces guardrails automatically
- Full observability with automated alerting
Typical problems: Platform team bottleneck, balancing flexibility with governance.
Level 5: Self-Healing Infrastructure
Characteristics:
- AI-driven anomaly detection and remediation
- Autonomous scaling and optimization
- Predictive maintenance
- Continuous compliance verification
- Human oversight for edge cases only
Typical problems: Trust calibration, handling novel failures, maintaining human expertise.
Assessment Checklist
Rate your organization (1-5) on each dimension:
| Dimension | Score |
|---|---|
| Version control for all infrastructure code | |
| Automated testing of infrastructure changes | |
| Environment parity (dev/staging/prod) | |
| Self-service resource provisioning | |
| Automated compliance checking | |
| Drift detection and remediation | |
| Incident auto-remediation | |
| Cost optimization automation |
Total: /40 — Divide by 8 for your maturity level.
Building the Roadmap
From Level 1 to 2 (3-6 months)
- Put all scripts in Git
- Set up basic CI/CD (GitHub Actions, GitLab CI)
- Start with Ansible for configuration management
- Document runbooks
From Level 2 to 3 (6-12 months)
- Adopt Terraform for infrastructure provisioning
- Implement GitOps (ArgoCD, Flux)
- Add automated testing (Terratest, Molecule)
- Standardize on container images
From Level 3 to 4 (12-18 months)
- Build or adopt an Internal Developer Platform
- Implement policy-as-code (OPA, Kyverno)
- Create self-service templates and golden paths
- Full observability stack
From Level 4 to 5 (18-24 months)
- Integrate AI/ML for anomaly detection
- Build agentic remediation with guardrails
- Implement predictive scaling
- Continuous chaos engineering
