Feature

Repository Intelligence

Discover services, dependencies, and topology from your repositories to generate accurate IaC and governed plans.

Repository Intelligence is OrchesTerra’s discovery layer: it turns a codebase into a structured view of what must be deployed and how components connect.

Instead of guessing architecture from file names, OrchesTerra builds a service map that reflects dependencies and runtime expectations—so generation starts from reality, not assumptions.

Inputs

  • A connected git repository (the platform team selects what “represents the environment”.)
  • Configuration signals (for example, how services are built and deployed).
  • Optional metadata about your platform conventions.

Outputs

  • service discovery summary (what services exist and how they relate),
  • dependency graph and topology hints,
  • a basis for Terraform/OpenTofu module generation,
  • and cost estimation context.

Where governance fits

Repository Intelligence creates the “what” and “how” of your intended infrastructure.

Governance fits when reviewers need to approve changes generated from that discovery, and when drift remediation requires decisions with risk context.

Related: approval workflows and policy packs.

FAQ

Is discovery language-specific?

No—discovery is based on infrastructure/runtime signals and repository structure, not limited to a single programming language.

Platform evaluation

See OrchesTerra on your infrastructure

Request access to generate architecture from a repository, review the plan, and run governed reconciliation across AWS, Azure, GCP, and OCI.