timetobail
My stack

HCP Vagrant · Closing down · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on HCP Vagrant and the Vagrant public box registry?

Time to Bail · Boarding pass

FromHCP Vagrant and the Vagrant public box registry
ToYour pick

Yes.

HCP Vagrant is decommissioned December 31, 2026. Move your boxes to another host first.[1]

Bail means: it is ending, or getting much worse, for this group. Leave before the date.

Gate closes
End of operations
Time left
77days
Status
Bail

HCP Vagrant and the public box registry end December 31, 2026

HashiCorp ends HCP Vagrant, which hosts the public Vagrant box registry. Support ends November 2, 2026. On December 31, 2026 all deployments are decommissioned. Move your boxes first.

How it is winding down

  1. Oct 1No new boxes or registries fromDone
  2. Nov 2End of support and maintenanceNext
  3. Dec 31End of operations

What to do before December 31

Tick steps as you go. Your progress stays in this browser.

  1. List the boxes you use

    Check each Vagrantfile for config.vm.box names that come from the public registry.

  2. Download the boxes you need

    Save the .box files you depend on now, before support ends November 2, 2026.

  3. Host them yourself

    Put the boxes and catalog metadata on your own storage, then point your Vagrantfiles to it.

Facts we checked

Facts and their sources
End of operationsDecember 31, 2026[1]
No new boxes or registries fromOctober 1, 2026[1]
End of support and maintenanceNovember 2, 2026[1]
What happensAll deployments are decommissioned on December 31, 2026[1]
What you must doMove your Vagrant boxes to another host and pay for that hosting[2]
What the new host needsIt must serve the .box files and catalog metadata to the Vagrant CLI[2]
Promised helpTools to export boxes and guidance on hosting boxes in S3[1]
Boxes hosted on HCP VagrantMust be moved by December 31, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. HCP Vagrant end of life HashiCorp · primary · checked Oct 13
  2. HCP Vagrant deprecation: important dates and migration guidance HashiCorp · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on HCP Vagrant and the Vagrant public box registry? Yes. HCP Vagrant is decommissioned December 31, 2026. Move your boxes to another host first.

On our scale this is Bail: it is ending, or getting much worse, for this group. Move your work out now.

HashiCorp ends HCP Vagrant, which hosts the public Vagrant box registry. Support ends November 2, 2026. On December 31, 2026 all deployments are decommissioned. Move your boxes first.

Here are the facts we checked:

  • End of operations: December 31, 2026 (HashiCorp)
  • No new boxes or registries from: October 1, 2026 (HashiCorp)
  • End of support and maintenance: November 2, 2026 (HashiCorp)
  • What happens: All deployments are decommissioned on December 31, 2026 (HashiCorp)
  • What you must do: Move your Vagrant boxes to another host and pay for that hosting (HashiCorp)
  • What the new host needs: It must serve the .box files and catalog metadata to the Vagrant CLI (HashiCorp)
  • Promised help: Tools to export boxes and guidance on hosting boxes in S3 (HashiCorp)
  • Boxes hosted on HCP Vagrant: Must be moved by December 31, 2026 (HashiCorp)

This is a full shutdown, not a pause. When the service closes, files and lists you did not save may be gone.

Do not wait for a last reminder email. Those emails are often late, and some never come.

HashiCorp is the main source for this page. HCP Vagrant has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Boxes hosted on HCP Vagrant: Must be moved by December 31, 2026.

Export takes some work. Do not leave it for the last day.

The date to remember is December 31, 2026. After that, it may be too late to save what you need.

What to do before December 31

  1. List the boxes you use. Check each Vagrantfile for config.vm.box names that come from the public registry.
  2. Download the boxes you need. Save the .box files you depend on now, before support ends November 2, 2026.
  3. Host them yourself. Put the boxes and catalog metadata on your own storage, then point your Vagrantfiles to it.

A few rules help every move go well:

  • Save what you can first. Pick the new tool after that.
  • Keep every export in two places, like your laptop and a cloud drive.
  • Test the new tool with a small part of your data before you move it all.
  • Tell your users or team once, in one short and clear message.

How to tell your users

Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People leaving HCP Vagrant and the Vagrant public box registry need a new home. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product