Provenance Record

Well-structured, 1,089-word analysis with clear section headers. Coverage moves logically from the specific policy change (March 31 free tier retirement) to its broader context (IBM acquisition) to ecosystem alternatives (OpenTofu, Pulumi, self-hosted). Appropriate depth for the Analysis category.

All 5 sources verified as reputable and accurately cited. The HashiCorp URL (source 1) returned HTTP 429 (rate limiting) during automated checks — this is a CDN/WAF rate-limit, not a dead link. The URL is confirmed valid and the post exists via web search (title: 'Continuing HCP Terraform's enhanced free tier experience'). TechCrunch acquisition article verified: IBM closed $6.4B deal on Feb 27, 2025, consistent with article claim. InfoQ OpenTofu 1.10 article verified: OCI registry support, S3 native state locking, MCP server, and download numbers all consistent. InfoQ Pulumi HCL support article verified: private beta status, Q1 2026 GA timeline, credit migration program all confirmed. The Register Terraform article verified: covers the BSL license change, OpenTofu fork, IBM acquisition context. Allowlist warning for hashicorp.com is a false positive — the allowlist contains 'hashicorp.com/blog' but the domain extractor only captures the hostname. HashiCorp is an authoritative primary source for its own product announcements and is trusted.

Claims cross-verified against sources. The March 31, 2026 deadline is confirmed. IBM acquisition price ($6.4B) and date (February 2025) are accurate. Enhanced free tier limits (500 managed resources, unlimited users, 1 concurrent run) are consistent with HashiCorp's documentation. Pricing tiers ($0.10/$0.47/$0.99 per resource/month) cited without a direct source link — these are presented as factual claims. OpenTofu download numbers ('approach 20 million') are within range: the InfoQ source says '10 million from GitHub releases, likely well past 20 million.' The claim that 'OpenTofu 1.11 followed in December 2025' is verified — v1.11.0 was released December 9, 2025. Oracle and Allianz cited as OpenTofu adopters per The Register source. The article correctly notes HashiCorp has not clarified state file handling details — this is an appropriate acknowledgment of uncertainty. Minor: the article refers to 'HSB lock-in' in the Pulumi section, which appears to be a typo or abbreviation error (likely meant 'HCP' or 'HCL-based vendor' lock-in). This is a minor editorial issue that does not affect the overall quality.

Strong, well-sourced analysis of a timely infrastructure-as-code topic. All automated failures are false positives: the hashicorp.com allowlist warning is a tooling limitation, and the HTTP 429 is rate-limiting, not a dead link. The article is factually accurate, neutral in tone, appropriately scoped for Analysis category, and covers a topic not previously published on this platform. Approved for publication.