Roadmap: ThothCTL as a Framework-Defined Infrastructure (FdI) Platform¶

Vision¶

Transform ThothCTL from an IaC management CLI into an IaC-native Framework-Defined Infrastructure platform where business intent and application conventions automatically produce production-ready infrastructure code — without requiring developers to write Terraform manually.

graph TB
    INTENT["💡 Developer Intent<br/><i>'I need a microservices platform for my Python API'</i>"]

    subgraph FdI["⚙️ ThothCTL FdI Engine"]
        SPACE["🌐 Space Conventions"]
        COMP["🧩 Composition Engine"]
        AI["🤖 AI Inference<br/><i>from app code</i>"]
        SPACE --> GEN
        COMP --> GEN
        AI --> GEN
        GEN["📦 Generated Output<br/>Terraform/Tofu/CDK + CI/CD + Security + Cost"]
    end

    INTENT --> SPACE
    INTENT --> COMP
    INTENT --> AI

Current State (v0.15.0) — IaC Maturity Level 4+¶

Phase 1: Stack Composition Engine (v0.16 – v0.17)¶

Goal: Declaratively define infrastructure stacks from reusable building blocks.

Deliverables¶

Example¶

# stack.thoth.yaml
name: payments-platform
cloud: aws
region: us-east-1
components:
  - type: networking/vpc
    cidr: "10.0.0.0/16"
    availability_zones: 3
  - type: compute/eks
    version: "1.30"
    node_groups:
      - name: workers
        instance_type: m6i.large
        min_size: 3
        max_size: 10
  - type: database/rds-postgresql
    version: "16"
    instance_class: db.r6g.large
    multi_az: true
  - type: observability/cloudwatch
    dashboards: true
    alarms: true

thothctl generate stack --manifest stack.thoth.yaml --space production
# → outputs a complete Terraform/Terragrunt project

Phase 2: App-to-Infra Inference (v0.18 – v0.19)¶

Goal: Scan application source code and automatically infer the required infrastructure.

Deliverables¶

Inference Examples¶

Workflow¶

# Scan app and generate stack manifest
thothctl generate stack --from-app ./my-api --space production

# Output: inferred stack.thoth.yaml
# Developer reviews and approves

# Generate the IaC
thothctl generate stack --manifest stack.thoth.yaml

Phase 3: Convention-Driven Automation (v0.20 – v0.21)¶

Goal: The Space becomes a full "framework" that encodes organizational standards — infra generation is fully governed by conventions.

Deliverables¶

Space Policy Example¶

# ~/.thothcf/spaces/production/policies.toml
[mandatory_components]
networking = ["waf", "vpc_flow_logs"]
compute = ["auto_scaling", "container_insights"]
data = ["encryption_at_rest", "automated_backups", "multi_az"]
security = ["cloudtrail", "guardduty", "security_hub"]

[naming]
pattern = "{space}-{project}-{component}-{env}"

[cost]
max_monthly_estimate = 50000  # USD
require_approval_above = 10000

[compliance]
frameworks = ["soc2", "hipaa"]

Phase 4: Continuous Reconciliation (v0.22+)¶

Goal: Move from one-time generation to continuous alignment between intent and infrastructure state.

Deliverables¶

Architecture¶

graph TB
    SM["📋 Stack Manifest"]
    LC["☁️ Live Cloud Resources"]
    PM["📊 Production Metrics"]

    SM --> RE
    LC --> RE
    PM --> RE

    subgraph RE["🔄 Reconciliation Engine"]
        ID["Intent Drift"]
        SD["State Drift"]
        CF["Cost/Perf Feedback"]
    end

    RE --> PR["📝 Auto-generated PRs<br/><i>IaC updates aligned to intent</i>"]

FdI Maturity Progression¶

Differentiation¶

Unlike existing FdI tools (Vercel, SST, Nitro) which target frontend/serverless apps:

• ThothCTL FdI targets enterprise infrastructure compositions (VPCs, EKS, RDS, multi-account)
• Works with existing IaC tools (Terraform, Tofu, Terragrunt) — not a replacement
• Security-first — compliance, scanning, and AI review baked into the generation pipeline
• Multi-cloud — not locked to a single provider's serverless platform
• Organization-aware — Spaces encode team conventions, not just technical defaults

Success Metrics¶

Timeline Estimate¶