Physical servers carrying a layer of virtual machines

A lean platform, by design

Each component has only the privileges it needs. The platform's services are written in Go and confined by OpenBSD's pledge and unveil mechanisms: even if compromised, a process can neither read nor execute anything outside its scope.

The building blocks are mature and well known: OpenBSD's vmm hypervisor, KVM for Windows and GPUs, the pf firewall, the relayd load balancer, etcd for the platform state. Our code assembles them; it does not replace them.

Two families of hypervisors

By default, your Linux and OpenBSD VMs run on vmm, the hypervisor built into OpenBSD: each VM is an isolated, unprivileged process. Windows VMs and those using an NVIDIA GPU run on KVM servers, managed by the same platform and connected to the same private networks.

On AMD EPYC servers, a VM can also be confidential: its memory is encrypted by the processor (AMD SEV), with a key unique to that VM.

A routed network, with no shared network

Each VM receives an address announced individually by the server that runs it (/32 routing via BGP, internal to the platform). There is no large layer 2 network shared between customers: each organization has its own routing table and its own private networks, isolated from the others even when address ranges overlap.

Example of a virtual data center (VDC) on the PYSOFT cloud From the Internet, traffic arrives on a public IP associated with a load balancer, which distributes it across two web instances connected to a private SDN network. A database uses a volume replicated in three copies, protected by backups and CDP. Outbound traffic to the Internet goes through address translation (SNAT). Internet Your VDC: isolated organization inbound outbound Public IP Load balancer Internet egress address translation (SNAT) Routed private network · 10.0.0.0/24 Web instance 1 “web” firewall Web instance 2 “web” firewall Database “db” firewall Volume (3 copies) Backups and CDP
VDC example: the load balancer distributes traffic across two web instances, the database keeps its data on a replicated, backed-up volume, and outbound traffic to the Internet goes through address translation.

Distributed storage and data protection

VM disks are split into chunks written in three copies on three different servers. They can be encrypted with AES-256 using keys managed by the platform. Snapshots, scheduled backups and continuous data protection (CDP) complete the picture.

High availability

If a server goes down, the platform isolates it (fencing) and then restarts its VMs on another server. Losing the control plane stops no VM: they keep running, and only operations are suspended until it comes back.

Portal, API, Terraform and AI assistant

Everything can be managed from the web portal, the documented REST API (OpenAPI), the command line, or Terraform and OpenTofu. An AI assistant built into the portal prepares routine operations for you: you confirm them with one click.

The platform

At a glance

Reduced attack surface

Confined services (pledge, unveil), auditable code, no unnecessary components.

vmm and KVM

Linux and OpenBSD on vmm; Windows and GPUs on KVM.

Confidential VMs

Memory encrypted by the processor (AMD SEV).

Routed network

/32 addresses announced via BGP, one routing table per organization.

Distributed storage

Three copies on three servers, encryptable disks.

Automatic failover

VMs from a failed server restart elsewhere.

Backup and CDP

Scheduled backups and restore to the second.

AI assistant

It prepares your operations; you confirm.

API and Terraform

REST API, command line, Terraform and OpenTofu provider.

Process

How it works

Step 1

You request

From the portal, the API, Terraform or the AI assistant: flavor, image, network, firewall.

Step 2

The platform places

The controller picks a server based on your quotas and the available capacity, then prepares the network, firewall and disks.

Step 3

The VM boots

You connect to it over SSH (Linux, OpenBSD) or remote desktop (Windows).

Frequently asked questions

Good to know

On proven open source building blocks: OpenBSD's vmm hypervisor for Linux and OpenBSD VMs, KVM for Windows and GPUs, etcd for the platform state, pf for the firewall and relayd for load balancing. The code that assembles them (agent, controller, portal) is developed by PYSOFT.

vmm, OpenBSD's hypervisor, for Linux and OpenBSD VMs; KVM for Windows VMs and those that use a GPU.

Yes: a REST API described in OpenAPI, a command line, and a Terraform and OpenTofu provider for VMs, security groups, public IPs and load balancers. Programmatic access uses application credentials, with the permissions of a role.

Yes. Each organization has its own routing table and its own private networks; its VMs, volumes, firewall rules and backups are only accessible to its members, according to their role.

For its security: the system is designed to reduce the attack surface, and its confinement mechanisms (pledge, unveil) limit what each process can do. Its networking components (pf, relayd, bgpd, iked, WireGuard) are built in and have been proven for years.

The platform isolates the server and then restarts its VMs on another server, from their replicated disks. Losing the control plane, on the other hand, stops no VM.
PYSOFT Cloud

The other services in your VDC

Your virtual data center (VDC) in Algeria

A VDC brings your entire infrastructure together in an isolated space: servers, networks, firewall, VPN, storage and load balancers. You …

Virtual servers hosted in Algeria

Virtual servers hosted in Dellys and billed in dinars: choose a predefined configuration or build your VM by the vCPU, …

Encrypted VMs, from disk to memory

Encrypt each VM's disk with AES-256 using a key unique to that VM, and its memory with the AMD processor. …

Appstore: your applications ready in minutes

Choose an application and a VM size: the platform takes care of the rest, from installation to HTTPS, including the …

Autoscaling: your servers follow the load

An instance group adds VMs when the load goes up and removes them when it goes back down. You pay …

Routed SDN network: private networks and public IPs

Each organization has its own network, isolated from the others at the routing level. Your VMs communicate with each other …

Firewall as a Service (FWaaS) based on pf

Every VM has its own firewall, applied on its interface by pf, OpenBSD's firewall. You get the fine-grained control of …

VPN as a Service: IPsec and WireGuard

Connect your offices and your team members to your private network in the cloud, without exposing your servers to the …