Mr.PlanB Logo
    Infrastructure Automation Ledger 2026
    Ledger
    Infrastructure Automation Ledger 2026

    Digger: Infrastructure Automation Ledger 2026 Scorecard

    Digger, now OpenTaco, runs Terraform plans in your own CI and is adding state, drift and remote runs as an open-core startup without published pricing.

    Edition October 16, 20267 min read

    Where Digger put its effort, 2024 to 2026

    Each square is one capability area in one year. The brighter it is, the more the area gained in the Infrastructure Automation Ledger that year; 1, 2 and 3 mark that year's biggest pushes.

    ’24’25’26
    Provisioning breadth2
    Configuration management depth
    State, planning and safety1
    Language and authoring
    Orchestration and self-service3
    Scale and control plane
    Security and compliance
    Bare metal and day-2 operations
    Ecosystem and integrations
    AI assistance
    no change+0.5+1+1.5 or moreScores out of 5 per area.

    Biggest pushes overall: State, planning and safety (+1), Provisioning breadth (+0.5), Orchestration and self-service (+0.5). Already strong in 2023: State, planning and safety, Provisioning breadth, Orchestration and self-service.

    Top focus each year: 2026 State, planning and safety. 2 of 3 years show no gain in any area.

    Part of the Infrastructure Automation Ledger (edition 2026-10-16). How the scores work: methodology.

    Snapshot

    • Type: product (open core; the project was renamed OpenTaco on 2025-11-07, the company is still Digger)
    • Owner: Digger Inc. (private startup; country, funding and investors not found; no acquisition found)
    • Engine: runs Terraform, OpenTofu and Terragrunt inside your existing CI system
    • Licence: MIT core; the ee/ directory (enterprise backend, drift service) under the Digger Enterprise License, production use per user seat; no price list found
    • Latest release: v0.6.154 (2026-10-07); Backend EE 0.1.7.32 and Drift 0.1.1.6 (2026-05-04)
    • Support lifecycle: none published
    • Next milestone: none published; remote runs are in Beta
    • Targets: Terraform and OpenTofu binaries supplied by your CI runner (no version ceiling documented in the sources read, 2026-10-15), Terragrunt; self-hosted orchestrator; GitHub confirmed, other VCS described in the docs
    • Tier: IaC management platform
    • Archetype: Slow follower
    • Evidence grade: B. Licence files, README, rename notice and the GitHub release list were read from primary sources (2026-10-15). The docs overview is short and release years are inferred from the page footer and Atom feed. Pricing and funding were not found. Scores start in 2023, the last year named in the ee/LICENSE copyright header; earlier release history was not read.

    Scorecard

    DimensionScoreDirection
    Capability today34.1 / 100higher is better
    Momentum since 2023+6.7 pointshigher is better
    Credibility14.5 / 25higher is better
    Commercial risk11.0 / 25lower is better
    Technical lock-in4.5 / 25lower is better
    Integrator fit6.5 / 20higher is better
    AI leverage1.0 / 20higher is better
    Ledger Index42.8 / 100balanced weights; see the methodology

    Capability by domain, 2015 to today

    Scores 0 to 5 against fixed anchors; total is weighted to 100.

    Domain (weight)201520192022Today
    Provisioning breadth (15)n/an/an/a2.5
    Configuration management depth (12)n/an/an/a0
    State, planning and safety (12)n/an/an/a3.5
    Language and authoring (10)n/an/an/a1
    Orchestration and self-service (10)n/an/an/a2.5
    Scale and control plane (8)n/an/an/a2
    Security and compliance (10)n/an/an/a2
    Bare metal and day-2 operations (8)n/an/an/a0
    Ecosystem and integrations (8)n/an/an/a2.5
    AI assistance (7)n/an/an/a0
    Total / 100n/an/an/a34.1

    Year by year: 2023: 27.4 · 2024: 27.4 · 2025: 27.4 · 2026: 34.1

    What moved the score

    YearDomainChangePointsTrigger
    2026Ecosystem and integrations2 → 2.5+0.82026: drift notices to Slack and GitHub Issues; Checkov in the run
    2026Orchestration and self-service2 → 2.5+1.02026-03 and 2026-04: Taco UI; sandbox sidecar for remote runs (Beta, half step)
    2026Provisioning breadth2 → 2.5+1.5v0.6.142 (2026-01): Terragrunt documented beside Terraform and OpenTofu
    2026Security and compliance1.5 → 2+1.0v0.6.141 (2026-01): clearer permission errors; token service (2026-02); OPA-based RBAC; SSO not confirmed
    2026State, planning and safety2.5 → 3.5+2.42026-02: OpenTaco state management and token service tags; 2026-05: enterprise drift service (Drift 0.1.1.6)

    Direction, 2023 to 2026

    Each release item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

    DateItemThemeDriver
    2025-11Project renamed OpenTaco; scope widened to state, remote runs and driftPackagingV
    2025-11OpenTaco state management with an HCP Terraform compatible interface (vendor claim)State and planningM
    2026-01v0.6.141: clearer permission errors; pagination for team membersSecurityC
    2026-01v0.6.142: Terragrunt in the docs; apply check passes on zero-change plansProvisioning breadthC
    2026-01Digger Backend EE 0.1.7.22 to 0.1.7.25: enterprise backend imagesPackagingP
    2026-02statesman and token-service tags: state and token servicesState and planningV
    2026-03Sandbox sidecar manages E2B sandboxes for remote Terraform and OpenTofu runs (Beta)OrchestrationM
    2026-04Taco UI 0.1.32.13: web front endOrchestrationV
    2026-05Drift 0.1.1.6: enterprise drift detection serviceState and planningC
    2026-05v0.6.145: drift exclude patterns; community edition backend default imagesState and planningC
    2026-10v0.6.146 to v0.6.154: nine numbered releases from June to October (notes not read)PackagingC
    • Centre of gravity: State and planning (4), Packaging (3), Orchestration (2)
    • Blind spots (no items): Configuration management, Language, Scale, Bare metal, Ecosystem, AI, Licensing
    • Driver mix: Vision 27%, Customer need 45%, Market window 18%, Upstream 0%, Portfolio 9%
    • Idea-to-need index: 0.30 (0 = demand-pulled, 1 = thesis-pushed)

    Credibility: 14.5 / 25

    CriterionScoreBasis
    Cadence4Numbered releases about every two weeks in 2026 (v0.6.141 on 2026-01-21 to v0.6.154 on 2026-10-07); October 2025 to January 2026 not read
    Roadmap transparency2.5Open repository with 423 open issues; no roadmap read; the rename was announced in the README
    Say-do2.5Rename and widened scope shipped in part (repository and docs still say digger); remote runs still Beta
    Velocity3.5State service, token service, UI, drift service and sandbox runner within 2026
    Lifecycle stability2Project renamed 2025-11-07 with repository and docs still mixed; several component version lines

    Commercial risk: 11.0 / 25 (lower is better)

    CriterionScoreBasis
    Price and licence volatility2MIT core with a proprietary ee/ directory; no price list published; the date the ee/ licence was introduced is not found
    Purchase constraints2Production use of ee/ needs a seat subscription; the core is free
    Channel and access1.5Open download of the core; ee/ source is readable; sales by contact
    Owner stability3.5Small startup; country, funding and investors not found; project renamed in 2025
    Cost of staying supported2No support lifecycle published

    Technical lock-in: 4.5 / 25 (lower is better)

    CriterionScoreBasis
    Formats0.5Plain code and digger.yml
    Export path1Runs in your CI; state import and export through the backend interface (vendor claim)
    Stack coupling1.5Low for pull request automation; higher once OpenTaco state and remote runs are adopted
    Hardware / cloud coupling0.5Self-hostable; telemetry can be disabled
    Skills and tooling coupling1Standard Terraform skills; OPA for RBAC

    Integrator fit: 6.5 / 20

    CriterionScoreBasis
    Partner programme openness1.5No programme found
    Multi-tenancy and self-service1.5Not documented on the pages read
    API and infrastructure-as-code2.5CLI and orchestrator API; no Terraform provider found
    Skills and certification1None found

    AI leverage: 1.0 / 20

    How the product uses AI, scored per year like capability. Only GA counts.

    Criterion20192022TodayLatest step
    AI code and plan generationn/an/a02023: None
    AI platform stackn/an/a02023: None
    AI-assisted operationsn/an/a02023: None
    Agent opennessn/an/a12023: CLI and orchestrator API; no MCP server found

    Year by year: 2023: 1 · 2024: 1 · 2025: 1 · 2026: 1

    AI say-do, 2023 to 2026: 0 AI items announced; 0 GA, 0 still preview, 0 pending, 0 dropped. No AI item was found in the README or the docs overview; other docs sections were not fully browsed.

    Digger has no AI feature and no MCP server in the sources read. The sandbox runner is infrastructure for remote execution, with no AI role stated.

    Reading

    Digger started as the Atlantis alternative that runs inside your CI, and since the OpenTaco rename it is becoming a small platform with its own state service, drift detection and remote runs. The capability score is close to Atlantis today and will move if the Beta pieces land; the lock-in score is low because the orchestrator sits beside your CI rather than replacing it. The archetype reflects a thin public record (no roadmap, no pricing, a rename still half applied) rather than the release pace, which is fortnightly. Before depending on it, ask for the price list and the legal entity, neither of which is public, and note that owner stability carries the highest risk score of the six.

    Open questions and items to re-score

    • Legal entity, country, funding and Y Combinator batch: not found (the YC profile URL returned 404).
    • Pricing: both pricing URLs returned 404; the licence says per seat.
    • When the ee/ directory became proprietary.
    • Releases between 2025-10-15 and 2026-01-20 were not read.
    • Whether OpenTaco has an MCP server or AI feature in docs sections not browsed.
    • Supported VCS list beyond GitHub; SSO; multi-tenancy.

    Related reading

    More from Infrastructure Automation Ledger 2026