Coming soon · private beta first

NovaPanel VPS

Install it on your dedicated server and start creating KVM virtual servers to sell. Add more dedicated servers as nodes whenever you grow, and run them all from one panel, with the same design as the NovaPanel you already know.

An alternative to Virtualizor, VirtFusion and SolusVM.

One email when the beta opens and one at launch. No newsletter. Privacy policy

From a dedicated server to a VPS business

  1. 1

    Install the panel

    One command on a dedicated server running Ubuntu or Debian sets up the panel and its database.

  2. 2

    Add your servers as nodes

    The same machine, or as many others as you have. One command installs KVM and the node agent and connects it to the panel.

  3. 3

    Create and sell VPSes

    Set up plans, IP pools and OS images, then deploy servers for your customers. Each customer gets their own panel to run them.

Everything in it

Built and working in the current build, ahead of the beta. A few parts are still being tested on more hardware before invitations go out.

Servers

  • Deploy from cloud images with cloud-init: password or SSH keys, network and hostname set on first boot
  • Deploy several at once with a name pattern
  • Bring your own qcow2 or raw image from a link
  • Private templates made from an existing server
  • First-boot scripts at deploy and reinstall
  • One-click apps: Docker, Portainer, WordPress, LAMP, Node.js, n8n and more
  • Rebuild, resize, clone, rename and move to another client
  • Extra disks, attached live and kept on reinstall
  • UEFI, Secure Boot, vTPM, CPU model and dedicated cores per plan
  • Deletion protection, suspend, and servers that expire on a date
  • Reserve a server now, pick the OS later
  • Bulk and scheduled power actions

Console and access

  • Browser console (noVNC) with paste, key combinations, screenshots and recording
  • Serial console
  • The hypervisor's address never reaches the customer
  • Root password reset through the guest agent
  • SSH key library, injected at deploy
  • Rescue mode with SSH ready and the login emailed
  • Ready-made connect command and one-click port opening
  • Time-limited support access the customer grants
  • Processes and services inside the server, with start, stop and restart

Storage, snapshots and backups

  • Named snapshots customers can revert themselves
  • Scheduled backups with count or daily, weekly and monthly retention
  • Encrypted offsite copies, configured in Settings
  • Restore in place, to a new server, or single files from a backup
  • Backup limits and manual-backup cooldowns per plan
  • Disk IOPS and bandwidth limits per plan, applied live
  • ISO library, customer ISOs from a link, and media per plan
  • Fleet-wide backup health page

Networking

  • IPv4 pools with automatic allocation, bound to nodes
  • Public bridged or routed addresses, and NAT with port forwards
  • Domain forwarding for NAT servers: HTTP by host name, HTTPS by SNI
  • Default-deny firewall per server, with rule templates
  • Anti-spoofing on by default
  • Network speed cap per plan
  • Reverse DNS self-service through PowerDNS
  • Private networks per client on a node
  • Outgoing mail (port 25) blocked on new servers until staff allow it
  • A map of the whole network

Bandwidth

  • Monthly traffic metering per server
  • Quotas that throttle or suspend
  • A warning at 80%, by email, webhook or chat
  • Overage policy per plan

Monitoring and alerts

  • CPU, memory, disk and network graphs per server, live up to a year
  • Host graphs for every node
  • Alert rules with duration, cooldown, mute and acknowledge
  • Alerts to email, Slack, Discord, Telegram or a webhook
  • Prometheus exporter and Grafana dashboard
  • Unusual-activity detection: traffic, packet rate and CPU
  • Uptime checks with down and back-up emails
  • A public status page with locations and maintenance
  • Hardware sensors and out-of-band power through IPMI or Redfish

Nodes

  • Many nodes, grouped by location
  • Placement that spreads or fills, with a location picker
  • CPU and memory overcommit ratios
  • Pause new deploys on a node
  • Node health at a glance, and offline detection
  • Browser terminal to a node, opt-in and audited

Customers, resellers and teams

  • Resellers with quotas, their own branding and their own domain
  • Staff roles with 21 permissions
  • Customer teams: owner, member and viewer, invited by email
  • Log in as a client
  • Guided deploy with OS tiles and priced plans
  • Getting-started checklist and a spend and bandwidth overview
  • Announcements and targeted mailouts to customers
  • 7 languages, plus language packs you upload

Security

  • Two-factor sign-in with recovery codes, and passkeys or security keys
  • Enforce two-factor for the whole team
  • Sign-in history and a new sign-in email
  • CAPTCHA, admin IP allowlist and login throttling
  • Audit log, plus an activity timeline per server
  • Passwords and secrets encrypted at rest
  • Signed updates that cannot be rolled back

API and automation

  • REST API for staff and customers, with an OpenAPI reference
  • "Try it" console in the API docs
  • Scoped tokens: read-only, expiry, maximum lifetime
  • Signed webhooks with retries
  • Command-line tool
  • Hook scripts that run on panel events

Running the panel

  • Everything set in the panel, no config files
  • Your logo, colours, theme presets and custom CSS
  • 12 editable email templates with preview, and an email log
  • One-line installer for the panel and for nodes, signature-checked
  • Updates from inside the panel, signed
  • Encrypted panel backups you can restore on a new server

Light on your hypervisors

Each node runs one small agent, a single static binary. There is no web application, database or PHP on your hypervisors, so there is less to patch and less to break.

  • Nodes connect over mutual TLS. The panel is its own certificate authority. A node enrols once and every request after that is authenticated both ways.
  • Tasks run on the node, not over SSH. Deploys, backups and console sessions are handed to the agent over that connection, and it reports the result.
  • Add nodes as you grow. Group them by location, bind address pools to them, and the panel marks a node offline if it stops checking in.

Questions

When does it launch?

There is no date yet. A private beta comes first, then a public one. Everyone on the waitlist hears about both before anything is announced elsewhere.

Does it replace the NovaPanel hosting panel?

No. NovaPanel VPS is a separate product for running virtual servers. The hosting panel carries on exactly as it is, with its own releases and licences.

What do I need?

A dedicated server, or several, running Ubuntu or Debian with hardware virtualisation (Intel VT-x or AMD-V) turned on. The panel and a node can share one machine, so a single server is enough to start.

Does it connect to WHMCS or another billing system?

Not yet. The beta is for running servers; billing integrations come later. The API and signed webhooks are there today if you want to wire up your own.

Can I move servers over from another panel?

There is no importer yet. Bringing your own disk image from a link works today.

Does it do LXC containers as well?

Not yet. Today it creates KVM virtual machines: full servers with their own kernel, which is what most VPS customers expect.

How will it be priced?

The plan is a flat price per node, with no charge per virtual server, and a free tier for a small setup. Final prices are announced at launch.

Want in early?

The private beta goes to the waitlist first.

Join the waitlist