About TellIaC: Plain English Infrastructure for Modern Engineering

TellIaC was conceived to eliminate unnecessary syntactical friction in cloud engineering. We believe cloud topologies should be understandable by every engineer, security auditor, and product team member without requiring proprietary domain-specific languages.

The Vision: Human Infrastructure as Code

Over the past decade, Infrastructure as Code (IaC) has fundamentally transformed how cloud workloads are provisioned. However, as cloud environments expand across multiple hyperscalers (AWS, Microsoft Azure, Google Cloud Platform) and container orchestrators (Kubernetes), the complexity of configuration languages has surged.

Engineers spend countless hours debugging cryptic indentation errors in YAML, wrestling with vendor-specific DSL quirks in Terraform HCL, or diagnosing variable resolution conflicts.

TellIaC provides a refreshing alternative: a deterministic, human-readable grammar that reads like natural English sentences while retaining the mathematical rigor, dependency graphing, state tracking, and security controls expected in enterprise DevOps pipelines.

💡
Core Philosophy Infrastructure specifications are communication documents between humans and machines. Clear natural sentences reduce misconfigurations, improve code reviews, and democratize cloud operations across multidisciplinary engineering teams.

How TellIaC Works: Architectural Overview

TellIaC is not an opaque AI wrapper or black box. At its core sits a locally executed compiler and runtime pipeline designed for predictable, offline operation:

  1. Deterministic Grammar Lexer & Parser: Reads .hiac files and extracts resource declarations, provider contexts, module invocations, and input variables using formal sentence grammar specifications.
  2. Directed Acyclic Graph (DAG) Engine: Builds an internal dependency graph connecting all network, compute, database, and security resources. Detects cyclical dependencies and optimizes parallel execution paths.
  3. Multi-Cloud Resource Providers: Maps abstract definitions to cloud API calls across AWS (via Boto3 / SDKs), Azure (via Azure Resource Manager APIs), GCP (via Google Cloud Client Libraries), and Kubernetes (via K8s Core APIs).
  4. Terraform HCL Exporter (telliac export): Synthesizes standard HashiCorp Configuration Language (main.tf, variables.tf, outputs.tf) for complete zero-lock-in migration into existing enterprise Terraform ecosystems.
  5. State Management & Distributed Locking: Maintains cryptographic state records (local or remote in AWS S3, Azure Blob, or Google Cloud Storage) with optimistic locking to prevent concurrent state corruption.
  6. Cost Estimation & Security Auditing: Proactively computes monthly cloud spend breakdowns and scans for high-risk configurations (e.g. open 0.0.0.0/0 CIDR blocks, plaintext tokens, or unencrypted storage).
Advertisement
TellIaC is supported by compliant advertising to keep open documentation and tools freely accessible.

Open Source Integrity & Ecosystem Interoperability

TellIaC is developed under the permissive MIT Open Source License. We believe that critical infrastructure automation tools must remain transparent, auditable, and free from artificial proprietary constraints.

Key integrations and dependencies include:

  • Python 3.10+ Core Runtime: Built on industry-standard parsing, typing, and networking libraries.
  • HashiCorp Terraform Interoperability: Generated HCL follows standard Terraform provider conventions for AWS, Azure, Google, and Kubernetes.
  • Cloud Provider SDKs: Direct interoperability with official provider credentials (IAM roles, service principals, Google Application Default Credentials, and kubeconfig files).

Platform Sustainability & Ethical Advertising

TellIaC's documentation, web sandbox, releases hub, and educational guides are funded through ethical, non-intrusive Google AdSense display advertising. We adhere to strict advertising standards:

  • No advertisements are ever placed inside terminal interactive playgrounds, code editors, command-line interfaces, or download actions.
  • We never sell telemetry, cloud credentials, or code snippets to third-party data brokers.
  • Advertisements are clearly demarcated from editorial technical content.

Project Roadmap & Community Contributions

TellIaC is actively evolving. Our roadmap includes expanded support for edge cloud providers, native OpenTofu provider mappings, automated policy-as-code linting with OPA/Rego, and native ARM64 macOS binary builds.

We invite developers, DevOps practitioners, and cloud architects to explore our GitHub repository, report issues, and contribute improvements:

GitHub Repository → | Explore Technical Guides → | Contact Engineering Support →