Skip to main content

​
Built on Infrastructure as Code

Anyshift doesn’t just read your cloud. It reads your code, your state, and your live infrastructure, then correlates the three so you can see where they agree and where they’ve drifted. Terraform code instantiates Terraform state, which manages live infrastructure Declared resources are linked to the state that instantiated them, and state entries are linked to the live resources they manage. That’s how Annie answers questions that span layers: “Which module deployed this pod?”, “What code manages this RDS instance?”, “Which resources are running without any Terraform backing?”
The same model applies to Kubernetes: declared manifests (or Helm charts) → live cluster state, streamed by the Anyshift agent.

​
What You Can Ask Annie

  • “Which Terraform module created this EC2 instance?”
  • “Show me all resources defined in the networking module”
  • “What variables does this state file use?”
  • “What resources were modified outside of Terraform this week?”
  • “Which live resources have no Terraform backing?”
  • “Are my declared replicas matching the pods actually running?”
See the Drift Detection page for more.
  • “What breaks if I destroy this module?”
  • “Which services depend on this security group?”
  • “If I change this variable, what resources are affected?”

​
Explore the IaC Section

Terraform

How Annie ingests Terraform code and state, and what she does with them.

Kubernetes (Live)

How Annie streams live cluster state and ties it to your declared K8s manifests.

Drift Detection

Find the gap between what you declared and what’s actually running.

Knowledge Graph

How all of this connects under the hood.