The News
Spacelift announced Run Observability at OpenTofu Day North America in Salt Lake City on November 9, 2026, marking the first product to translate OpenTelemetry traces from OpenTofu into structured, actionable findings for platform teams. The feature breaks down infrastructure deployment runs by phase, resource, and provider, surfacing the root cause of slow or failed runs without requiring debug log re-runs or manual log triage. Run Observability is available immediately for Spacelift customers on OpenTofu native stacks and requires no additional backend configuration.
Analyst Take
The infrastructure observability gap was always real. AI made it urgent.
Platform teams have operated with a fundamental visibility deficit for years: a failed or slow OpenTofu run produced a wall of log output and a total runtime number, neither of which told engineers whether the problem was their code, a flaky provider, or a third-party API going dark. That was a painful but manageable gap when deployment runs were largely human-initiated and relatively infrequent. AI coding tools have changed the calculus entirely. Spacelift’s own Infrastructure Automation Report 2026 found that 76% of respondents were willing to apply AI-generated Terraform to production with little to no scrutiny, and that 93% of organizations had experienced at least one AI-caused infrastructure incident. More runs, less human review, and faster feedback loops mean the cost of blind spots compounds quickly.
Run Observability is a direct product response to that dynamic. By ingesting the OpenTelemetry traces that OpenTofu has been capable of emitting since version 1.10 and running them through a rule-based analysis engine against the stack’s own run history, Spacelift converts raw telemetry into findings. A platform engineer no longer needs to re-run a failed job with debug flags; they see in seconds that the initialization phase ran three times longer than baseline and that a specific provider download was responsible. That’s a meaningful reduction in diagnostic toil, and it directly targets what ECI Research’s Google GovTech Survey identified as a significant productivity drag: according to ECI Research, 21.2% of respondents reported a “High bottleneck” experience, with developers routinely waiting weeks for cloud infrastructure or databases, a problem that worsens when the infrastructure pipelines themselves become opaque.
Why OpenTofu specificity is a strategic bet, not a limitation
The FAQ makes a point worth examining: Run Observability works exclusively on OpenTofu stacks, not on Terraform. That’s not an oversight; it’s a signal about where Spacelift is placing its bets. Spacelift is a founding contributor to the OpenTofu project and the OpenTelemetry tracing capability that makes Run Observability possible was built into OpenTofu with Spacelift’s direct involvement. The company is effectively creating a premium observability experience that is only achievable on the open-source fork it helped instrument. For ITDMs evaluating IaC orchestration platforms, this creates a concrete differentiation point: if your organization is migrating from Terraform to OpenTofu (a trend accelerating since HashiCorp’s BSL license change), Spacelift offers a level of run-level observability that has no direct equivalent on the Terraform side of the ecosystem today. That’s a durable competitive advantage, not easily replicated by a vendor that didn’t participate in building the underlying tracing infrastructure.
For developers, the architecture here matters. OpenTofu emits OTLP traces that any compatible backend like Jaeger or Grafana Tempo can ingest. Spacelift’s value-add is the analysis layer on top: a rule engine that checks each trace against historical baselines and generates natural-language findings. This is a sensible separation of concerns. The raw observability signal is open and portable; the intelligence layer is proprietary and lives in Spacelift. Developers who care about avoiding lock-in can still access raw traces through open backends; organizations that want the diagnostic intelligence pay for Spacelift. That framing could reduce adoption friction considerably.
CI/CD fragmentation makes this harder to ignore
One reason infrastructure observability has lagged application observability is that CI/CD standardization in most organizations remains patchy at best. According to ECI Research’s Google GovTech Survey, 40.8% of respondents reported “Fragmented” CI/CD pipelines, where each project team maintains its own. Fragmented pipelines mean fragmented signal: no consistent baseline against which to measure run performance, no centralized place to catch regressions. Run Observability works best when Spacelift is the single orchestration layer across stacks, which gives the rule engine the historical run data it needs to flag anomalies. For organizations operating fragmented IaC pipelines, adopting Spacelift as a consolidation point becomes the prerequisite that makes Run Observability valuable, a natural land-and-expand motion for Spacelift’s commercial strategy.
Looking Ahead
The immediate competitive pressure lands on Terraform Cloud and HashiCorp’s successor product under IBM’s ownership. Neither currently offers run-level trace analysis tied to provider and phase breakdowns, and the instrumentation required to build it on Terraform’s codebase doesn’t exist today the way it does in OpenTofu. Spacelift has a window of at least 12 to 18 months to build Run Observability into a genuinely sticky capability before a credible response is possible. The more important long-term play is whether Spacelift can extend this observability model to the broader Day 2 operations surface it’s been building out, including the Flows product announced in October 2026. An intelligence layer that understands run behavior across provisioning, drift detection, and remediation workflows would be meaningfully harder to replicate than a single feature.
For platform engineering leaders, the trajectory here points toward infrastructure pipelines being treated with the same observability rigor as application delivery pipelines. Teams that instrument and baseline their IaC runs today will be better positioned to govern AI-generated infrastructure changes as agentic tooling pushes run volumes higher. Spacelift is making a credible argument that it should be the platform where that governance lives. Organizations still managing IaC runs through fragmented tooling should treat this announcement as a prompt to evaluate whether their current setup gives them the visibility they’ll need as AI accelerates the pace of infrastructure change.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
