HashiCorp winds down Boundary Community Edition and HCP Vagrant

Two new entries tonight, and they rhyme. HashiCorp is narrowing Boundary and Vagrant to their commercial cores — the open-source command-line tools keep working in both cases, but the free community build and the hosted registry around them are being pulled.

Deprecated, effective now: Boundary Community Edition

HashiCorp announced on 9 October that it is deprecating Boundary Community Edition — the free, self-hosted edition of its zero-trust secure-access and privileged-access tool — and has archived the hashicorp/boundary GitHub repository effective immediately. The repo is read-only now: no more releases, bug fixes, or security patches from HashiCorp. The company is concentrating all development on the commercial editions, HCP Boundary and Boundary Enterprise, neither of which is affected.

Existing Community Edition deployments keep running, but HashiCorp’s own guidance is pointed: review the license and any open bugs or security vulnerabilities before you keep relying on it. The code can still be forked and self-maintained — you just inherit the maintenance. If you need a supported path, it is the commercial editions or a third-party tool such as Teleport.

Shutting down 31 December: HCP Vagrant box registry

The hosted HCP Vagrant service — the box registry many still call Vagrant Cloud — is being decommissioned in three steps:

• 1 October 2026 — no new boxes or registries can be created (already passed).
• 2 November 2026 — end of support and maintenance for existing deployments.
• 31 December 2026 — all remaining Vagrant deployments are decommissioned; the hosted boxes stop being served.

If any of your Vagrantfiles pull a box from an HCP-hosted registry, vagrant up will break once the service is gone. The fix is to move those boxes to your own hosting before year-end — HashiCorp says it will document an Amazon S3 path, and any replacement needs to serve the .box files and catalog metadata the CLI expects. As with Boundary, the open-source Vagrant CLI and its GitHub repository are unaffected: this is the hosting going away, not the tool.

Reached today: Microsoft Sentinel SAP container images removed

The container images for Microsoft Sentinel’s containerized (agent-based) SAP data connector are removed today, 14 October, completing the retirement that began when the connector itself went unsupported on 14 September. After today there is no supported way to pull, redeploy, scale, or recover the container agent — a running one may limp on, but a failed one has no rebuild path. The supported replacement is the agentless SAP data connector. The entry’s status is now passed, re-verified against Microsoft’s migration guide.

The next few weeks on the board

Dates ahead, each verified against its primary source: Cloudflare Workers KV legacy API (15 Oct), OpenSSL 3.4 end of life and Minimus shutdown (both 22 Oct), OpenAI GPT-4 / GPT-3.5 / o1 / o3 model removals (23 Oct), Kubernetes 1.34 end of life (27 Oct), Fitbit’s legacy Web API turned off (30 Oct), OpenAI’s hosted Evals platform going read-only (31 Oct), and HCP Vagrant’s full shutdown (31 Dec). Full board with live countdowns on the calendar.