VorticPanel

What's new in VorticPanel.

Every release and what changed in it. The newest is 0.3.72, from October 24, 2026.

October 2026

Versions 0.3.0 to 0.3.72

  • Imports from VirtFusion and Virtualizor: pick the servers, copy them while they run or adopt them in place, and roll back for up to 14 days.
  • Live moves between nodes, and moves with one restart between Intel and AMD or between Linux distributions.
  • Resellers sell servers and GPU instances within the quotas you set.
  • GPU instances in containers, with JupyterLab over HTTPS and the customer's own Docker image where you allow it.
  • Billing through WHMCS or Blesta, with one-click sign-in for customers.
  • Private networks between nodes encrypted with WireGuard, and nodes that only take orders signed by your panel.
  • IPv6 pools of any size, and backups made while servers keep running.
Show each release
  1. 0.3.72

    • A node's SSH can be on any port: the panel reads it from the node and shows it on the node's Overview, and moves to the node connect there.
    • Imports read each source hypervisor's SSH port from the source panel when it gives one, and Change port beside the hypervisor sets it.
  2. 0.3.71

    • GPU instances show their usage over the last hour, day, week or month: GPU load, card memory, temperature, power, CPU, memory and network.
    • An instance can be renamed from its Details too.
  3. 0.3.69

    • GPU instance pages show the two disks plainly: Your files (/workspace, kept) and System disk (reset when started afresh).
    • CUDA works in GPU instances after their host restarts; hosts missing the device CUDA needs are repaired when the update reaches them.
    • Own GPU images from private registries pull with the login given.
    • Own GPU images take an image's page address from Docker Hub, GitHub, Quay or NVIDIA NGC, with or without https://, and show which image they'll run.
    • When an image can't be pulled, the message says whether the registry has no such image, is limiting pulls or can't be reached.
  4. 0.3.67

    • GPU instance pages show the two disks plainly: Your files (/workspace, kept) and System disk (reset when started afresh).
    • Own GPU images take an image's page address from Docker Hub, GitHub, Quay or NVIDIA NGC, with or without https://, and show which image they'll run.
    • When an image can't be pulled, the message says whether the registry has no such image, is limiting pulls or can't be reached.
  5. 0.3.64

    • Own GPU images take a Docker Hub page address or a docker pull command, and show which image they'll run.
    • The GPU node installer restarts the machine at the end when the NVIDIA driver needs it to load.
  6. 0.3.63

    • Servers can't be suspended or terminated while they're moving, and a cancel that comes too late finishes the move instead.
    • Wrong two-factor codes are limited per day, and a lockout emails the account's owner; staff managers hear about new staff, role changes and panel API keys.
    • The audit log is tamper-evident, copied to the system journal and checked with vorticpanel audit-verify.
    • Nodes keep servers' disks out of their own disk scanning, and folders a GPU image declares as volumes count toward the instance.
    • The Updates page warns when the update server offers an older version than before.
  7. 0.3.62

    • Customers → SSH keys lists every customer's saved SSH keys, to search them and remove one from an account.
    • Billing panels keep changing packages, addresses, backup plans and power while the license needs attention.
    • Imported servers keep the virtual hardware they had, and VirtFusion customers their time zone.
    • Resellers are told when any change takes a quota past 90%.
    • Security fixes from a full review, and help text that matches what the panel does.
  8. 0.3.61

    • Imported servers keep their own CPU and memory when the package they're mapped to is smaller, as they already kept their disk size.
  9. 0.3.60

    • Debian 12 and other Linux servers with a minimal cloud kernel now read their first-boot settings, so they come up with their hostname, password, network and guest agent.
    • A reinstall's snapshot is kept when a later step of the reinstall fails.
    • A reinstall's snapshot is marked as not consistent when the server didn't shut down in time and was forced off.
    • Imports from VirtFusion count each server's traffic the way VirtFusion did (both ways, inbound only or outbound only), and its first traffic period ends when it would have there.
    • Packages created from VirtFusion's count and reset traffic the way their servers did.
    • VirtFusion servers protected from deletion arrive with delete protection on.
    • The import's dry run names servers that had firewall rules on the source panel, which don't come across.
  10. 0.3.58

    • Imports can create a source panel's packages here, with the same CPU, memory, disk, traffic and port speeds, one at a time or all at once.
    • A package the source panel no longer sells comes over hidden.
  11. 0.3.56

    • Imports connect to VirtFusion panels that only answer on their own domain name.
    • A VirtFusion that refuses its IP address says to use its domain name instead.
  12. 0.3.55

    • Imports wait and try again when the old panel asks them to slow down.
    • Imports say what refused the API key.
    • A node can be drained while it's offline.
  13. 0.3.54

    • Backups and snapshots of running servers are made while they keep running.
    • A backup no longer fails when a node briefly loses its connection.
  14. 0.3.53

    • Rocky Linux and AlmaLinux nodes set up their network bridge themselves.
    • Moves with a restart work between AlmaLinux, Rocky, Debian and Ubuntu nodes.
    • Catalog OS templates pick up newer builds by themselves.
    • Windows servers answer ping over IPv6.
  15. 0.3.52

    • IPv6 pools of any size, handing each server a block of the size you choose, down to one address.
  16. 0.3.51

    • Packages can allow more than one storage tier.
    • A banner on the server page when changes wait for a restart.
    • Removing a disk waits for the server to let go of it.
  17. 0.3.50

    • Default virtual hardware for new servers, panel-wide or per package.
    • Windows sees disks on SCSI or SATA as solid-state drives.
    • Nodes show physical cores and threads.
  18. 0.3.49

    • A node keeps its place in the panel after its OS is reinstalled.
    • Servers whose disks were lost can be restored from their latest backups, all at once.
    • Moves get through when a node's SSH server is busy.
  19. 0.3.48

    • Extra traffic added this month can be taken back.
    • Saved Windows images get a fresh identity for each server made from them.
    • Set up the bridge on a node's Settings tab.
  20. 0.3.47

    • Staff can set a server's own monthly traffic allowance.
    • Imported servers keep their own traffic limit every month.
  21. 0.3.46

    • Pick which servers an import brings, with search and filters.
    • Imported servers keep their power state, suspension, reverse DNS, traffic, extra disks and their owners' SSH keys.
    • Customers get a "Your server has moved" email.
    • Firmer limits on self-service servers, private networks and GPU power actions.
  22. 0.3.45

    • Fixed moves between nodes failing with "Permission denied".
    • A node's management address can be changed on its Settings tab.
  23. 0.3.44

    • New IPv4 pools take the gateway, netmask and usable range your provider gave you.
  24. 0.3.43

    • The fleet overview works on a new panel before any package exists.
    • A node being installed isn't reported as down before it first connects.
  25. 0.3.42

    • Consoles keep working on a node whose DNS stops answering, and the node repairs its DNS settings.
  26. 0.3.41

    • Adopt-in-place imports show only the settings that apply to them.
  27. 0.3.40

    • Customers get an email when their password, two-factor or keys change.
    • Changing package adds the new package's IP addresses.
    • Unmetered packages are never slowed or suspended for traffic.
    • Staff see a line at the top of the page when an update is out.
  28. 0.3.39

    • Hidden packages are offered only to staff and billing.
    • Clearer wording across the panel.
  29. 0.3.38

    • Moves with a restart are off only for the restart itself.
    • Customers can run their own Docker image on GPU offers that allow it.
    • A separate logo for the dark theme.
  30. 0.3.37

    • Servers that can't move live move with one restart, even between Intel and AMD nodes.
    • JupyterLab on GPU instances can be served over HTTPS through the panel.
  31. 0.3.36

    • Enrolling a node is its own permission.
    • Staff are alerted when a node's credential is replaced, or when a node reports more hardware than before.
    • Fixes from a full security review.
  32. 0.3.35

    • Emptying a node can give servers new addresses where theirs won't work, and email the customers.
    • A server's storage type no longer stops it moving.
  33. 0.3.34

    • Imported servers start with BIOS or UEFI to match their disk.
    • Force off during a hardware change leaves the server off, and the change applies at its next start.
  34. 0.3.33

    • Imports copy servers while they run, and each is offline only for a last short pass.
    • Imports can be scheduled up to 30 days ahead, with an email to each customer.
    • Notifications can be filtered by topic.
  35. 0.3.32

    • Delete protection and hard reset for servers.
    • Outbound firewall rules for customers.
    • Separate inbound and outbound port speeds, and a choice of how traffic is counted.
    • Webhooks to Slack, Discord and Telegram, and Prometheus metrics.
    • Your own logo, and a time zone for each person.
  36. 0.3.31

    • Any folder on a node, such as one on a second drive, can be storage.
  37. 0.3.30

    • Floating IPs can only be reserved where the account has a server.
  38. 0.3.29

    • IP pools can be renamed, and single addresses taken out of them.
    • Staff can release a customer's floating IP.
  39. 0.3.28

    • Staff are told when storage runs low or goes missing.
    • Floating IPs come from another pool in the location when the first is full.
  40. 0.3.27

    • Smaller fixes to support sessions, node keys and messages.
  41. 0.3.26

    • Nodes only take orders signed by your panel.
    • Private networks between nodes are encrypted with WireGuard.
    • GPU instances run in user namespaces, so root inside isn't root on the host.
    • GPU instances can wait for the customer to choose an image.
    • Fixes from a full security review.
  42. 0.3.25

    • Every server's backups and snapshots in one place, under Fleet.
    • Report a problem sends an issue to support along with the panel's diagnostics, which you see first.
  43. 0.3.24

    • Billing can add a customer's SSH key from their order.
  44. 0.3.23

    • Works with the VorticPanel WHMCS module, from Downloads in your account.
    • Billing can sign customers straight in to the panel.
    • A log of every API call, under Administration → API requests.
    • Customers and resellers can be deleted once nothing of theirs is running.
  45. 0.3.22

    • Panel API keys belong to the panel, not a staff member, so billing keeps working when staff leave.
    • The installer gets Caddy from the system's packages or Caddy's own release.
  46. 0.3.21

    • Servers on a node that isn't answering show their status as Unknown.
  47. 0.3.20

    • A node that stays connected but stops reporting shows as offline after 5 minutes.
  48. 0.3.19

    • A bot check (Cloudflare Turnstile) can be turned on for sign-in and password resets.
  49. 0.3.18

    • Resellers' own servers and the ones they sell are listed apart.
  50. 0.3.17

    • Resellers see everything they sell in one list, with search and filters.
    • Resellers can open the console and JupyterLab on their customers' GPU instances.
  51. 0.3.16

    • A reseller's page says which of its locations can't take servers right now.
  52. 0.3.15

    • The GPU offers list shows where each offer is sold and how much room is left.
  53. 0.3.14

    • Resellers can sell GPU instances, limited to the offers and number of cards you give them.
  54. 0.3.13

    • Low and high CPU priority now give half and double a normal server's share.
  55. 0.3.12

    • The Updates page lists recent releases and this panel's update history.
    • Usage reports show past months' traffic.
    • Force off isn't offered while a server is moving.
  56. 0.3.11

    • Imports bring Windows servers on the virtual hardware they had, so they boot with their own drivers.
    • IDE can be chosen as a disk bus for older Windows servers.
  57. 0.3.10

    • Imports bring UEFI servers, with or without Secure Boot, along with their boot entries.
  58. 0.3.9

    • Encrypted copies of the controller can go to S3 or SFTP every hour or day, under Settings → Backups.
  59. 0.3.8

    • The installer sets up a firewall on the controller: SSH, HTTP and HTTPS only.
  60. 0.3.7

    • Pages left open across an update load again without a refresh.
  61. 0.3.6

    • Firmer limits on requests, consoles and sign-ins.
    • Staff see only what their role allows, including in support sessions.
    • GPU container hosts need NVIDIA Container Toolkit 1.17.8 or later.
  62. 0.3.5

    • Install with one command from vorticpanel.com.
    • A new panel asks for its license key, with links to the free trial and the plans.
  63. 0.3.4

    • Fixed servers on the same node sometimes failing to apply their settings at the same moment.
  64. 0.3.3

    • The panel checks its license and looks for new versions every hour.
  65. 0.3.2

    • Updates show each step as it happens.
  66. 0.3.1

    • Updates no longer stop when an outside package repository is down.
  67. 0.3.0

    • Agent updates are signed with the release key; a node that has had a signed agent only takes signed ones.
    • Security fixes: two-factor guessing, root passwords no longer kept with repeated requests, import address and adoption checks, reverse DNS sync, private network guard, move keys expire, IPv6 router spoofing, GPU instance isolation.