Automatic extraction from IaC
Point Depgraf at your Terraform, CloudFormation, or Kubernetes sources. It parses resources and references into a typed graph — no agents, no runtime instrumentation, no manual upkeep.
See the cascade before it hits.
Dependency graph & change-impact analysis
Depgraf reads your Terraform, CloudFormation, and Kubernetes manifests and reconstructs the real dependency graph between your services, queues, databases, and external APIs — without you hand-drawing a single diagram.
Before a change ships, Depgraf computes its blast radius: every downstream service that could be affected, the shared resources in the path, and the teams that own them. The graph stays current because it is derived from the same code you already deploy.
Point Depgraf at your Terraform, CloudFormation, or Kubernetes sources. It parses resources and references into a typed graph — no agents, no runtime instrumentation, no manual upkeep.
Open a pull request and Depgraf annotates it with the blast radius: which services depend on what you touched, transitively, and how far the change can propagate.
Because the graph is derived from code, it never drifts from reality the way a wiki diagram does. Merge a change and the topology updates with it.
Every node carries its owning team, so an impact report tells you exactly who needs to be in the room before a risky change lands.
When an alert fires, Sremate gathers context, traces dependencies, and surfaces likely root causes directly in Slack — turning a noisy page into a structured investigation. It remembers past incidents, so it gets sharper every time.
Walog is a fast, native macOS app for exploring, searching, and tailing CloudWatch log groups across every account — no slow console tabs, no context-switching when you are deep in an incident.
It statically analyzes your infrastructure-as-code — Terraform, CloudFormation, and Kubernetes manifests — and resolves resource references into a typed cross-service graph. There is no runtime agent to install.
The set of services, shared resources, and teams that a given change can affect, computed transitively across the dependency graph. Depgraf surfaces it on the change itself so you see impact before you merge.
Yes. Sremate uses the same dependency graph to trace incidents — when an alert fires, it walks the graph Depgraf maintains to find likely upstream causes.
Terraform, AWS CloudFormation, AWS CDK (synthesized output), and Kubernetes manifests. If you describe your infrastructure as code, Depgraf can read it.
Whether it is a product question or a consulting conversation, write to us directly — a real engineer reads every message.
A real engineer reads every message.