HashiCorp is deprecating HCP Vagrant through a phased process. The Vagrant CLI and source repository will remain available, but customers must move their Vagrant boxes to another hosting provider and assume the associated hosting costs.
HCP Vagrant will stop supporting new box and registry creation on October 1, 2026, and customers using HCP Vagrant have until December 31, 2026 to find a new provider and rehost their boxes. To help with the transition, we will release additional capabilities, including:
The option to export boxes to a local drive
Guidance on how to host Vagrant boxes in Amazon S3
Details about the folder structure required to support multiple providers and architectures
Instructions for taking a snapshot of all existing Vagrant boxes and placing them into a static archive that uses URL redirects during the transition
»Important dates in the deprecation rollout
End of new creation: October 1, 2026. After this date, users cannot create new Vagrant boxes or registries
End of support and maintenance: November 2, 2026. HashiCorp will end support and maintenance for existing Vagrant deployments
End of operations: December 31, 2026. HashiCorp will decommission all remaining Vagrant deployments
»Deprecation details
This deprecation applies only to HCP Vagrant. The Vagrant CLI and source repository on GitHub will remain available, enabling teams to continue building boxes locally and sharing them through a new customer-hosted box repository. However, users will no longer be able to create new boxes or share box environments through the HCP Vagrant and Vagrant Public Registry interfaces after the applicable shutdown dates.
»Start planning your migration now
Start your migration by taking inventory of where HCP Vagrant Registry is used across your organization.
Consider reviewing:
Vagrantfiles that reference registry-hosted boxes
CI/CD pipelines that download or publish boxes
Internal developer documentation
Onboarding guides
Automation scripts
Public or private boxes your team maintains
Any downstream users or teams that depend on those boxes
Once you understand how your organization uses HCP Vagrant, evaluate where you will host those boxes after the service ends. Your replacement repository must make the .box files and catalog metadata available to the Vagrant CLI. Catalog metadata preserves information about box versions, providers, architectures, download URLs, and checksums.
To support a smooth transition, we will publish migration guides that explain how to migrate your HCP Vagrant Registry data to customer-managed hosting solutions. If you encounter issues during this phased deprecation, please open an issue on our Vagrant GitHub repository or reach out to vagrant@ibm.com
