Skip to content

What is Aletheia

Aletheia is an infrastructure control plane for teams running on AWS. It reads your live AWS resources and your infrastructure-as-code repositories, then joins them into a single picture: what exists, which code declares it, who owns it, and how it has changed.

Most teams already have the raw material. It is just scattered.

  • The AWS console knows what exists, but not who owns it or which repository declares it.
  • Terraform state knows what is managed, but not what drifted or what was never in code.
  • Git knows what changed in code, but not whether that change reached production.
  • Your team knows who owns what, and that knowledge lives in people’s heads.

Aletheia joins those sources so a question like “who owns this database, which module declares it, and what changed on it last week” has one answer instead of four investigations.

Source What Aletheia reads How it connects
AWS accounts Live resource inventory and configuration A read-only IAM role you create
Terraform state Which resources are managed, and by what Scoped read access to the state objects you designate
Source control Repositories, infrastructure-as-code projects, pull requests A GitHub App or a GitLab connection
CI pipelines Terraform plans and applies An ingest token you generate
Your organization Teams, environments, applications, ownership Defined in the product, or inferred from tags

Aletheia is read-only against your cloud. This is a deliberate boundary, not a current limitation:

  • It never calls a mutating AWS API. The role you grant it cannot create, modify, or delete resources.
  • It never runs terraform apply, and it never writes to your Terraform state.
  • It holds no long-lived cloud credentials. Access is by role assumption with an external ID.

The CI integration is observational in the same way: your pipeline sends Aletheia the result of a plan or apply that it ran itself. Aletheia does not run anything.