HashiCorp Cloud Platform
Deprecation of HCP Vagrant
What's changing
HCP Vagrant is being deprecated and limited features will be available from the community edition effective March 15, 2027. Most notably this change will now require customers using Vagrant boxes to be responsible for the hosting costs incurred on given providers.
Customers with running instances will have until June 7, 2027, to find a new provider and rehost their boxes, while support for new box creation from the HashiCorp Platform will end December 14, 2026. Additional capabilities will be released to help with the transition including an ability to export boxes to a local drive, guidance on how to host Vagrant boxes in S3 along with details on the folder structure to support the variety of providers and architectures, and how to take a snapshot of all existing Vagrant boxes and put them into a static archive with URL redirects until the official deprecation.
Important dates
| Milestone | Date |
|---|---|
| End of new Box/Registry creation | December 14, 2026 |
| End of support and maintenance | March 15, 2027 |
| End of operations | June 7, 2027 |
Deprecation details
This deprecation applies to HCP Vagrant. The community edition in GitHub including the CLI will remain available to customers which will enable the ability to build boxes locally or share boxes in a new customer hosted location.
This deprecation is a phased process that concludes with end of support.
- New Vagrant boxes can no longer be created in HCP Vagrant as of December 14, 2026.
- Existing deployments will continue to operate until the end of support date of March 15, 2027.
- At the end of support, all deployments will be decommissioned effective June 7, 2027.
Next steps for current HCP Vagrant users
- Review the timeline and begin your planning process.
- Take inventory of where HCP Vagrant Registry is used across your organization.
- Start evaluating where those boxes should live in the future.
- Plan your migration.
FAQs
Q. What are the hosting costs I will now be responsible for?
A. The hosting costs users will now be responsible for will depend on the provider and hosting service they choose. Common pricing for hosting charges across some providers can be found following these links: AWS storage fees, IBM Cloud storage fees, and Azure storage fees.
Q. What happens to my ability to create new Vagrant boxes after December 14, 2026?
A. You will still be able to create new Vagrant boxes using the Vagrant command-line tool. However, you will no longer be able to create new Vagrant boxes or share box environments via HCP Vagrant and Vagrant Public Registry interfaces. The main difference is that customers will be responsible for finding a new location to host their boxes.