Virtual Machines

Full virtual machines on decentralized infrastructure

Need more than containers? LinqProtocol supports complete virtual machines via KubeVirt. SSH in with your private key, run any OS, and treat it like any cloud instance.

KubeVirt

The best of both worlds

KubeVirt is a Kubernetes add-on that allows you to run virtual machines alongside containers on the same infrastructure. It brings traditional VM workloads into the Kubernetes ecosystem.

This means you can:

  • Run legacy applications that require a full OS
  • Use operating systems and kernels not available in containers
  • Get true process isolation for security-sensitive workloads
  • SSH into your instances like traditional cloud VMs
Capabilities

Everything you need from a VM

SSH Access

Connect via SSH using your private key. Manage your VM exactly like you would an AWS EC2 or DigitalOcean droplet.

Multiple OS Options

Run the operating system you need: Ubuntu, Debian, CentOS/Rocky or Alpine. (Custom images coming soon)

Persistent Storage

Attach persistent volumes that survive reboots. Store data, databases, and state.

Networking

Full network access with public endpoints. Run web servers, APIs, databases - anything that needs to be reachable.

Resource Flexibility

Choose CPU cores, memory, and storage based on your workload. Scale up when you need more.

Coming Soon

Snapshot & Backup

Create snapshots and backups of your VMs for disaster recovery.

Use Cases

When you need a full VM

Legacy Applications

Some applications require a full operating system, specific kernels, or system-level access that containers can't provide.

Development Environments

Spin up a complete dev environment that matches production. SSH in and work like you're on a local machine.

Security Isolation

For workloads that need stronger isolation than containers provide, VMs offer a hardware-level boundary.

Database Servers

Run database servers with full control over configuration, tuning, and backup strategies.

Build Servers

CI/CD agents, build farms, and compilation jobs that need a full Linux environment.

Comparison

When to use what

Use Containers When:

  • Your app is containerized (Docker)
  • You want fast startup times
  • You're deploying stateless services
  • You need easy horizontal scaling

Use VMs When:

  • You need SSH access
  • Your app requires a full OS
  • You need kernel-level features
  • Security isolation is paramount
  • You're running legacy software

LinqProtocol supports both. Use containers for modern microservices, VMs for everything else. Mix and match based on your needs.

SSH Access

Connect like any cloud VM

1

Launch Your VM

Choose your OS, select resources, and deploy through the LinqProtocol dashboard.

2

Download Your Key

Download your private key file from the dashboard. Keep it secure.

3

Connect

Use SSH with your private key to connect to your VM.

_
4

Work

Install software, run processes, manage your server - full root access.

Security

Secure by design

Key-Based Auth - Password authentication is disabled. Only key-based access.
Network Isolation - VMs run in isolated network namespaces
Firewall Rules - Only ports you expose are reachable
Encrypted Storage - Persistent volumes are encrypted at rest
Pricing

Pay for what you use

VMs are billed based on resources consumed:

  • vCPU hours
  • Memory (GB hours)
  • Storage (GB/month)

Pricing is up to 80% savings vs. AWS for equivalent EC2 or GCP Compute Engine instances.