# BYOC


BYOC (bring your own cloud) runs your team's VMs on servers in your own cloud
account or data center. exe.dev runs those servers as part of exe.dev, and
your team uses it just as it would on our hardware.

## Why

- **Keep workloads in your account.** VMs, and the disks they write, sit on
  machines you own, inside your network and your security controls.
- **Run next to your data.** VMs are close to the databases and services
  they work with, with no trip across the internet.
- **Spend what you have.** Put existing cloud commitments and credits toward
  the capacity.
- **Choose where.** Run in the regions your compliance requirements name,
  not just [ours](/docs/regions).

## How it works

Your servers become dedicated hosts assigned to your team. Every new pool the
team creates is placed on one of them automatically, as with any
[dedicated hardware](/docs/pools#regions):

```
pool hosts                 # your hosts: region, status, largest pool each can take
pool new build --cpus=32   # no --region; the host decides
```

Pools on your hosts take effect immediately at any size a host can take, and
never fall back to shared hardware. Everything above the hosts works as
described in [Enterprise exe](/docs/enterprise): the HTTPS proxy and custom
domains, integrations, teams and SSO, Shelley, and the CLI and API.

## Servers

exe.dev VMs are KVM virtual machines with their disks on local NVMe, so a
host needs hardware virtualization and local NVMe drives: a bare-metal
instance from your cloud provider, or a server in your own rack. We work out
the fleet's size and layout with you.

## Getting started

BYOC is part of [Enterprise exe](/docs/enterprise). Email
[support@exe.dev](mailto:support@exe.dev) to set it up.