For development on Windows 10 Pro, CloudCaptain can run your apps on Hyper-V.


  • dev

Supported Versions

CloudCaptain supports Hyper-V running on Windows 10 Pro.

VirtualBox compatibility

Due to the way Hyper-V is architected, VirtualBox will no longer work if Hyper-V is enabled. If you need VirtualBox compatibility, you must disable Hyper-V to make VirtualBox work again.

CPU & RAM usage

You can control the number of CPUs exposed to the VM using the cpus property and the number of MB of RAM using the ram property. By default, CloudCaptain assigns 2 CPUs and 1024 MB of RAM to the Instance.


CloudCaptain creates a new public Hyper-V Virtual Switch on your external network interface.

Accessing services running on the physical host

To make it easy to access services running on your physical machine (outside of your CloudCaptain Hyper-V instance), CloudCaptain exposes an environment variable named BOXFUSE_HOST_IP to each of its Hyper-V instances. This environment variable contains the IP address of your physical machine (example: which you can use this to construct URLs to access your services.

Live images

To use Hyper-V with live images, you must set the windows.user and windows.password properties to ensure the Hyper-V instance can access the directory on your host.

AWS Credentials

To make it easy to access AWS services from your VirtualBox instances, CloudCaptain automatically exposes the AWS credentials stored by the AWS CLI on your local machine to the running instances.

CloudCaptain will attempt to load credentials in the following order:

  1. The boxfuse profile in ~/.aws/credentials
  2. The default profile in ~/.aws/credentials
  3. The default section in ~/.aws/config

You can also manually override this by explicitly setting the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.


Database support is not yet available on Hyper-V. If you need this feature, use VirtualBox instead.