Discover every infrastructure asset.
Govern all of it automatically.
Curate connects to every Git repository and cloud account in your organization and builds a complete, real-time inventory of every IaC module, deployed resource, and configuration asset, including everything that was never codified.

One unified inventory.
Every asset, everywhere,
continuously updated.
Curate connects to every source simultaneously, Git repositories for IaC and automation assets, cloud accounts for deployed resources, and policy files for compliance configurations. Everything lands in a single real-time inventory with three properties no fragmented toolset can match.
Auto-Discover
Real-time Inventory
Full Visibility
WHAT CURATE DELIVERS
Three capabilities that close the visibility gap.
Most infrastructure teams are managing blind. They don’t know what automation they have, what’s running outside it, or how it all connects. Curate fixes all three, simultaneously, from day one.
Every piece of infrastructure automation in your organization, found and cataloged
- Scans every connected Git repository and surfaces every IaC file, Terraform modules, Helm charts, Kubernetes manifests, Ansible playbooks, CloudFormation templates, and shell scripts, whether deployed, dormant, or forgotten
- For the first time, your organization has a single source of truth for what automation exists, who owns it, what state it is in, and what it depends on
- Reuse becomes possible. Duplication becomes visible. Governance becomes enforceable.
Console-provisioned resources discovered and codified automatically
- Resources provisioned via the cloud console, one-off scripts, or manual processes are surfaced as Unmanaged assets automatically, no manual scanning required
- Select any Unmanaged resource and Curate generates a production-ready, open-source Terraform module defining its exact configuration, in under a minute
- This is how shadow IT gets brought under governance, and how your cloud accounts stop accumulating invisible debt
Every asset carries full context, what it is, what it depends on, and what depends on it
- Every asset in the inventory carries detailed metadata including configurations, parameters, ownership, deployment status, and full dependency relationships
- Platform teams can see how components interact, identify what depends on what, and make changes with full visibility of downstream impact
- This dependency map is what the AI Copilot uses to generate environment blueprints that respect your infrastructure relationships automatically
The AI Copilot uses this dependency map to generate environment blueprints that respect your infrastructure relationships automatically.
Every resource deployed via the console, codified in under 60 seconds
Most cloud environments carry significant infrastructure provisioned directly via the console, without IaC, without governance, without documentation. These resources accumulate as technical debt. This video shows how Curate discovers them and converts them to production-ready Terraform in one step.

