SaaS
HashiCorp
HashiCorp is retiring HCP Vagrant, its hosted Vagrant box registry. New box and registry creation ends 14 December 2026, support ends 15 March 2027, and all operations cease on 7 June 2027, after which hosted boxes are decommissioned. The Vagrant CLI and community edition are not affected.
departs 7 Jun 2027
Quick answers
- Is it true that HCP Vagrant Registry is shutting down — boxes must move off by 7 June 2027?
- Yes. HashiCorp has officially announced it, effective 7 Jun 2027. HCP Vagrant Registry is the hosted service where Vagrant users publish, version, and download "boxes" — the base VM images a Vagrantfile pulls to spin up a development environment.
- When does it take effect?
- 7 Jun 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Start by taking inventory: find everywhere your organization references HCP Vagrant Registry — Vagrantfiles that pull hosted boxes, CI that provisions from them, and any boxes you publish for others.
What this means for you
HCP Vagrant Registry is the hosted service where Vagrant users publish, version, and download "boxes" — the base VM images a Vagrantfile pulls to spin up a development environment. It is the successor to Vagrant Cloud, which HashiCorp migrated into HCP. Now HashiCorp is winding the hosted registry down entirely, on a staged timeline: new box and registry creation ends 14 December 2026; support and maintenance end 15 March 2027; and on 7 June 2027 operations end and hosted boxes are decommissioned. The important scope limit: this is only the hosted HCP Vagrant service. Vagrant itself — the open-source CLI and the community edition on GitHub — is not going away; you can still build boxes locally and share them from a location you host yourself. What disappears is HashiCorp's hosted place to store and distribute those boxes, along with the free public hosting many teams and box publishers have relied on. Anyone whose Vagrantfiles reference boxes hosted on HCP Vagrant, or who publishes boxes for others to consume, needs a new home for those artifacts before 7 June 2027.
Where to go
Start by taking inventory: find everywhere your organization references HCP Vagrant Registry — Vagrantfiles that pull hosted boxes, CI that provisions from them, and any boxes you publish for others. Then decide where those boxes should live. HashiCorp's guidance is that boxes move to customer-hosted storage; common targets are object storage such as AWS S3, Azure Blob Storage, or another provider you control, with Vagrant configured to fetch boxes from there. Note the two intermediate dates while you plan: after 14 December 2026 you can no longer create new boxes or registries on HCP, and after 15 March 2027 the service is unsupported, so treat those as the practical windows to finish publishing and to complete testing of your new hosting. The hard deadline is 7 June 2027, when hosted boxes are decommissioned. Because the CLI and local box building continue, this is a migration of where artifacts are stored, not a change to how Vagrant itself works — but you do take on the hosting (and its cost) yourself.
- Self-hosted object storage (AWS S3, Azure Blob Storage, or similar) as the new home for your Vagrant boxes, fetched directly by the Vagrant CLI
- The Vagrant community edition / CLI on GitHub — unaffected; keeps building boxes locally and sharing them from a location you host
HashiCorp is retiring HCP Vagrant, the hosted registry where Vagrant users store and distribute the base VM images — “boxes” — that a Vagrantfile pulls to build a development environment. This is the same service that absorbed the old Vagrant Cloud when HashiCorp folded it into the HashiCorp Cloud Platform. Now the hosted registry is being wound down on a staged schedule.
The timeline
HashiCorp’s official end-of-life page lays out three dates:
- 14 December 2026 — end of new box and registry creation. After this you can no longer create new boxes or registries on HCP Vagrant.
- 15 March 2027 — end of support and maintenance. The service keeps running but is unsupported.
- 7 June 2027 — end of operations. Hosted boxes are decommissioned; this is the hard deadline.
What is not going away
This is a shutdown of the hosted service only. Vagrant itself — the open-source CLI and the community edition on GitHub — continues. You can still build boxes locally and share them from a location you host. What you lose is HashiCorp’s hosted place to keep and distribute boxes, including the free public hosting that many box publishers and teams have leaned on. The practical shift is that box hosting (and its cost) becomes your responsibility.
What to do
Treat this as an artifact-migration project, not a tooling change. Inventory every reference to HCP Vagrant Registry — Vagrantfile entries that pull hosted boxes, CI that provisions from them, and any boxes you publish for others. Pick a new home: HashiCorp points customers to self-hosted storage, and object stores like AWS S3 or Azure Blob Storage are the usual destinations, with Vagrant configured to fetch boxes from there. Use the intermediate dates as planning fences — finish publishing before 14 December 2026, and have your replacement hosting tested before support ends on 15 March 2027 — so that nothing depends on HCP when operations end on 7 June 2027.
Entry changelog
- — last reviewed.
- — Entry created from HashiCorp's official HCP Vagrant end-of-life page. Staged timeline: new box/registry creation ends 14 Dec 2026, support ends 15 Mar 2027, operations end (boxes decommissioned) 7 Jun 2027. Vagrant CLI/community edition unaffected. Surfaced via Layer-2 discovery.
Put this countdown in your README
Building on HashiCorp? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/hcp-vagrant-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.