# Arm64 VDS: 64-bit Arm servers with nested virtualization

> Arm64 VDS: 64-bit Arm (AArch64) virtual servers with nested virtualization and full root access, for build VMs, image testing and Arm-native apps.

1. [Home](https://hyperdc.com/)
2. [Cloud Servers](https://hyperdc.com/cloud-servers)
3. [VDS Hosting](https://hyperdc.com/vds-hosting)
4. Arm64 VDS

A 64-bit Arm (AArch64) virtual server with nested virtualization and full root access. Run your own Arm virtual machines inside it, give every build a clean VM of its own and host Arm-native apps, on the operating systems listed with each plan.

- 64-bit Arm (AArch64) virtual server
- Nested virtualization for your own VMs
- Full root access over SSH
- Systems and locations listed with each plan

View plans

root@arm64: \~

root@arm64:\~# uname -m

aarch64

root@arm64:\~# docker build -t app .

Successfully tagged app:latest

root@arm64:\~# docker run app uname -m

aarch64

root@arm64:\~#

## Choose a plan that fits

Tell us what you need and our team will help you choose the right plan.

[Contact us](https://hyperdc.com/contact-us) [Client area](https://hyperdc.com/account)

## Your own Arm virtual machines, inside your server

An Arm64 VDS is a 64-bit Arm (AArch64) virtual server like our Arm64 VPS, with one addition: nested virtualization. Your server can start virtual machines of its own, so you can give every build a clean VM, test images before they ship or run a small lab, all on Arm.

Everything else stays familiar: root access over SSH, the operating systems and locations listed with each plan, and the same client area as your other services.

View plans Compare Arm64 lines

- Nested virtualization for your own Arm VMs
- arm64 binaries and container images run natively
- Root access over SSH
- Operating systems listed with each plan
- Locations listed with each plan

## 64-bit Arm with room for your own VMs

### Nested virtualization

Start your own 64-bit Arm virtual machines inside the server: nested virtualization is available on every Arm64 VDS plan.

### 64-bit Arm processors

Your server's virtual processors run 64-bit Arm (AArch64) code, so software built for arm64 runs the way it was built to.

### Full root access

Log in as root over SSH, install packages from your system's arm64 repositories and configure every service yourself.

### Isolated builds

Give every build or test run its own throwaway VM, so jobs never share files, caches or credentials.

### Containers and Kubernetes

Run arm64 and multi-platform images with Docker or Podman, or a small Kubernetes cluster with k3s.

### Arm64 CI runners

Register the server as a GitHub Actions, GitLab or Jenkins runner and build arm64 releases in every pipeline.

### Systems from the plan

Each plan lists the operating systems it offers, and you pick one in the order form.

### Locations from the plan

Each plan lists the data centers it is offered in; pick the one closest to your users when you order.

### Help from our team

Open a support ticket if the server or the network needs attention, and follow every reply in one place.

## What runs well on an Arm64 VDS

### A clean virtual machine for every build

Start a fresh arm64 VM for every CI job or release build and delete it afterwards. Builds stay reproducible, and a broken job never leaves files or credentials behind for the next one.

- One VM per job or release
- The same base image every time
- Nothing left behind between runs

### Test operating-system images and upgrades

Boot the cloud images, appliances or golden images you prepare for Arm servers in a virtual machine first, check cloud-init, packages and services, and rehearse upgrades before they reach production.

### Software for Arm devices

Run the 64-bit Arm Linux your gateways, edge boxes or single-board computers use in a virtual machine, test new builds there and keep a known-good environment for every device generation.

### Multi-architecture container images

Build the linux/arm64 variant of your images natively with Docker Buildx, push it next to the amd64 variant and publish one multi-platform tag, so every user pulls the right image for their machine.

- Native arm64 layers, no emulation
- One tag for arm64 and amd64
- Your own registry or Docker Hub

root@arm64: \~

root@arm64:\~# uname -m

aarch64

root@arm64:\~# docker build -t app .

Successfully tagged app:latest

root@arm64:\~# docker run app uname -m

aarch64

root@arm64:\~#

### Network and operating-system labs

Build small labs of several Arm virtual machines on one server to practise routing, firewalls, clustering or configuration management without touching production.

### Arm-native web servers and APIs

Serve websites, APIs and background workers with Nginx, Caddy, Node.js, Python, Go, PHP or Java, all of which run natively on arm64, with PostgreSQL, MySQL or Redis next to them.

## Technical specifications

What every plan on this page shares. vCPU, memory and storage differ by plan and are listed with each plan.

Architecture 64-bit Arm (AArch64) uname -m prints aarch64\
Server type Virtual dedicated server with nested virtualization Run your own Arm virtual machines inside\
Virtual machines inside 64-bit Arm guests x86 guests only through emulation\
Access Root over SSH Sign in with your SSH key\
Containers Docker, Podman and k3s on arm64 Pull the arm64 or multi-platform variant of an image\
x86 software Needs an arm64 build or emulation Keep x86-only software on a Linux VDS\
Operating systems Listed with each plan Pick one in the order form\
Locations Listed with each plan Pick one in the order form\
Support Support tickets from the client area

## Arm64 VDS, Arm64 VPS or Linux VDS?

All three are virtual servers with full root access. They differ in the processor architecture and in whether you can run your own virtual machines inside.

| Feature | This page **Arm64 VDS** 64-bit Arm with nested virtualization (Recommended) | **Arm64 VPS** A 64-bit Arm virtual server | **Linux VDS** x86-64 with nested virtualization |
| --- | --- | --- | --- |
| Processor architecture | 64-bit Arm (AArch64) | 64-bit Arm (AArch64) | x86-64 |
| Native arm64 softwareBinaries and container images built for linux/arm64. | Included | Included | Not included |
| Native x86 softwareBinaries and container images built for linux/amd64. | Not included | Not included | Included |
| Your own VMs insideNested virtualization lets your server start virtual machines of its own; on Arm64 these are 64-bit Arm virtual machines. | Included | Not included | Included |
| Virtual machines inside | 64-bit Arm guests | No VMs inside | x86-64 guests |
| Root access | Included | Included | Included |
| Operating systems | Listed with each plan | Listed with each plan | Linux distributions and BSD |
| Best for | Clean build VMs, image testing and labs on Arm | Arm-native apps, arm64 builds and CI, scale-out services | x86 VM labs, databases and larger apps |

- This page
  ### Arm64 VDS (Recommended)
  64-bit Arm with nested virtualization
  Processor architecture 64-bit Arm (AArch64)\
  Native arm64 softwareBinaries and container images built for linux/arm64. Included\
  Native x86 softwareBinaries and container images built for linux/amd64. Not included\
  Your own VMs insideNested virtualization lets your server start virtual machines of its own; on Arm64 these are 64-bit Arm virtual machines. Included\
  Virtual machines inside 64-bit Arm guests\
  Root access Included\
  Operating systems Listed with each plan\
  Best for Clean build VMs, image testing and labs on Arm
- ### Arm64 VPS
  A 64-bit Arm virtual server
  Processor architecture 64-bit Arm (AArch64)\
  Native arm64 softwareBinaries and container images built for linux/arm64. Included\
  Native x86 softwareBinaries and container images built for linux/amd64. Not included\
  Your own VMs insideNested virtualization lets your server start virtual machines of its own; on Arm64 these are 64-bit Arm virtual machines. Not included\
  Virtual machines inside No VMs inside\
  Root access Included\
  Operating systems Listed with each plan\
  Best for Arm-native apps, arm64 builds and CI, scale-out services
- ### Linux VDS
  x86-64 with nested virtualization
  Processor architecture x86-64\
  Native arm64 softwareBinaries and container images built for linux/arm64. Not included\
  Native x86 softwareBinaries and container images built for linux/amd64. Included\
  Your own VMs insideNested virtualization lets your server start virtual machines of its own; on Arm64 these are 64-bit Arm virtual machines. Included\
  Virtual machines inside x86-64 guests\
  Root access Included\
  Operating systems Linux distributions and BSD\
  Best for x86 VM labs, databases and larger apps

A comparison of the server lines, not of single plans: each page lists its plans with their resources and price.

[See Arm64 VPS](https://hyperdc.com/arm64-vps) [See Linux VDS](https://hyperdc.com/linux-vds-hosting)

## Set up your Arm64 VDS

Step-by-step guides for SSH, security, Docker and Kubernetes that apply to Arm64 servers too.

[More guides](https://hyperdc.com/guides/search?product=arm64-vds)

- Tutorials [How to install Docker Engine on Ubuntu 24.04 and 26.04](https://hyperdc.com/guides/tutorials/install-docker-ubuntu)
  Install Docker Engine, Buildx and Compose from Docker's official apt repository on Ubuntu LTS, run it without sudo, rotate logs and keep published ports private.
  15 min Beginner
- Tutorials [Docker Compose basics: run multi-container apps on a Linux server](https://hyperdc.com/guides/tutorials/docker-compose-basics)
  Write a compose.yaml with services, volumes and networks, keep secrets in .env, start services in the right order with healthchecks, then update, back up and run several stacks side by side.
  35 min Beginner
- Tutorials [How to install K3s on Ubuntu: single-node Kubernetes with Traefik and HTTPS](https://hyperdc.com/guides/tutorials/install-k3s)
  Set up a single-node K3s Kubernetes cluster on Ubuntu LTS, open only the ports it needs, expose a test app through the bundled Traefik ingress with cert-manager TLS, and learn backups and upgrades.
  45 min Intermediate
- Tutorials [How to install Forgejo or Gitea with Docker Compose, PostgreSQL and HTTPS](https://hyperdc.com/guides/tutorials/install-gitea-forgejo)
  Run your own Git forge with Forgejo or Gitea: official Docker images, PostgreSQL, Caddy for HTTPS, SSH on port 2222 and no open registration, plus dump-based backups and safe major-version updates.
  40 min Intermediate
- Getting started [Connect to your Linux server with SSH](https://hyperdc.com/guides/getting-started/connect-to-linux-server-ssh)
  Your first login to a new Linux server: where to find the details, how to connect from any computer and what to do in the first five minutes.
  10 min Beginner
- Security [How to secure a new Linux server in the first hour](https://hyperdc.com/guides/security/secure-a-new-linux-server)
  A new server is reachable from the internet the moment it boots. These steps close the most common gaps before you install anything else.
  30 min Beginner

## What you get with HyperDC

### One account for everything

Hosting, servers, domains and invoices are managed from the same client area.

### Invoices in one place

Every invoice is listed in the client area, where you can also pay it online.

### Support from the client area

Open a support ticket whenever you need help and follow every reply in one place.

## From order to online

1. ### Choose a service
   Pick the product, location and billing cycle that fit your project.
2. ### Complete your order
   Review your cart and pay with one of the available payment methods.
3. ### Receive your details
   We email your login details as soon as the service is ready.
4. ### Get help when you need it
   Open a support ticket from the client area and follow every reply.

## One provider for hosting, servers and domains

Hosting and servers since 2013, with 267k+ websites hosted on our services.

### One client area for every service

Order, manage and pay for hosting, servers and domains from the same account.

hyperdc.com/account

**Services** **Domains** **Invoices**

**Linux VPS** Active

**Web hosting** Active

**example.com** Active

### Help from our team

Open a support ticket from the client area and follow every reply.

Support ticket

**You**Can you help me move my website to a new server?

**HyperDC team**Of course. Send us the details of your current host and we will plan the move with you.

Answered

### Choose your location

Pick the data center when you order. Each service page lists where it runs.

[All data centers](https://hyperdc.com/data-centers)

Europe*Nearest to you* United States

### Room to grow

Move between hosting, VPS, VDS and dedicated servers as your project grows.

[Compare servers](https://hyperdc.com/cloud-servers)

## Moving from another provider?

Tell us what you run today and where it is hosted. We will reply with the steps to move it to your new HyperDC service.

- Tell us what you run today and where it is hosted
- Get the steps to move it to your new HyperDC service
- Switch over when everything is ready

[Contact us](https://hyperdc.com/contact-us)

**Current host** **HyperDC**

Files copied Databases imported DNS updated Live

## Services that work well together

### Arm64 VPS

Virtual servers on 64-bit Arm for native builds and apps.

[Learn more](https://hyperdc.com/arm64-vps)

### Linux VDS

Larger virtual servers on NVMe, with nested virtualization.

[Learn more](https://hyperdc.com/linux-vds-hosting)

### Nested Dedicated Servers

Virtualization extensions for your own VMs and emulators.

[Learn more](https://hyperdc.com/nested-dedicated-server-hosting)

### Kubernetes VPS

Lightweight Kubernetes clusters such as k3s.

[Learn more](https://hyperdc.com/kubernetes-vps)

### Data centers

See every location where HyperDC services run.

[Learn more](https://hyperdc.com/data-centers)

### Contact us

Questions before you order? Our team will help.

[Learn more](https://hyperdc.com/contact-us)

## Policies that apply

- [Terms of Service](https://hyperdc.com/legal/terms-of-services)
- [Refund Policy](https://hyperdc.com/legal/refund-policy)
- [Privacy Policy](https://hyperdc.com/legal/privacy-policy)
- [Acceptable Use Policy](https://hyperdc.com/legal/acceptable-use-policy)

## Frequently asked questions

Still have a question? Send us a message and our team will reply by email.

[Contact us](https://hyperdc.com/contact-us) [Open a ticket](https://hyperdc.com/support/new-ticket)

### What is an Arm64 VDS?

An Arm64 VDS (virtual dedicated server) is a 64-bit Arm (AArch64) virtual server with nested virtualization available, so you can run virtual machines of your own inside it. You get full root access to install the system's arm64 packages and your own tools, as on any of our virtual servers.

### What is the difference between an Arm64 VPS and an Arm64 VDS?

Both are 64-bit Arm virtual servers with full root access. At HyperDC a server is called a VDS only when nested virtualization is available on it: an Arm64 VDS can run your own virtual machines, an Arm64 VPS cannot. Choose the VPS when your workload runs directly on the server and the VDS when you need virtual machines inside it.

### What can I run inside an Arm64 VDS?

Virtual machines with 64-bit Arm operating systems, managed with the virtualization tools of your Linux distribution, and containers next to them. Typical uses are a clean VM for every build or test run, images you prepare before they go to other Arm servers or devices, and small labs for networking and operating-system work. Nested virtual machines add some overhead compared with running directly on the server.

### Can I run x86 virtual machines inside it?

Not with hardware acceleration. Nested virtualization runs guests of the server's own architecture, so the virtual machines inside an Arm64 VDS are 64-bit Arm machines. x86 guests run only through full emulation, which is far slower. For x86 virtual machines, choose a Linux VDS.

### Are Arm64, AArch64 and ARM64 the same?

Yes. AArch64 is Arm's name for its 64-bit execution state, Linux reports it as aarch64 in the output of uname -m, and Debian-based distributions and Docker call the same architecture arm64. Software built for any of these names runs on your server.

### Will my software run on Arm64?

Most open-source server software does: web servers, databases, language runtimes such as Node.js, Python, Go, Java, .NET, PHP and Rust, and many Docker images are published for arm64. Software that exists only for x86, such as some closed-source agents or tools, has to be rebuilt for arm64 or replaced. Check the vendor's download page or the image's platform list before you move.

### Can I use it as a CI runner?

Yes, and nested virtualization adds an option: start a fresh virtual machine for every job, so builds never share state. GitHub Actions runners, GitLab Runner, Jenkins and Buildkite agents all run on Linux arm64, and your arm64 jobs then build and test natively next to your x86 runners.

### Which operating systems can I install?

The systems each plan offers are listed on this page and in the order form; pick one when you order. They are 64-bit Arm builds, so the packages you install from the system's repositories are arm64 packages as well.

### How do I connect to my Arm64 VDS?

We email the IP address and root login details as soon as the server is ready. Connect with any SSH client, such as Terminal on macOS and Linux or Windows Terminal and PuTTY on Windows, then add your SSH key and turn off password logins.

### Can I run Docker and Kubernetes on it?

Yes. Docker Engine, Docker Compose, Podman and lightweight Kubernetes distributions such as k3s are available for arm64, and the steps in our Docker and k3s guides apply to Arm64 servers too. Pull the arm64 or multi-platform variant of an image, or build your own on the server.

### Which billing cycles can I choose?

Every plan lists the billing cycles it is offered with. Switch the cycle above the plans to compare prices; longer cycles show the saving against monthly billing when there is one.

### How do I pay?

Choose one of the payment methods offered at checkout. Every invoice also stays available in the client area, where you can pay it online.

### Where do I manage my service after ordering?

Your service appears in the client area as soon as it is set up. From there you can manage it, pay invoices and open support tickets.

## Questions before you order?

Send us a message and our team will help you choose the right service.

[Contact us](https://hyperdc.com/contact-us) [Client area](https://hyperdc.com/account)

Support ticket

**You**Can you help me move my website to a new server?

**HyperDC team**Of course. Send us the details of your current host and we will plan the move with you.

Answered

---

Source: <https://hyperdc.com/arm64-vds>\
Updated: 2026-10-10