How it works
From connection to governed, reusable infrastructure assets
Six steps. From your first Git connection to a fully governed, AI-ready infrastructure inventory.
Read-only access to every Git repo and cloud account
Connect Curate to your Git repositories and cloud accounts using read-only permissions. No write access required. Supports AWS and Azure cloud accounts, and any Git provider hosting Terraform, Helm, CloudFormation, Kubernetes, Ansible, or shell scripts. GCP cloud account support is in progress.
Every IaC file across every repository, active, dormant, or forgotten
Curate scans every connected Git repository and surfaces a complete catalog of every IaC file it contains, active modules, dormant templates, deprecated playbooks, and duplicates across teams. Every file is indexed with its type, location, owner, last-modified date, and deployment status. This is the automation inventory your organization has never had before.
Every live resource across every cloud account, including what was never codified
Alongside Git, Curate scans every connected cloud account and surfaces a complete list of deployed resources, VMs, databases, storage, network configurations, containers, broken down by service type and region. This includes resources deployed outside any IaC process: console provisioning, one-off scripts, and legacy infrastructure that has never been codified.
Every asset tagged as Codified, Managed, or Unmanaged, so you know exactly where you stand
Every resource in the inventory is tagged with one of three statuses. Codified means the resource has been converted to IaC via Curate. Managed means it was deployed and is governed via Torque. Unmanaged means it was deployed outside Torque — shadow IT, console provisioning, or legacy infrastructure. This view tells platform teams exactly where their governance coverage stands and what to prioritize next.
Unmanaged infrastructure becomes governed Terraform in under a minute
Select any Unmanaged resource, including those deployed manually via the cloud console, and Curate generates a production-ready, open-source Terraform file defining its exact configuration. The file is ready to download and commit to your repository immediately. This is how unmanaged infrastructure gets codified and brought under governance without writing a single line of code.
Natural language becomes governed infrastructure, built from your actual inventory
Once assets are in the inventory, the AI Copilot uses them to generate environment blueprints from natural language prompts. Describe what you need, the Copilot selects the right IaC modules from your Curated inventory, maps dependencies, and produces a deployable blueprint. No YAML expertise required. The blueprint is built from your actual, governed assets, not generic templates.
This is where Curate hands off to Self-Service. The Copilot’s output is only as good as the inventory it works from, and now that inventory is complete.
FAQ
Frequently Asked Questions
Curate discovers three categories of assets simultaneously. First, every IaC file across your connected Git repositories, Terraform modules, OpenTofu files, Ansible playbooks, CloudFormation templates, Helm charts, Kubernetes manifests, and shell scripts, whether actively deployed, dormant, or deprecated. Second, every live resource deployed across your connected cloud accounts, including resources that have no corresponding IaC definition. Third, policy and compliance files such as Rego policies and OPA configurations. All three are surfaced in a single unified inventory with metadata, ownership, and status.
Curate recognizes the following IaC and automation formats: Terraform (.tf, .tfvars), OpenTofu, Ansible playbooks and roles, AWS CloudFormation templates, Helm charts, Kubernetes YAML manifests, and shell scripts. On the cloud side, Curate connects to AWS, Microsoft Azure, and Oracle Cloud, with GCP support in progress. Configuration file types include YAML configs, JSON configs, and environment files. Policy formats include Rego and OPA configurations.
These are the three governance statuses Curate assigns to every discovered asset. Codified means the resource has been converted to a Terraform module via Curate. Managed means it was deployed via Torque, whether codified or not. Unmanaged means it was deployed directly via the cloud account, outside Torque governance. The Unmanaged category is typically where shadow IT, console-provisioned resources, and legacy infrastructure sit. Filtering to Unmanaged gives platform teams a direct view of their governance debt.
Read-only access to your cloud accounts and Git repositories. Curate does not require write permissions and does not modify, deploy, or delete any resources. Your credentials are managed centrally within Torque and are never exposed to individual users. This is intentional, Curate is a discovery and inventory layer, not an execution layer.
The Copilot has access to every asset Curate has discovered and indexed. When you describe an environment in natural language, the Copilot selects IaC modules from your actual, validated inventory, not generic templates from a library. That means the generated blueprint uses your real assets, respects the dependencies Curate has mapped, and is deployable immediately. The quality and accuracy of what the Copilot produces is directly tied to the completeness of what Curate has discovered.
Git repository discovery works with any Git provider and supports all IaC formats used on GCP, including Terraform and Kubernetes YAML. Cloud account discovery for GCP is currently in progress and will be available in an upcoming release. AWS and Azure cloud account connections are fully supported today.
Curate is Day 0.
Here’s what comes next.
The inventory Curate builds is the foundation every other Torque capability runs on. The completeness of what Curate discovers directly determines the coverage of what Operate can govern.
Deploy governed environments on demand, for every team
Govern, optimize, and continuously improve what you’ve deployed
The AI Copilot that powers blueprint generation and environment design
Try it yourself
Explore Curate in a live playground
No installation. No configuration. Connect to a pre-loaded environment and see Curate discover, inventory, and govern infrastructure across a live technology stack.
Pre-loaded blueprints across IaC, containers, and GPU infrastructure, ready to launch in one click.
Real governed environments that provision, enforce policy, and tear down automatically.
No credentials required, explore the full platform experience without connecting your own cloud.
Live cost and drift tracking so you can see the governance layer in action from day one.
Ready to see more? Book a demo with our team.
See how Curate discovers your actual infrastructure estate, Git repositories, cloud accounts, and unmanaged resources, in a live session tailored to your environment.











