HCP Vagrant winds down: no new boxes from 1 October, shut on 31 December

HCP Vagrant winds down: no new boxes from 1 October, shut on 31 December

22 September 2026 — HashiCorp is deprecating HCP Vagrant, the hosted registry that took over from Vagrant Cloud in 2024. It announced the timetable on 17 September. The Vagrant command-line tool and its source code stay available. The hosted registry, and HashiCorp paying to host other people's boxes, do not.

The three dates

• 1 October 2026: end of new creation. From this date nobody can create new Vagrant boxes or registries on the platform.
• 2 November 2026: end of support and maintenance. HashiCorp stops supporting and maintaining existing deployments. Its documentation says only limited features remain, through the community edition, from this date.
• 31 December 2026: end of operations. HashiCorp decommissions all remaining deployments. Customers with running instances have until then to rehost their boxes.

The documentation states the consequence plainly: customers using Vagrant boxes become responsible for the hosting costs on whichever provider they choose.

What HashiCorp says it will provide

HashiCorp promises four things. It will offer a way to export boxes to a local drive, and guidance on hosting boxes in Amazon S3. It will document the folder structure needed for different providers and architectures. And it will explain how to snapshot existing boxes into a static archive that uses URL redirects during the transition. It says it will publish migration guides for moving registry data to customer-managed hosting.

What to do now

• Inventory first. HashiCorp's own checklist covers Vagrantfiles that reference registry-hosted boxes, CI/CD pipelines that download or publish boxes, and internal documentation and onboarding guides. It also names automation scripts, the public or private boxes your team maintains, and any downstream teams that depend on them.
• Publish before 1 October if you must. A team that ships new box versions has little more than a week left to do it on the platform. After that, new versions need somewhere else to live.
• Choose where boxes will live. The replacement has to serve both the .box files and the catalogue metadata the Vagrant CLI reads: versions, providers, architectures, download URLs and checksums. Object storage with a static catalogue is the route HashiCorp describes.
• Budget for it. Storage and egress for large boxes become your bill. Estimate it from the box sizes and download counts you see today.

The announcement leaves several things open. It does not say when the export tool and migration guides will ship, or whether public boxes will still download after 31 December. A team that depends on public boxes it does not control should copy the versions it needs now. HashiCorp's contact for the transition is vagrant@ibm.com.

Sources

• HashiCorp blog, "HCP Vagrant deprecation: important dates and migration guidance" — 17 September 2026
• HashiCorp Developer, "Deprecation of HCP Vagrant" (read 22 September 2026) — 22 September 2026