HashiCorp has announced that HCP Vagrant will no longer accept new box or registry creations after October 1 2026 and will be fully shut down on December 31 2026. This affects any workflow that relies on the hosted registry for publishing or pulling Vagrant boxes, so engineers need to relocate those artifacts, adjust automation, and budget for new hosting.
Key dates and shutdown timeline
- October 1 2026: Creation of new boxes or registries via HCP Vagrant is blocked.
- November 2 2026: HashiCorp ends support and maintenance for existing deployments.
- December 31 2026: All remaining HCP Vagrant services are decommissioned.
Supported migration mechanisms
HashiCorp will provide three practical aids to move your boxes:
- Export of existing boxes to a local drive.
- Guidance for hosting
.boxfiles in Amazon S3, including required folder layout for multiple providers and architectures. - Instructions to snapshot the full registry into a static archive that uses URL redirects during the transition.
Architectural and operational considerations
When you replace HCP Vagrant, the new repository must expose both the raw .box files and the accompanying catalog metadata (versions, providers, architectures, URLs, checksums) in a format the Vagrant CLI can consume. This has several downstream effects:
- CI/CD pipelines: Update any
vagrant box addorvagrant box pushsteps to point at the new endpoint. - Documentation and onboarding: Revise Vagrantfile examples, internal guides, and new‑hire material to reference the new host.
- Automation scripts: Adjust any custom tooling that enumerates boxes from the HCP registry.
- Downstream consumers: Notify teams that depend on shared boxes to avoid broken builds.
Because the Vagrant CLI and source repository remain available, you can continue to build boxes locally; the only change is the distribution layer. Hosting costs will now be borne by the consuming organization, so budgeting for storage and egress (especially for S3) becomes a new operational item.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Take immediate inventory of all HCP Vagrant references across code, pipelines, and docs. Choose a hosting target (e.g., Amazon S3) and follow the published folder‑structure guide. Export your current boxes, verify that the catalog metadata is correctly reproduced, and run a smoke test with vagrant box add from the new location. Finally, update CI/CD definitions and documentation before the October 1 2026 cut‑off to avoid service disruption.