Deprecation of HCP Vagrant | HashiCorp Cloud Platform | HashiCorp DeveloperHashiConf 2025 Don't miss the live stream of HashiConf Day 2 happening now View live stream

Sign in<br>Sign up

Theme

HashiCorp Cloud Platform Home

Deprecation of HCP Vagrant

What's changing<br>HCP Vagrant is being deprecated and limited features will be available from the community edition effective March 15, 2027.<br>Most notably this change will now require customers using Vagrant boxes to be responsible for the<br>hosting costs incurred on given providers.<br>Customers with running instances will have until June 7, 2027, to find a new provider and rehost<br>their boxes, while support for new box creation from the HashiCorp Platform will end December 14,<br>2026. Additional capabilities will be released to help with the transition including an ability to<br>export boxes to a local drive, guidance on how to host Vagrant boxes in S3 along with details on<br>the folder structure to support the variety of providers and architectures, and how to take a<br>snapshot of all existing Vagrant boxes and put them into a static archive with URL redirects until<br>the official deprecation.<br>Important dates<br>MilestoneDateEnd of new Box/Registry creationDecember 14, 2026End of support and maintenanceMarch 15, 2027End of operationsJune 7, 2027

Deprecation details<br>This deprecation applies to HCP Vagrant. The community edition in GitHub including the CLI will<br>remain available to customers which will enable the ability to build boxes locally or share boxes<br>in a new customer hosted location.<br>This deprecation is a phased process that concludes with end of support.<br>New Vagrant boxes can no longer be created in HCP Vagrant as of December 14, 2026.<br>Existing deployments will continue to operate until the end of support date of March 15, 2027.<br>At the end of support, all deployments will be decommissioned effective June 7, 2027.<br>Next steps for current HCP Vagrant users<br>Review the timeline and begin your planning process.<br>Take inventory of where HCP Vagrant Registry is used across your organization.<br>Start evaluating where those boxes should live in the future.<br>Plan your migration.<br>FAQs<br>Q. What are the hosting costs I will now be responsible for?<br>A. The hosting costs users will now be responsible for will depend on the provider and hosting<br>service they choose. Common pricing for hosting charges across some providers can be found<br>following these links: AWS storage fees, IBM Cloud storage fees, and Azure storage fees.<br>Q. What happens to my ability to create new Vagrant boxes after December 14, 2026?<br>A. You will still be able to create new Vagrant boxes using the Vagrant command-line tool. However,<br>you will no longer be able to create new Vagrant boxes or share box environments via HCP Vagrant<br>and Vagrant Public Registry interfaces. The main difference is that customers will be responsible<br>for finding a new location to host their boxes.

Edit this page on GitHub