Servers protected by a shield and a security perimeter

Less exposed code, fewer risks

The platform is built on OpenBSD, a system known for its security, and on deliberately compact code. Its services are confined by pledge and unveil: each one can only do what it needs to, even if it is compromised. Each VM is a separate, unprivileged process.

Confidential VMs

On AMD EPYC servers, a VM can run with memory encrypted by the processor (AMD SEV), with a key unique to that VM: its memory remains unreadable to the host system. This protection comes on top of disk encryption.

Data encryption

VM disks can be encrypted with AES-256-XTS, using keys managed by the platform. A removed disk, a replication copy or the remnants of a deleted volume remain unreadable.

Network isolation

Each organization has its own routing table: no layer 2 network is shared between customers. Each VM has its own firewall, which also blocks address spoofing.

Identities, roles and audit

Your team members sign in through a shared identity portal, with two-factor authentication, or with their company account (OpenID Connect). The platform checks the permissions of their role on every request, and every action is recorded in the audit log.

Your VMs belong to you

The platform installs no agent in your VMs and does not log into them. Catalog applications are installed on first boot, by cloud-init, with no subsequent access.

Security

At a glance

Reduced surface

OpenBSD, confined services, compact and auditable code.

Confidential VMs

Memory encrypted by the processor (AMD SEV).

Encrypted disks

AES-256-XTS, keys managed by the platform.

Isolation through routing

No network shared between customers.

Single sign-on and 2FA

Federation with your company account.

Audit log

Every action is tracked.

Frequently asked questions

Good to know

A VM whose memory is encrypted by the processor, with a key unique to it (AMD SEV). Its memory remains unreadable to the host system, which protects data while it is being processed, in addition to encrypted disks.

The platform installs no agent in your VMs and does not log into them. To go further, encrypt your disks and choose a confidential VM.

Through a shared identity portal, with two-factor authentication, or with your company account (OpenID Connect). Each person is given a role that defines what they can do.
PYSOFT Cloud

The other services in your VDC

How the PYSOFT cloud works

The PYSOFT cloud combines proven building blocks (OpenBSD, KVM, etcd, pf, relayd) around simple, auditable code. The goal: to offer …

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 …