HashiCorp is deprecating HCP Vagrant — the cloud-hosted Vagrant box registry and hosting service (formerly Vagrant Cloud) — in three steps: no new boxes/registries after 1 October 2026, end of support 2 November 2026, and full decommission of all remaining deployments on 31 December 2026

What this means for you

If any of your Vagrantfiles pull boxes from HCP Vagrant (the hosted box registry many teams know as Vagrant Cloud), that hosting is going away and your boxes will stop being served. The shutdown runs in three steps: as of 1 October 2026 you can no longer create new Vagrant boxes or registries; on 2 November 2026 HashiCorp ends support and maintenance for existing deployments; and on 31 December 2026 it decommissions all remaining Vagrant deployments, after which the hosted boxes are gone. Any `vagrant up` that resolves a box from an HCP-hosted registry will break once the service is decommissioned. This is a shutdown of the hosting service only — the open-source Vagrant CLI and its GitHub repository are unaffected and keep working; you just have to host your boxes somewhere else.

Where to go

Inventory every Vagrantfile that references an HCP-hosted (Vagrant Cloud) box, then move those boxes to alternative hosting before 31 December 2026. HashiCorp says it will provide migration guidance, including instructions for hosting boxes on Amazon S3; any replacement needs to serve the ".box files and catalog metadata" the Vagrant CLI expects. After the shutdown you can continue building boxes locally and distributing them through a self-managed repository — the CLI itself does not change.

• Self-host boxes on Amazon S3 (HashiCorp's documented migration path) or any store serving .box files + catalog metadata
• A self-managed box repository referenced directly from your Vagrantfile
• The open-source Vagrant CLI and GitHub repository remain available and unaffected