Infrastructure Forensics
Evidence-grade intelligence. Not just "what they use," but how they operate.
The Constraint Radar
Reasoning: GDPR/EU Regions Detected
Reasoning: Deep AWS Native Service Usage
Reasoning: Manual Pipelines observed
Reasoning: HIPAA/Encryption Flags
Reasoning: Overprovisioned Resources
Operating Model Archetype
Kubernetes Platform Builder
This organization is past the 'experimental' phase. They are actively centralizing infrastructure. They employ a Platform Engineering team and are sensitive to 'Day 2' operational toil.
Coverage & Blind Spots
*We cannot see private VPC traffic. Deductions on internal routing are inferred from Security Groups.
Main Hypothesis
Production-Grade Kubernetes Platform on AWS
Competing Hypothesis
Ephemeral / Sandbox Environment
Change Detection: Critical Events
Replicas spiked 2x -> 50x. WAF rules added.
Encryption-at-rest modules added to Terraform.
Competitive Incumbency
Validation Workflow
Look for `cluster-autoscaler` or `aws-load-balancer-controller` in new signals.
Check for `deploy-prod.yaml` or environment tags in subsequent commits.
Draft message to VP Eng referencing "Scaling pains post-launch".