Skiff 1
- vCPU
- 1 × shared
- RAM
- 1 GB
- Storage
- 20 GB NVMe SSD
- Transfer
- 2 TB
- IPv4 / IPv6
- 1 / /64 routed
Operating system
OpenBSD is built around correctness and secure defaults: two remote holes in the default install in a quarter of a century, W^X enforced, pledge and unveil sandboxing throughout the base system. It is the natural choice for a firewall, a jump host, or anything on the edge of your network.
KVM gives you a real machine: your own kernel, your own /proc, nothing shared. That is exactly what OpenBSD needs, and what OpenVZ or LXC cannot offer—they pin you to the host kernel. Before you choose it, know that OpenBSD here is not about speed. You are trading raw throughput for security and correctness. If you expect a performance race, this is the wrong system.
Customers run firewalls, bastion and jump hosts, mail relays, and DNS servers. These are edge roles where OpenBSD's secure defaults and tiny footprint beat raw performance. The small package ecosystem rarely matters—these jobs need little beyond base. Accept the six-month release cadence and you get a system that is boring in the best way.
The OS itself boots in 256 MB, but that leaves nothing for your application. Plan on 1 GB as the comfortable floor—enough for sshd, a mail relay, or a DNS resolver with headroom. Disk is cheap; start at the base plan and grow. OpenBSD's footprint means you are not paying for idle kernel memory.
OpenBSD boots in 256 MB and is comfortable with 1 GB. Add whatever your application needs on top of that — the operating system baseline is a floor, not a budget.
Yes, on true KVM virtualisation, which is what every OnionVPS instance runs. This would not be possible on OpenVZ or LXC-based virtual servers, which share the host kernel and can only run Linux.
2 releases (~1 year)
Yes. Every OnionVPS plan includes custom ISO upload, so you can boot the exact OpenBSD version you want—7.8 or 7.7—rather than a provider image. True KVM means the installer sees real hardware, and you keep full control of partitioning and flags.
Absolutely. A wrong pf rule can lock you out of SSH, but the VNC console is always available, independent of the guest network. You can recover without opening a ticket—just boot to single-user or edit the config from the console.