# VM Sandboxes

### (Previously Devboxes) [Permalink for this section](/content/docs/learn/vm-sandboxes/overview#previously-devboxes/index.html)

CodeSandbox provides two development environments that are ideal for prototyping and rapid web development: [VM Sandboxes](/content/docs/learn/vm-sandboxes/overview/index.html) and [Browser Sandboxes](/content/docs/learn/browser-sandboxes/templates/index.html).

We generally recommend using VM Sandboxes, which provide all the tooling needed for building prototypes. Sandboxes are mostly useful as a playground for basic front-end JavaScript projects.

VM Sandboxes are a great way to work on any type of project, regardless of its language or size. VM Sandboxes run [VMs](/content/docs/learn/environment/vm/index.html) and leverage our memory snapshotting to spin up an environment in 1.5 seconds. They have built-in [Docker support](/content/docs/learn/environment/docker/index.html) and include several valuable features, such as [AI](/content/docs/learn/ai/overview/index.html), collaborative [Terminals](/content/docs/learn/repositories/terminal/index.html), [Tasks](/content/docs/learn/repositories/task/index.html), and [VS Code integration](/content/docs/learn/getting-started/setting-up-vscode/index.html).

ℹ️

VM Sandboxes run on VM credits. Check out the [plans page](/content/docs/learn/plans/subscriptions/index.html) to learn how these credits work.

## What is a VM Sandbox? [Permalink for this section](/content/docs/learn/vm-sandboxes/overview#what-is-a-vm-sandbox/index.html)

Unlike Sandboxes that run on your browser, VM Sandboxes run on our [VMs](/content/docs/learn/environment/vm/index.html).

VM Sandboxes are great for prototyping any type of project in any programming language. They can run both backend and front-end services.
You can learn more about the editor and the unique functionalities of the cloud developer environment in [repositories](/content/docs/learn/repositories/overview/index.html).

Like Browser Sandboxes, VM Sandboxes are free to use.

VM Sandboxes run on VMs, which brings two features that make them great for prototyping:

1. Fast cloning. You can fork VM Sandbox [within 2 seconds (opens in a new tab)](/content/blog/how-we-clone-a-running-vm-in-2-seconds/index.html) and continue with an exact clone of the microVM. This way, you can quickly test multiple approaches to your prototype.
2. Instant resume. When you connect to a VM Sandbox, it will wake up within 1 second and continue with your running dev server. This way, you can quickly continue prototyping.

VM Sandboxes and Repository branches run on the same infrastructure and use the same editor. The main distinction is that Repositories have more features suited to full-scale development. Once you create a Repository from a VM Sandbox you will have:

- Branching
- Git tooling
- Full integration with GitHub

To configure a VM Sandbox, you can read more about [tasks (opens in a new tab)](/content/docs/learn/repositories/task/index.html) and [Docker (opens in a new tab)](/content/docs/learn/environment/docker/index.html).

## Creating a VM Sandbox [Permalink for this section](/content/docs/learn/vm-sandboxes/overview#creating-a-vm-sandbox/index.html)

To create a new VM Sandbox, you can clone a template from our ["Create VM Sandbox" (opens in a new tab)](/content/d/index.html) modal. When clicking on a template, we create a fork (a copy) of the template and open the newly created sandbox in our web editor.

[Collaborate & Share](/content/docs/learn/repositories/collaborate-share "Collaborate & Share"/index.html) [Getting Started](/content/docs/learn/vm-sandboxes/your-first-sandbox "Getting Started"/index.html)
