# Instances

## Containers and virtual machines

MNX.io provides three classes of compute instances: hardware virtual machines, infrastructure containers, and Docker containers.

### [Virtual Machines](/instances/virtual-machines.md) <a href="#triton-virtual-machines" id="triton-virtual-machines"></a>

Virtual machines (VMs) are hardware virtual machines (HVMs) wrapped in highly secure zones, supporting a variety of images including Linux, FreeBSD, Windows, and Docker Engine.

Each HVM is implemented using a hypervisor: either KVM or bhyve. KVM was the first HVM supported and remains a strong choice for most VMs, particularly if you are already using KVM in Triton and are satisfied with the performance and features. Bhyve is a newer HVM which aims to improve performance and scalability, while growing the feature set. Because bhyve is relatively new, not all images are supported on bhyve.&#x20;

### [Infrastructure containers](/instances/infrastructure-containers.md) <a href="#infrastructure-containers" id="infrastructure-containers"></a>

Leverage container-native Linux (lx zones) on infrastructure containers to extend the benefits of containerization to legacy applications and stateful services, such as databases. Containerizing an application in infrastructure containers is easy because they offer all the services of a typical unix host and behave similarly to hardware virtual machines.

Infrastructure containers enjoy their own virtual NICs, filesystems, and all the resource and security isolation that you'd expect of a Virtual Machine, but with the elastic performance and bursting that's only possible with containers.

### [Docker containers](broken://pages/-LuID4_toQjz50xpAsA2) <a href="#docker-containers" id="docker-containers"></a>

Other Docker run-time environments require complex VM host cluster management and provide only limited networking and security capabilities, Using MNX.io transforms an entire data center into an easy to manage, elastic Docker host, while delivering enterprise grade networking and security to each Docker container.

### Comparing containers vs. virtual machines <a href="#comparing-containers-vs-virtual-machines" id="comparing-containers-vs-virtual-machines"></a>

It can be difficult to decide which type of infrastructure to use for an application. Below are some example scenarios in which you may decide on using a containerized instance versus a virtual machine.

| Purpose                                                                | Container | VM |
| ---------------------------------------------------------------------- | --------- | -- |
| Secure and high performance                                            | ✓         | ✓  |
| Brand new microservice-based application                               | ✓         | ✓  |
| Existing application to be converted into microservices                | ✓         | ✓  |
| Quickly resize instances without rebooting                             | ✓         | ✗  |
| Specific environment needs such as FreeBSD, Windows, and Docker Engine | ✗         | ✓  |
| Legacy applications                                                    | ✗         | ✓  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mnx.io/instances.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.