Inside ops0: How Discovery, IaC, Resource Graph, and Workflows Work Together

ops0 has five core components: Discovery scans your cloud and turns what it finds into code. IaC generates Terraform from natural language. Resource Graph shows you a live map of everything with drift detection. Configurations handles server setup with AI-generated Ansible playbooks. Workflows automate operations and infrastructure changes. They all talk to each other. Discovery feeds IaC, Resource Graph catches drift, Workflows orchestrate operations using the full dependency context. It covers 4 cloud providers, 27+ compliance frameworks, and 245+ API endpoints.

Most platforms bolt features together and call it integration. ops0 was built as a loop from the start.

Here's how the pieces connect.

Discovery: Understanding What Exists

Discovery is responsible for scanning and understanding your existing cloud.

You connect your AWS, GCP, or Azure accounts. Discovery immediately begins a comprehensive scan of your entire infrastructure. Within minutes, it:

• Discovers every resource across all regions and services

• Maps dependencies and relationships automatically

• Lists everything in a centralized view

• Can generate IaC for what exists

Discovery solves the brownfield problem. Most organizations have years of accumulated infrastructure that was never codified. Manually importing it into Terraform takes months. Discovery does it automatically.

This becomes the foundation for everything else. You can't manage what you don't know about. Discovery ensures you know about everything.

IaC: From Intent to Code

IaC is responsible for creation and modification.

You tell IaC what you want: "I need a scalable web tier with a Postgres backend." IaC generates the Terraform (or your preferred format).

But it's not just generating code blindly. It has context. It knows your existing infrastructure (from Discovery). It knows your cloud provider. It knows your organizational policies.

It doesn't just output a code block. It creates a plan. It shows you the resources. It explains its choices.

And critically: it syncs to Git automatically and can deploy directly. The workflow isn't "copy-paste into your repo" - it's "review, approve, deploy."

IaC is what replaces the "write HCL" part of the work.

Resource Graph: Seeing the Truth

Resource Graph is responsible for visualization and drift detection.

It builds a real-time graph based on your state files and your actual cloud resources. Every resource, every connection, every dependency - visible and queryable.

The key capability: it shows the disparity between IaC and real state. Your Terraform says one thing; your cloud says another. Resource Graph shows you exactly where they diverge.

Upstream and downstream dependencies are mapped. When you look at a resource, you see everything it affects and everything that affects it.

And here's what makes it actionable: you can fix drift in one click. Choose to update your IaC to match reality, or push reality to match your IaC. The gap closes immediately.

Resource Graph is what makes infrastructure visible and manageable.

Configurations: Bootstrap and Maintain Servers

Configurations is responsible for server-level setup and maintenance.

It provides templates for common configurations - NGINX, Docker, MySQL, Node.js applications, and many more. Each template is a tested playbook that you can deploy with confidence.

But you're not limited to templates. You can ask the AI to create custom configurations. Describe what you need; it generates the playbook. Once approved, it deploys.

This covers the gap between infrastructure provisioning (handled by IaC) and application deployment. Your servers need to be configured correctly. Configurations handles that.

Deployments: History and Active State

Deployments tracks what's been deployed and what's currently active.

Every deployment is logged - what was deployed, when, by whom, what the result was. This is your audit trail.

Active deployments are visible in one place. You see what's running across your infrastructure, not scattered across different tools and dashboards.

Workflows: Automating Operations

Workflows are responsible for automating infrastructure changes and operational tasks.

Workflows are built on a DAG-based engine designed for reliability and visibility. They support 7 different step types for different kinds of operations, 3 trigger types (manual, scheduled, event-based), and parallel execution for efficiency. Events stream in real-time via Server-Sent Events so you see what's happening as it happens.

When something needs to change, Workflows execute the necessary steps automatically. They handle infrastructure provisioning, configuration management, incident response, and custom operational procedures. You define the logic once, and the system executes it reliably every time.

Workflows integrate with Resource Graph to understand your infrastructure context, so changes are made with full awareness of dependencies and blast radius.

Workflows are what makes infrastructure operations reliable and repeatable.

Infrastructure: The Unified View

Infrastructure provides a centralized view of all your servers, server groups, and Kubernetes clusters.

It's the single pane of glass for seeing everything in one place. Not scattered across cloud consoles. Not hidden in different tools. Everything, visible.

The Closed Loop

The real power comes when these capabilities connect.

Discovery + IaC = Brownfield to Code

Discovery scans what exists. IaC generates code for it. Legacy infrastructure becomes codified infrastructure.

IaC + Resource Graph = Drift Prevention

IaC knows what should exist. Resource Graph knows what does exist. When they diverge, you see it immediately and fix it in one click.

Resource Graph + Workflows = Context-Aware Operations

Workflows execute operations with knowledge of your full infrastructure context. They know what's connected to what, what changed recently, and the full blast radius of any change.

Workflows + IaC = Automated Infrastructure Changes

Workflows can trigger infrastructure changes through IaC. When a change is needed, the workflow requests IaC to generate the code, applies it, and monitors the result. The system improves itself automatically.

Configurations + Deployments = Server Lifecycle

Configurations bootstraps servers correctly. Deployments tracks what's active. The full server lifecycle is managed.

Why Integration Matters

Most tools address one part of this lifecycle.

Provisioning tools don't monitor. Monitoring tools don't provision. Visualization tools don't remediate. Each tool requires you to bridge the gap manually.

ops0 unifies the context. Discovery, IaC, Resource Graph, Configurations, Deployments, Workflows, and Infrastructure share information. When one capability acts, the others know about it.

This is what makes it an "AI Infrastructure Engineer" rather than just "AI Tools." An engineer holds the whole system in their head - design, reality, and health. ops0 does the same.

The Experience

Using ops0 feels different.

You give intent: "Launch this new service." IaC generates the code. You approve. Resource Graph shows it's live. Workflows orchestrate the deployment and monitor the result.

You're still in charge. You make the decisions. But you're not doing all the manual work anymore.

This is the future of infrastructure management. Not fragmented tools that each solve one problem. An integrated system that manages the full lifecycle.

And it's all built on the integration of Discovery, IaC, Resource Graph, Configurations, Deployments, Workflows, and Infrastructure working together.